May 2008 - Zope-Dev - Zope lists

Zope3 on Google AppEngine
by Jodok Batlogg 02 Jun '08

02 Jun '08

Hi, Next week Lovely will be sprinting in New York/San Francisco to get the Zope3 framework and the first applications running on Google AppEngine. You’re welcome to join us. Google AppEngine is a perfect match to the transition we at Lovely Systems made during the last 12 month in “stealth mode”. We’re using heavily WSGI and are replacing ZODB within most of our applications. Tomorrow we’re leaving to New York visiting our friend reco. dobee and I will be working on getting the component architecture running on AppEngine. Later next week we’ll fly to San Francisco to attend Google I/O and get even more insight to the technology. We’re open to release lovely.nozodb and the related components in near future, as usual - just some polishing missing… Please drop me a note (jodok(a)lovelysystems.com, batlogg on skype/AIM) or give me a call (+43 664 9636963) if you want to join us. jodok -- Lovely Systems, Partner phone: +43 5572 908060, fax: +43 5572 908060-77 Schmelzhütterstraße 26a, 6850 Dornbirn, Austria

9 19

zope.sqlalchemy, integration ideas
by Martijn Faassen 02 Jun '08

02 Jun '08

Hi there, Today I had a discussion with Jasper Spaans about how to go about improving megrok.rdb, Grok's relational database integration which aims to integrate Grok with SQLAlchemy. We started developing megrok.rdb at the Grokkerdam sprint a few weeks ago. We reread the discussion surrounding zope.sqlalchemy for ideas on how to go about integration and configuration. I think these discussions reach wider than just Grok's concerns. Note that I'm not proposing we fold any of these ideas into zope.sqlalchemy itself, which should remain as free of policy as possible; it could become (yet another) extension. Let me run our current thinking by the list. What would be nice in Zope applications (and we think would be good for Grok) would be per-instance database configuration. That is, we want to be able to install multiple instances of the same application and then configure each of them with a different database URN and it should all work, each talking to their own database. Michael Bayer's suggestion involves the use of scoped sessions. He proposed the following code: Session = scoped_session() # start of request engine = get_appropriate_engine() Session(bind=engine) try: # do request finally: Session.remove() Let's go through the steps. First it makes a scoped session object, it then configures it with the right engine at the start of the request (it can do this on a per-class level), and then at the end of the request it removes the Session again, which results in the actual session being closed. Our get_appropriate_engine() would probably look the engine up as a local utility, as Laurence suggested. There is a bit of question about engine configuration, though. If we want to support the use case of looking up the engine URL in a persistent datastore (for instance one URL per location), we have a question of ordering. We cannot do it too early; at the start of the transaction there isn't a ZODB yet to talk to so we can't look up a local utility. We can try doing it just in time: _Session = scoped_session() def Session(*args, **kw): engine = get_appropriate_engine() _Session.bind(bind=engine) return _Session(*args, **kw) Here get_appropriate_engine() could do a component.getUtility() and look up the engine for us, possibly in an application-local way. There's still the question of how this engine got configured in the first place. How does it know the database URL? How does the engine get created after the database URL is known (this might be quite late in the game; it could be stored in the ZODB). It then starts to look more and more attractive to do something similar like collective.lead's IDatabase utility, which can be stored persistently in the ZODB and has a getEngine() method which actually gets the engine (creating it if necessary). If we use sqlalchemy.ext.declarative, we also need to make the declarative extension of SQLALchemy load up the tables at the right point in time. We would also like a way to hook into matters and register some of our own tables and mappers manually. We figured perhaps the utility could fire an event that you can then write a handler for. This way there's less need to subclass the utility just to change some configuration (this is what collective.lead currently requires you to do). If a persistent local utility is in play, it shouldn't fire the configuration event during its own creation, as that would mean it'd only be fired once ever. We want to fire it just after engine creation. I guess the database utility can remain quite simple. Its main tasks would be: * allow access to the engine (creating it the first time) * fire the event for additional configuration when the engine is first created * maintain or somehow obtain the database URL. This could be retrieved from the ZODB if it's a local utility, or it could be hardcoded into a global utility, or it could be retrieved from some config file by a global utility. We could have an expanded variety which also configures things using the SQLAlchemy declarative extension. We still have the question of the 'remove()' bit in Michael's code. We looked at ScopedSession's remove() method, and it looks like it removes the session from the thread-local storage, and it actually closes the session. Closing the session should be taken care of: zope.sqlalchemy's integration with Zope's transaction machinery will close the session. What about the registry cleanup that remove() appears to do? Is this currently being done by zope.sqlalchemy? Should it be? Anyway, a whole lot of abstract talk. I still hope to get some feedback on this. Regards, Martijn

