[Repoze-dev] repoze.bfg 1.0a7 released...

2009-06-30 Thread Chris McDonough
1.0a7 is a feature release which extends the "resource" feature required by a customer; now it is possible to override static resources as well as templates. There are no backwards incompatibilities. Tres also improved the "bfg_alchemy" Paster template. The bfg "current" index at http://dist

Re: [Repoze-dev] traversal vs url dispatch for rest'ish applications

2009-06-30 Thread Iain Duncan
On Tue, 2009-06-30 at 15:59 -0400, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Iain Duncan wrote: > > On Tue, 2009-06-30 at 15:30 -0400, Tres Seaver wrote: > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA1 > >> > >> Iain Duncan wrote: > >> > >>> Thanks for the cl

Re: [Repoze-dev] traversal vs url dispatch for rest'ish applications

2009-06-30 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Iain Duncan wrote: > On Tue, 2009-06-30 at 15:30 -0400, Tres Seaver wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Iain Duncan wrote: >> >>> Thanks for the clarification, that's what I tried last night, ( called >>> the top one PetCon

Re: [Repoze-dev] traversal vs url dispatch for rest'ish applications

2009-06-30 Thread Iain Duncan
On Tue, 2009-06-30 at 15:30 -0400, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Iain Duncan wrote: > > > Thanks for the clarification, that's what I tried last night, ( called > > the top one PetContextFactory ). The problem I hit was that if the PCF > > is the end of

Re: [Repoze-dev] traversal vs url dispatch for rest'ish applications

2009-06-30 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Iain Duncan wrote: > Thanks for the clarification, that's what I tried last night, ( called > the top one PetContextFactory ). The problem I hit was that if the PCF > is the end of the traversal, then the context should be a list of pets, > but if it

Re: [Repoze-dev] traversal vs url dispatch for rest'ish applications

2009-06-30 Thread Iain Duncan
On Tue, 2009-06-30 at 06:19 -0400, Chris McDonough wrote: > On 6/30/09 1:39 AM, Iain Duncan wrote: > >> Let's imagine a view "pets": > >> > >> from webob import Response > >> > >> def pets(context, request): > >> return Response ('OK') > >> > >> when a URL comes in that is for a paricular pet

Re: [Repoze-dev] repoze.bfg 1.0 final to be released by Monday July 6.

2009-06-30 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Aspeli wrote: > Chris McDonough wrote: >> If nobody finds any showstopper bugs, repoze.bfg 1.0 will be released on or >> before Monday July 6. Speak now or forever hold your peace wrt to API >> issues; >> after 1.0 the existing APIs will be

Re: [Repoze-dev] Help with integration with pylons needed

2009-06-30 Thread Vedran Hudec
Hi all, problem has been solved: 1) foo.password changed to foo._set_password('foo') 2) the problem was in the name "username" text box. It should be "login". Best regards, Vedran On Tue, Jun 30, 2009 at 11:25 AM, Vedran Hudec wrote: > Hi all, > > some help needed, I'm thinking of going crazy

Re: [Repoze-dev] traversal vs url dispatch for rest'ish applications

2009-06-30 Thread Chris McDonough
On 6/30/09 1:39 AM, Iain Duncan wrote: >> Let's imagine a view "pets": >> >> from webob import Response >> >> def pets(context, request): >> return Response ('OK') >> >> when a URL comes in that is for a paricular pet: >> >> from webob import Response >> >> >> def pets(context, request): >>

Re: [Repoze-dev] Help with integration with pylons needed

2009-06-30 Thread Bruno Binet
Hi, I encountered the same error following this tutorial : http://wiki.pylonshq.com/display/pylonscookbook/Authorization+with+repoze.what The line which hurts is : login_counter = request.environ['repoze.who.logins'] It works for me when I replaced that line by : if 'repoze.who.logins' in reques

[Repoze-dev] Help with integration with pylons needed

2009-06-30 Thread Vedran Hudec
Hi all, some help needed, I'm thinking of going crazy already. Dropped authkit solution because it was no good and you are my last hope before creating my own authorization/authentication solution. So, basically it is not working :(. In more words, the last error message is "wrong credentials" -