Re: [pylons-discuss] view_execution_permitted problem

2014-06-02 Thread Laurence Rowe
On Monday, 2 June 2014 04:25:13 UTC-7, Gerhard Schmidt wrote: > > Authorization policy gets the principals returned by the group finder > which may include the original principal but may not. So i would have to > re implement the group finder within the authorization policy. Sounds > redundant t

[pylons-discuss] Re: Integrating Schedular with Pyramid

2014-06-02 Thread Jonathan Vanasco
You can use "Command Line Pyramid" for this. http://docs.pylonsproject.org/docs/pyramid/en/latest/narr/commandline.html 1. Create a Python script that loads the pyramid API and bootstraps a request object. 2. Do whatever you want. 3. Trigger the script with whatever scheduling software you p

Re: [pylons-discuss] view_execution_permitted problem

2014-06-02 Thread Gerhard Schmidt
Am 02.06.2014 09:20, schrieb Laurence Rowe: > On Wednesday, 28 May 2014 00:17:11 UTC-7, Gerhard Schmidt wrote: > > The whole problem is the authentication policy isn't context aware. you > can't pass a different context from the one in request.context to > effective_principals and furt

[pylons-discuss] Integrating Schedular with Pyramid

2014-06-02 Thread Aniruddha Gaikwad
Hi, I am trying to integrate scheduler with Pyramid. I checked Celery, but looks like it did not support MSSQL. I am already using sqlalchemy to access MSSQL database. I also check pyramid_celery, but cant figure out how to run. My requirement for scheduler is : 1, Schedule task everyday at

Re: [pylons-discuss] view_execution_permitted problem

2014-06-02 Thread Laurence Rowe
On Monday, 2 June 2014 00:20:53 UTC-7, Laurence Rowe wrote: > > For my project I replicated something very similar to the Zope2/CMF/Plone > based local roles. I'll pull it out into a separate package if it's > useful to others. > https://github.com/ENCODE-DCC/encoded/blob/v11.0rc1/src/encoded/lo

Re: [pylons-discuss] view_execution_permitted problem

2014-06-02 Thread Laurence Rowe
On Wednesday, 28 May 2014 00:17:11 UTC-7, Gerhard Schmidt wrote: > > The whole problem is the authentication policy isn't context aware. you > can't pass a different context from the one in request.context to > effective_principals and further down to the callback. > > I circumvented this proble