7 26

Re: SVN: zc.datetimewidget/trunk/ prepare for a sanitizing release, thanks to a wild svn-based release
by Tres Seaver 31 May '08

31 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fred Drake wrote: > On Thu, May 29, 2008 at 12:11 AM, Fred L. Drake, Jr. <fdrake(a)gmail.com> wrote: >> Log message for revision 87005: >> prepare for a sanitizing release, thanks to a wild svn-based release > ... >> CHANGES >> ======= >> >> +0.6.1 (2008-05-29) >> +------------------ >> + >> +Unchanged from 0.5.2, but released with a new version number thanks to a >> +package with an 0.6.1dev-rBFN revision found in the wild. > > This is disgusting. We're going to have to all avoid placing those > nasty releases with Subversion revision numbers in any public > repositories. I'm sure I'm among the guilty, but... we've gotta do > better. Amen. <dead-horse beat="sans-merci"> If we quit keeping "guessed nex version number" on the trunk (or on release branches), such a release would be harder to make. Also, we wouldn't have to make unneeded changes to setup.py on the trunk. </dead-horse> Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFIQYqD+gerLs4ltQ4RAvu8AKCXDHKeIJm9cD5HGjOPwPd9SdqctQCXdZXF gTfE3sEsazUJdDJqO48F3A== =Ltvx -----END PGP SIGNATURE-----

2 1

Re: SVN: relstorage/branches/1.1/MANIFEST apparently, setuptools uses SOURCES.txt instead of MANIFEST
by Tres Seaver 31 May '08

31 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shane Hathaway wrote: > Log message for revision 87068: > apparently, setuptools uses SOURCES.txt instead of MANIFEST It generates that file in the .egg-info subdirectory when building an 'sdist' from a VCS checkout (subversion or another with the extension for finding files under version control). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIQYwQ+gerLs4ltQ4RAtjqAKChfjhSZq43UL6zxZzUatdiGln48QCfVFX6 rwibQgcylVfY0ShRVh42gq8= =BitZ -----END PGP SIGNATURE-----

2 1

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 31 May '08

31 May '08

Summary of messages to the zope-tests list. Period Fri May 30 11:00:00 2008 UTC to Sat May 31 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri May 30 21:07:45 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009634.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri May 30 21:01:29 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009630.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri May 30 21:03:04 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009631.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri May 30 21:04:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009632.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri May 30 21:06:15 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009633.html

1 0

Somebody needs to talk at EuropPython.
by Lennart Regebro 30 May '08

30 May '08

So, we need talks at EuropPython about both Repoze and Grok. I can't go, but I want to make sure *somebody* does. :) Hands up: Who is talking about Grok, and who talks about Repoze? :) Other super-cool Zope technologies that should be talked about? -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64

4 3

zope 3 component binaries for Python 2.5 on Windows
by Chris Withers 30 May '08

30 May '08

Hey Guys, So, we now have all the Zope 3 components and RestrictedPython working on Python 2.5. Where do I go to get windows binaries installers or similar for these? (ie: the C-components) If they don't exist yet, how do we go about getting them to exist? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 2

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 30 May '08

30 May '08

Summary of messages to the zope-tests list. Period Thu May 29 11:00:00 2008 UTC to Fri May 30 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu May 29 21:06:41 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009629.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Thu May 29 21:00:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009625.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu May 29 21:02:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009626.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu May 29 21:03:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009627.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu May 29 21:05:11 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009628.html

1 0

Zope2 porting Acquisition
by ranjith kannikara 29 May '08

29 May '08

Hello everyone, I came across an error in module Acquisition, while trying to port zope2 to python2.5. There was a discussion over the same topic in JAN-2008. In acquisition the wrapper compare is returning false irrespective of the parameters. >>> c = A() >>> b.c = c >>> b.c.d = c >>> b.c.d == c 1 >>> b.c.d == b.c 1 >>> b.c == c 1 here 1) b.c.d == c is returning false and 2) b.c.d == b.c returns 1 3) b.c == c returns false And the problem I stuck with was that in the comparisons 1 and 3 the function Wrapper_compare defined in _Acquisition.c is not even called. How a function (say Wrapper_compare) from a C-API is being called on reaching a line like >>> b.c.d == c .

2 2

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 29 May '08

29 May '08

Summary of messages to the zope-tests list. Period Wed May 28 11:00:00 2008 UTC to Thu May 29 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed May 28 21:05:41 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009624.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Wed May 28 20:59:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009620.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed May 28 21:01:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009621.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed May 28 21:02:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009622.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed May 28 21:04:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009623.html

1 0