http://permalink.gmane.org/gmane.comp.web.zope.grok.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6370 [..] comment from a lurker: Browsing through the tutorial I've seen that the important topic of persisting mutable objects is covered (good!) by using the '_p_changed' magic but I just want to ask the question whether people consider this to be best practice? At least I switched to using the persistent types that the ZODB provides for exactly that reason (PersistentList and PersistentMapping). Maybe this could be mentioned somewhere in the tutorial? (unless it is and I just messed it) Raphael Raphael Ritz 2008-10-07T10:49:32 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6369 Well, Brandon's answer got out a little quicker than mine, but since this is a very common question and the distinction between class attributes and object attributes is easily blurred since Python will look for class attributes in the absence of an object attribute during object attribute look-up, I wrote up my explanation in documentation: http://grok.zope.org/documentation/how-to/understanding-default-values-for-object-database/view This explanation is still a bit verbose. Brandon, feel free to go through and make the important bits in **bold** text :) It might also be nice to expand it with a discussion on properties and FieldProperties ... and to make the text not-so dry I could upload some photos taken from my excellent shoe collection ... :) http://www.flickr.com/photos/kteague/782104678/ Kevin Teague 2008-10-04T23:12:29 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6368 The difference you are seeing has do to with how Python works. Roughly speaking, when you ask an object for its "foo" attribute with something like "print mysample.foo", it looks: - For a "foo" attribute on the "mysample" instance. - For a "foo" attribute on the class "Sample". - For a "foo" attribute on all the parent classes of "Sample". - For a "foo" attribute on the metaclass. And Python returns the first value discovered. So, when you say: class Sample(grok.Application, grok.Container): text = 'default text' you are creating a "safety" or "fall-through" value that will be returned if an object is asked for its attribute "text" but does not actually have one. So: 'default text' 'not the default text' You see? Until the "s" instance is given its own value for "text", it uses the default one stored up in the class. I apologize if my using capital letters looks offensive, but I'm really just trying to be very, very clear: - The variable "text" on the CLASS does NOT get persisted or s Brandon Craig Rhodes 2008-10-04T22:03:27 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6367 * Randomised keys have better efficiency when filling a B-Tree. You need to check that the randomly generated key does not already exist. * Store the length with a BTrees.Length.Length and increment/decrement as you add/delete. Laurence Laurence Rowe 2008-10-04T21:57:44 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6366 I got BookShelf from: svn://svn.zope.org/repos/main/grokapps/BookShelf It didn't have a bookstrap.py, so I put one in. It had bootstrap.cfg. I am new to buildouts, is this ok to do? When I ran this: python2.4 bootstrap.py I got this: ---------------------------------------- Creating directory '/Users/john/sameple_grok/grokapps/BookShelf/bin'. Creating directory '/Users/john/sameple_grok/grokapps/BookShelf/parts'. Creating directory '/Users/john/sameple_grok/grokapps/BookShelf/ develop-eggs'. Generated script '/Users/john/sameple_grok/grokapps/BookShelf/bin/ buildout'. Develop: '/Users/john/sameple_grok/grokapps/BookShelf/.' Develop: '/Users/john/sameple_grok/grokapps/BookShelf/.' While: Installing. Getting section eggbasket. Error: The referenced section, 'eggbasket', was not defined. pb:~/sameple_grok/grokapps/BookShelf john$ ./ pb:~/sameple_grok/grokapps/BookShelf john$ svn infoPath: . URL: svn://svn.zope.org/repos/main/grokapps/BookShelf Repository Root: svn://svn.zope.org/repos/main Re John de la Garza 2008-10-04T21:49:09 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6365 I'm making an app that has polls for voting... When I make a Poll object to I have to create an ID so I can find it again. I'm comming froma RDBMS background and am wondering if there are any articles that would helpl me transistion. For example should the ID be the last object id + 1? I saw some sample code that kept the objects in a list then just got the length of the list, but if items are deleted then using the len as the ID could be trouble (not unique).... any feed back would be apprecitated. I've read intro to ZODB (Jim Fulton) but it doesn't mention deleting John de la Garza 2008-10-04T20:54:48 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6364 In the tutorial the first demo of persistent objects did this: class Sample(grok.Application, grok.Container): text = 'default text' Then as the tutorial goes on they do this: class Sample(grok.Application, grok.Container): def __init__(self): super(Sample, self).__init__() self.list = [] Why don't we have to add the string the same way as the list? I mean the variable text gets persisted between restarts of the server, but if we added a list by doing this: class Sample(grok.Application, grok.Container): list = [] it would be reset to empty every time we restarted the server I'd expect text='default text' to have the same resetting as list=[] What am I over looking? John de la Garza 2008-10-04T17:21:14 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6363 On Oct 1, 2008, at 6:56 AM, Godefroid Chapelle wrote: I've put the files in there (using the root account, then chown'ed them to jw.jw). The PDF links are currently missing for the Reference docs and complete Documentation PDF, because I took them out when I was working on the docs (since I was having trouble building these on the Mac ...)((I'd also intended to make the PDF links a bit nicer and perhaps put them in a sidebar-type area but haven't got around to it yet)) I'll look at building the PDF on the server - if that works, then I can update the release instructions for building the docs. Kevin Teague 2008-10-01T14:45:06 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6362 I just tried to do it. Unfortunately, even though I have ssh access, I cannot write to the given directory, it's under jw ownership/group... Godefroid Chapelle 2008-10-01T13:56:33 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6361 Hey Kevin, Thanks for integrating the Plone site with the official documentation, I'm really happy that this is done now! Regards, Martijn Martijn Faassen 2008-10-01T13:23:38 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6360 _______________________________________________ Grok-dev mailing list Grok-dev< at >zope.org http://mail.zope.org/mailman/listinfo/grok-dev Uli Fouquet 2008-10-01T12:56:13 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6359 _______________________________________________ Grok-dev mailing list Grok-dev< at >zope.org http://mail.zope.org/mailman/listinfo/grok-dev Yvan Strahm 2008-10-01T11:45:48 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6358 I've just updated the Grok Documentation home page (http://grok.zope.org/documentation/ ) so that there are a number of lnks into the Official Grok Documentation. I deleted the old, outdated copies of the docs which were inside Plone (so people won't accidentally update the wrong resource), as well as put an Apache rewrite rule in place to preserve any old links. I took a quick pass on the documentation home page at separating the Official Grok Doc links from the Community Grok Doc links - maybe this could be a little cleaner, but it's good enough for me :P We are also running on Plone 3.0.5 ATM - I'm running a dev sandbox site on 3.1 and it all seems quite happy so I'll probably update the production site soon-ish. I don't know about all this Python 2.5 stuff though - this is really going to make my "Python 2.4 for Life" tattoo look kind of silly. Kevin Teague 2008-10-01T07:21:01 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6357 For examples, also definitely look at the stuff under 'grokapps': svn://svn.zope.org/repos/main/grokapps/<someapphere>/trunk Regards, Martijn Martijn Faassen 2008-09-30T15:57:01 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6356 Hm, I admit I missed Michael's message, so that can't have helped. We saw the branch for paste support when doing the release but I figured it was a lot of changes to drop in all of a sudden. I think we already got the alternative i18n recipes in there? At least *some* alternative i18n messages made it into the trunk - is this another set again? I do see a recent branch that seems to be about supplying grokproject with an alternative release URL. I agree with JW we could make another release after the merge without waiting for a full Grok release. Note though that I *would* like to mention 'paste support' as a major new feature of the *next* version of Grok though. :) I think we need to work a bit on the coordination around grokproject. I'll try to pay better attention to what's up myself. Regards, Martijn Martijn Faassen 2008-09-30T13:24:08 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6355 Hey, rogererens wrote: No, you could start using the grokcore.* pieces in Zope 3 right away; grokcore.component is the easiest. You could use them for new stuff. If you want to convert the old stuff to use Grok you'd need to rewrite the code slightly, but there's no need to do this. This wouldn't entail using all of Grok, but much of Grok is now spun off into those pieces and the explicit aim is for them to be reusable in non-Grok Zope 3 and Zope 2 applications. Nope, this isn't there yet. People have spoken about adding one but it hasn't happened yet. Regards, Martijn Martijn Faassen 2008-09-30T13:09:26 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6354 On Tue, Sep 30, 2008 at 12:34 PM, Philipp von Weitershausen <philipp< at >weitershausen.de> wrote: Ok. I'll add it to the versions.cfg on the grok-trunk then. With the fixed grok-0.14.cfg file, yes, that's how it now works. regards, jw Jan-Wijbrand Kolman 2008-09-30T11:04:16 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6353 El 30 Sep 2008, a las 12:26 , Jan-Wijbrand Kolman escribió: Cool, thx. I don't think we should look at versions.cfg as a list of dependencies that Grok has. Rather, I think it's a known-good set description and grokui.admin simply is part of the whole set of software, *especially* if grokproject adds it to the sandbox automatically. Sure, preferrably by means of Grok's version.cfg (which is how it already works, right?). Philipp von Weitershausen 2008-09-30T10:34:45 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6352 http://grok.zope.org/releaseinfo/grok-0.14.cfg is fixed now. Interesting point... It is not a dependency of Grok iteself. I would thus expect it not to be in the versions.cfg of Grok. Should grokproject add the grokui.admin versions spec in the versions.cfg file that is created for a new project? regards, jw -- Jan-Wijbrand Kolman Jan-Wijbrand Kolman 2008-09-30T10:26:20 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6351 _______________________________________________ Grok-dev mailing list Grok-dev< at >zope.org http://mail.zope.org/mailman/listinfo/grok-dev Uli Fouquet 2008-09-30T09:40:18 http://permalink.gmane.org/gmane.comp.web.zope.grok.devel/6350 Also, grok 0.14's version list [1] doesn't include grokui.admin. So effectively grokui.admin is a free-floating dependency and not version-pinned. IMHO this should be fixed asap. [1] http://grok.zope.org/releaseinfo/grok-0.14.cfg Philipp von Weitershausen 2008-09-30T08:15:17 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.web.zope.grok.devel