Re: [Repoze-dev] When to inherit from the persistent.Persistent

2010-04-06 Thread george hu
That is very clear, thanks Casey. On Tue, Apr 6, 2010 at 6:20 PM, Casey Duncan wrote: > The only requirement for an object to be stored in zodb is that it is > pickeable. However, if an object is mutable (as most user-defined objects > are) its class should subclass Persistent so that updates to

Re: [Repoze-dev] When to inherit from the persistent.Persistent

2010-04-06 Thread Casey Duncan
The only requirement for an object to be stored in zodb is that it is pickeable. However, if an object is mutable (as most user-defined objects are) its class should subclass Persistent so that updates to it are automatically saved and it will get put as its own "record" in the database. Practi

[Repoze-dev] deprecation of zcml for?

2010-04-06 Thread Iain Duncan
I noticed in the 1.2 docs that view configuration in zcml uses the 'context' predicate instead of the zope 'for' predicate. Just wanted to know if I can still safely use 'for' or whether new code should switch all those. The 1.2 improvements look great btw! thanks iain ___

Re: [Repoze-dev] When to inherit from the persistent.Persistent

2010-04-06 Thread Carlos de la Guardia
Hi, are you referring to this Feeds example: http://dev.karlproject.org/tutorials/t2-contentandcataloging/feedentries.html If that's the case, note that both Feed and FeedEntry inherit from repoze.folder.Folder, which in fact does inherit from Persistent: http://svn.repoze.org/repoze.folder/tru

[Repoze-dev] When to inherit from the persistent.Persistent

2010-04-06 Thread george hu
In the official documentation, the tutorial of zodb wiki shows a Page class who is inherited from the the Persistent. When I look at the Feeds Tool example on Karl, none of the model classes are inherited from the Persistent, but the objects are saved into the zodb. So I would like to know the deta

Re: [Repoze-dev] Problem with repoze.what-pylons sample application

2010-04-06 Thread Andrey Popp
It seems you have this application not installed in terms of setuptools: run `python setup.py develop`. Paste get WSGI application via entry point which are became active only after installing package. On Tue, Apr 6, 2010 at 3:11 PM, Phenex wrote: > Hi, > i am unable to run the sample application

[Repoze-dev] Problem with repoze.what-pylons sample application

2010-04-06 Thread Phenex
Hi, i am unable to run the sample application of the repoze.what pylons integration. I get a bunch of error from paste i do not understant what went went wrong. After i failed to get the new version to run (the old one hase problems with unicode usernames but worked fine with the rest, so i inst

Re: [Repoze-dev] current repoze.who in PyPI and repoze.what

2010-04-06 Thread Gustavo Narea
Thank you, Tres! I'll release repoze.what 1.0.9 now. On Tue, Apr 6, 2010 at 8:38 AM, Tres Seaver wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Chris McDonough wrote: > > On 4/6/10 2:27 AM, Tim Hoffman wrote: > >> Yep thats what found. > >> > >> But at the moment if you easy_insta

Re: [Repoze-dev] current repoze.who in PyPI and repoze.what

2010-04-06 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris McDonough wrote: > On 4/6/10 2:27 AM, Tim Hoffman wrote: >> Yep thats what found. >> >> But at the moment if you easy_install repoze.what you end up with >> repoze.who.2.0.x and you can't seem to get >> repoze.who 1.0.18 from PyPI > > Yeah. I f

Re: [Repoze-dev] RenderResponse objects

2010-04-06 Thread Chris McDonough
On 4/6/10 3:15 AM, Chris Withers wrote: > Chris McDonough wrote: >>> Also, how come you put response attributes on the request when using a >>> renderer? >>> >>> How about a RenderResponse object: >>> >>> class RenderResponse(dict): >>> >>> def __init__(self): >>> super(dict,self).__init__() >>> se

[Repoze-dev] RenderResponse objects

2010-04-06 Thread Chris Withers
Chris McDonough wrote: >> Also, how come you put response attributes on the request when using a >> renderer? >> >> How about a RenderResponse object: >> >> class RenderResponse(dict): >> >> def __init__(self): >> super(dict,self).__init__() >> self.content_type = 'the default' >> self.header_list