;m wondering what is the latest version of AuthKit.. is there a
location this is stored (the repository i found which i searched
seemed pretty old)?...any ideas?
Steven
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
&
I'm a newbie as well (working through the pylonsbook.com) in my
SimpleSite/simplesite/websetup.py I have this line at the top of the
file which defines "model".
from simplesite import model
I think adding it to your websetup.py might do the trick.
Steven
On Oct 9, 11:05
ing SQLAlchemy and UsersFromDatabase? (I mean is AuthKit complete?)
[2] if so, any times on the exception I'm seeing?
Steven
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
I'm a newbie trying to get a grasp on what options I have for
Authentication and Authorization. From reading the docs and the
pylonsbook.com I've found 2 options so far:
repoze.who (ported from Zope)
AuthKit (work in progress? )
Are there others?
--~--~-~--~~~---~--~
ntation).
>
> On Oct 14, 4:04 pm, Steven <[EMAIL PROTECTED]> wrote:
>
> > I'm going through the tutorials athttp://pylonsbook.comandhave been
> > trying to get through the AuthKit section for a while.
>
> > I've tried both "easy_install AuthKit==dev&
ps there could be a "run level" concept
introduced here to help group them so that ordering can be automated.
For step #5 seems like a similar strategy could be adopted as #2
Well... that was what was on my mind this morning for some reason
and I thought
Thanks for your reply.
After going through the tutorials for AuthKit and for repoze.who, I
ended up taking your advice and building my own simple login for basic
login and authorization.
Thanks for the response!
Steven
On Oct 15, 3:30 pm, "Mike Orr" <[EMAIL PROTECTED]> wrot
class Sub(Base):
def _do_foo(self):
then you can have lovely generic methods and just add in an auxiliary
method at any point where you need to change behaviour depending on
subclass.
Cheers,
Steven
--~--~-~--~~~
account/create, while the nice
separation between form display and form processing is maintained.
I don't know what effect this change would have on backwards
compatibility, but it can be made with a trivial (two lines or so)
change to @validate. (I can do a quick patch if anyb
On 29 Jan 2008, at 08:36, Alberto Valverde wrote:
>
> Steven Holmes wrote:
>> Hi,
>>
>> @validate supports separating form rendering and form post processing
> into distinct methods. This is convenient, but has a nasty flaw: It
> requires two separate URLs, a form d
efault* do the right thing, which is to
have one exposed url for a form. Or at least, the documentation should
be altered or extended so that the one-url way of doing things is
prominent.
Basically, what I'm saying is I think @validate is broken and should
be fixed, irrespective of an
On 29 Jan 2008, at 16:21, Mike Orr wrote:
>
> On Jan 29, 2008 3:28 AM, Steven Holmes <[EMAIL PROTECTED]> wrote:
>> In my opinion, it should be *default* do the right thing, which is to
>> have one exposed url for a form. Or at least, the documentation
>> shoul
have this particular religion, but what would a REST zealot
> say? Seems like two different URI's for the same thing is bad.
>
> I've hacked up my base controller class to make it work the way that
> Steven wants. I suppose to me, clean URIs are better than clean
>
cts to /account/id)
/account/id <-- Displays the account details
/account/id/edit <-- Edit account details (similar to /account/create)
/account/delete <-- Deletes the account (GET gives a form asking
confirmation, POST does the deletion).
This has worked very well for me so far.
Chee
Just realised I accidentally sent this to Mike directly instead of the
list.
On 29 Jan 2008, at 23:17, Mike Orr wrote:
>
> On Jan 29, 2008 2:55 PM, Steven Holmes <[EMAIL PROTECTED]> wrote:
>
>> What I was suggesting for @validate would still have two methods on
>> t
15 matches
Mail list logo
