Re: [Zope-dev] Using zope.proxy for read-only instances
On 22.12.2008 11:34 Uhr, Andreas Kopecky wrote: Hi, My first question regarding that would be: why use zope.proxy for it. Personally - not knowing what exactly you have in mind ofc - i'd use something along the lines of class Proxy(object): def __init__(self, obj): self.obj = obj def __getattr__(self, attribute): return getattr(obj, attribute) maybe add a check of the returned attribute is callable or so. Sorry, invalid answer. That's what zope.proxy is designed for and I am trying to get it working (unlikely it has no documentation and the unittest don't give me much insight). In addition: your code won't work since you must refer to self.obj not 'obj' within __getattr__. And using self.obj will lead to an infinite recursion. I also think that __getattr__() is not used by new-styles classes. Instead you need to override __getattribute__(). Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Using zope.proxy for read-only instances
Hi, Well if it's invalid i won't bother with it but say: - i forgot a self - that is true - if added it does NOT loop infinitely - its not my example its taken from python cookbook - it works with new style objects - __getattribute__ does something different But frankly i was only trying to understand better what you want to do and be helpful - which obviously is neither needed nor wanted. Andreas Sorry, invalid answer. That's what zope.proxy is designed for and I am trying to get it working (unlikely it has no documentation and the unittest don't give me much insight). In addition: your code won't work since you must refer to self.obj not 'obj' within __getattr__. And using self.obj will lead to an infinite recursion. I also think that __getattr__() is not used by new-styles classes. Instead you need to override __getattribute__(). Andreas signature.asc Description: OpenPGP digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.dottedname and releases
On 02.12.2008 22:23 Uhr, Chris Withers wrote: Hi All, How do I go about getting myself added to the Zope 3 packages so I can do releases to PyPI? (my PyPI username is chrisw) Best you ask one of the related package maintainers (PyPI shows their names at the bottom) in private. Unfortunately this must happen with every individual package since PyPI has group support. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion merge tracking
On 13.11.2008 14:42 Uhr, Benji York wrote: I'd like for us to disallow pre-1.5 Subversion clients from making commits starting one year from now (or sooner if there is consensus). +1 - six months should be enough for the transition. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] PyPI mirrors available
Hi there, I would like to point out that we have started the PyPI replication project some months ago during the Blackforest sprint: http://www.openplans.org/projects/pypi-mirroring/project-home As an outcome we are now able to provide in phase one of the project some mirrors of PyPI index. Currently we have three mirrors up and running and some more mirrors will join the project soon. Right now we provide all packages of PyPI that are directly hosted on PyPI (no packages with external download URLs). This project should bring a lot of ease to buildout users because PyPI is no longer a single-point-of-failure. Currently you have to choose a PyPI mirror manually. For the next project phase we think about a smarter mirror selection mechanism that is more transparent to setuptools and zc.buildout. Suggestions and further support in terms of hardware resources and bandwidth are highly appreciated. Credits go to Josip Delic and Gottfried Ganssauge of Haufe Mediengruppe for their contributions to the original codebase of z3c.pypimirror and to Daniel Kraft of D9T for being doing most of the coding of the package. Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [EMAIL PROTECTED] linking to svn.zope.org
Hi there, I have package with a dependency to zope.schema. Setuptools tries to install zope.schema from svn.zope.org (which is currently down) instead of fetching the sdist/egg directly from PyPI. [EMAIL PROTECTED]:/home/develop/repository/svn.haufe.de/svnep/HaufeComponents/haufe.hrs.configuration/trunk python2.4 setup.py test running test Checking .pth file support in . /opt/python-2.4.4/bin/python2.4 -E -c pass Searching for zope.configuration Reading http://pypi.python.org/simple/zope.configuration/ Best match: zope.configuration 3.4.0 Downloading http://pypi.python.org/packages/source/z/zope.configuration/zope.configuration-3.4.0.tar.gz#md5=c0822830199d6bf4f1fdd0007e78a9dc Processing zope.configuration-3.4.0.tar.gz Running zope.configuration-3.4.0/setup.py -q bdist_egg --dist-dir /tmp/easy_install-sF3bKJ/zope.configuration-3.4.0/egg-dist-tmp-xinGS_ Installed /home/develop/repository/svn.haufe.de/svnep/HaufeComponents/haufe.hrs.configuration/trunk/zope.configuration-3.4.0-py2.4.egg Searching for zope.component Reading http://pypi.python.org/simple/zope.component/ Best match: zope.component 3.5.1 Downloading http://pypi.python.org/packages/source/z/zope.component/zope.component-3.5.1.tar.gz#md5=006c43ad77ed4982e49c07f6e65b68a2 Processing zope.component-3.5.1.tar.gz Running zope.component-3.5.1/setup.py -q bdist_egg --dist-dir /tmp/easy_install-q05rQz/zope.component-3.5.1/egg-dist-tmp-rmLhTl Installed /home/develop/repository/svn.haufe.de/svnep/HaufeComponents/haufe.hrs.configuration/trunk/zope.component-3.5.1-py2.4.egg Searching for zope.interface Reading http://pypi.python.org/simple/zope.interface/ Best match: zope.interface 3.5.0 Downloading http://pypi.python.org/packages/source/z/zope.interface/zope.interface-3.5.0.zip#md5=478d05add7cd7faf25a2fd880a739ddb Processing zope.interface-3.5.0.zip Running zope.interface-3.5.0/setup.py -q bdist_egg --dist-dir /tmp/easy_install-Pxwaxm/zope.interface-3.5.0/egg-dist-tmp-tkl-Zv Installed /home/develop/repository/svn.haufe.de/svnep/HaufeComponents/haufe.hrs.configuration/trunk/zope.interface-3.5.0-py2.4-linux-x86_64.egg Searching for zope.event Reading http://pypi.python.org/simple/zope.event/ Best match: zope.event 3.4.0 Downloading http://pypi.python.org/packages/2.4/z/zope.event/zope.event-3.4.0-py2.4.egg#md5=79af17fa33ec85de3894802e9bb72277 Processing zope.event-3.4.0-py2.4.egg creating /home/develop/repository/svn.haufe.de/svnep/HaufeComponents/haufe.hrs.configuration/trunk/zope.event-3.4.0-py2.4.egg Extracting zope.event-3.4.0-py2.4.egg to /home/develop/repository/svn.haufe.de/svnep/HaufeComponents/haufe.hrs.configuration/trunk Installed /home/develop/repository/svn.haufe.de/svnep/HaufeComponents/haufe.hrs.configuration/trunk/zope.event-3.4.0-py2.4.egg Searching for zope.schema Reading http://pypi.python.org/simple/zope.schema/ Reading http://svn.zope.org/zope.schema The simple index for zope.schema declarse this dependency to svn.zope.org: http://pypi.python.org/simple/zope.schema Can we please fix this? Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope3-Users] Will new release of zope3 include TSL/SSL in zope.sendmail
On 06.11.2008 10:31 Uhr, Jayarajan Jn wrote: Hi ALL, When will the next release of zope3 will be? will there be a zope3.4c2? By the way i wish to know whether next release will include the latest release of zope.sendmail which has TSL/SSL feature. I have noticed that last release, zope3.4c01 was on 31 Jan 2008. http://www.zope.org/Products/Zope3/3.4.0c1 And the zope.sendmail has trunked SSL/TLS feature on 19th Aug 2008. You mean 2007! http://svn.zope.org/zope.sendmail/trunk/src/zope/sendmail/mailer.py?rev=92747sortby=logview=log http://svn.zope.org/zope.sendmail/trunk/src/zope/sendmail/mailer.py?rev=92747sortby=logview=log So its obvious that zope3.4c01 don't have SSL/TLS feature in its zope.sendmail. And i have seen some other many other fixes in the zope.sendmail that enables it to work well with gmail and similar Those changes should be at least in the latest zope.sendmail 3.5.X releases. In the time of components and buildout you should be able to upgrade the zope.sendmail dependency easily yourself. -aj begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Event for system shutdown?
Is there an event in Zope 3 indicating a Zope server shutdown? Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 features
On 31.10.2008 18:36 Uhr, Tres Seaver wrote: In that case Plone will neither use 2.11 nor 2.12 but go straight for a Zope 2.13 including Python 2.6. A major release every six month would be desirable for us in that case. Right now I don't see anyone, who would be using those releases. If those people exist, please speak up. Plone isn't the only consumer of Zope2, although it is clearly the biggest one. Tres, what are you current needs and requirements (properly based on your Repoze project)? I agree that Plone isn't the only consumer but I wonder if all other consumers really have the need jumping on every train passing the train station. We have the luxury with four supported Zope 2 major release. I don't want a fith right now unless we are having very good reasons. I think we need to move toward 2.6 compatibility, but we need to give people a migration path, largely because 2.6 will break 3rd party apps in ways that 2.4 doesn't warn about. So, I would like to see a 2.12 which is explicity about bridging first to 2.5 support: that way, people get a chance to clean up the new deprecation warnings (e.g., for the 'with' keyword, etc.). If ZODB 3.9 lands in time, then a near-term release of Zope 2.12 could be this consolidation release (2.5 support, new ZODB, including maybe RelStorage, other work done to date). Good points - let's head for Python 2.5 support in Zope 2.12. We could the focus trunk development on 2.6 compatibility, with the goal of releasing a 2.13 no later than Q3 next year. ACK In the meantime, we can acknowledge that 2.8 and 2.9 are retired (no future work except maybe important security fixes), +1 and announce that 2.10 will be retired after the 2.12 release: We have to care about 2.10 for a longer period because of the large amount of Plone 3.X installations. I don't see a win there, myself: I'd rather make an easier transition for 2.12 than spend resources on a potentially-destabilizing backport of 2.5 compatibility. ok - the goals for the 2.12 release should be documented somewhere (your ideas, see above + the Hanno's proposals). Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 features
On 04.11.2008 18:41 Uhr, Hanno Schlichting wrote: Andreas Jung wrote: On 04.11.2008 18:19 Uhr, Jens Vagelpohl wrote: On Nov 4, 2008, at 13:59 , Hanno Schlichting wrote: If I'm not mistaken there was something about every release being supported two years after its initial release in those discussions. But time went on, we haven't sticked to a time-based release schedule and those policies haven't been written down or been followed. 2 years sounds fine to me. We must be careful with such time-based policies because of the installed (Plone) installations. Zope 2.8 and Zope 2.9 are definitely dead horses. We must support Zope 2.10 (which is a pretty good release) as long as Plone 3.X is supported. Let's say Plone 4 becomes mature in late 2009 and widely used by 2010...then we can talk about getting rid of 2.10 (except the Plone releases= 3.2 would adopt Zope 2.11 or 2.12 at some point but I haven't heard that this is on the agenda for the next Plone 3.X releases). There are currently no plans to switch to a new Zope version for neither Plone 3.2 or 3.3. There are no plans or even a preliminary roadmap for a Plone 3.4 release yet. It would be something like a summer or autumn 2009 release. I think we will have some kind of feedback loop here, which makes it a good idea from a Plone perspective to upgrade to at least Zope 2.11 for Plone 3.4, as Zope 2.10 by whatever date that will be, is going to be an old an rather unmaintained release. So sticking to support 2.10, 2.11 and trunk right now and phasing out 2.10 sometime next year, sounds like a good roadmap to me. ok,ok - I'll stop caring to much about the Plone world :-) Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zc.relationship 1.0.2 typo bug
On 03.11.2008 5:22 Uhr, Rudá Porto Filgueiras wrote: I found a typo bug in zc.relationship 1.0.2 (pypi and svn tag 1.02). It's fixed in trunk but not backported and plone.app.relations-1.0b2 unittest found this bug. Bugs and patches must be reported to the Launchpad bugtracker. A mailinglist is not the right place for archiving bug reports. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 features
On 30.10.2008 21:41 Uhr, Tres Seaver wrote: From a Zope perspective 2.11 should have had Python 2.5 support, but nobody cared enough to make it happen. We can support Python 2.4 and 2.5 alone in Zope 2.12 and release it in the next months. We should do a 2.12 very soon (before year end, likely), and it should retain 2.4 compatibility. What are our current needs for having a Python 2.5 compatible Zope 2 version (except it would be nice for having one). Being in sync with the latest Python 2.6 version is much more important than jumping on a half-dead horse like Python 2.5. Introducing another major Zope release with very little new exciting feature does not make sense to me at the time right now. It just adds another major release we have to support (we already support 2.9-2.11 and a bit 2.8) + the complexity for supporting two different Python versions for Zope 2.12. I am open to arguments but I really want to see why we need Zope 2.12 with Python 2.5 support this year (or at least very soon). In that case Plone will neither use 2.11 nor 2.12 but go straight for a Zope 2.13 including Python 2.6. A major release every six month would be desirable for us in that case. Right now I don't see anyone, who would be using those releases. If those people exist, please speak up. Plone isn't the only consumer of Zope2, although it is clearly the biggest one. Tres, what are you current needs and requirements (properly based on your Repoze project)? I agree that Plone isn't the only consumer but I wonder if all other consumers really have the need jumping on every train passing the train station. We have the luxury with four supported Zope 2 major release. I don't want a fith right now unless we are having very good reasons. Keeping an orderly succession of releases with good compatibility is important for the whole ecosystem (frankly, Plone should be willing to move to newer Zope versions even in a second dot release, but that is another debate). This is already the case (more or less). In my experience strategic consumers are possibly more interested in slower release cycles instead of getting major releases very often. I doubt that much people care about using Python 2.4 or Python 2.5 (I personally don't care much about Python 2.5)..other feature likes e.g. a new ZODB version with some cool new feature is more important for justifying a new major release. If Sidnei should be successful with making Plone 2.11 compatible with Python 2.5 then we might add inofficial support for Python 2.5 to the current Zope 2.11 release...but as stated earlier I would like to see some arguments why Python 2.5 compatiblity is necessary now and why Python 2.6 support at some time next year would not be good enough. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 features
On 30.10.2008 18:01 Uhr, Lennart Regebro wrote: On Thu, Oct 30, 2008 at 15:03, Hanno Schlichting[EMAIL PROTECTED] wrote: - Reconsider getting rid of ZClasses +1 I have some things I want to do when it coms to timezones, so I would like to mentally prepare me for about what release date we are talking about here, so I know when I have to do this. Could be a good xmas entertainment for example. :) I think there is need for setting a release date right now - I know that this a total contradiction to our former approach with time-based releases. The current 2.11 codebase is pretty much in sync with the latest Zope web-components. Since the Zope 2 development is in parts driven by the Plone community and their needs, it does make sense keeping the development in some way in sync with the Plone 4 release. Not much to be added to the feature set as proposed by Hanno - except a dedicated +1 for getting rid of ZClasses. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZCatalog caching with memcached
On 27.10.2008 17:18 Uhr, Rudá Porto Filgueiras wrote: On Mon, Oct 27, 2008 at 12:33 PM, Andreas Jung[EMAIL PROTECTED] wrote: On 27.10.2008 16:28 Uhr, Rudá Porto Filgueiras wrote: I will sugest a package called zope.memcached (like zope.sqlalchemy does for SQLAlchemy integration). That way any application who need to talk memcached can do it with out loose atomicit. I don't see a particular reason for creating a new package for here. Extend lovely.memcached and your done. There is not much need for scattering tiny functionalies into two modules here. The module world is already complicated enough. If lovely,memcached alredy is safe when some Exception is raised, discard my sugestion. It's also compatible with zope2? We are using it together with our cache tool I mentioned earlier with Zope 2.8.1. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Backporting some Python 2.5/2.6 fixes
On 27.10.2008 18:36 Uhr, Sidnei da Silva wrote: Hi all, I would like to propose backporting some of the fixes needed for Python 2.5 and 2.6 all the way down to Zope 2.10. The fixes that would be backported would only be those that deal with syntax changes (eg: 'with' and 'as' keyword being used as variables, relative imports) and some C-level changes, to Acquisition and zope.app.container if I recall. I would *not* backport changes to RestrictedPython because those are actually features (support for newer versions of Python) as opposed to the other changes, which are just 'bugfixes' IMHO. Why do we need these backports on the current maintenance branches? Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Backporting some Python 2.5/2.6 fixes
On 27.10.2008 18:55 Uhr, Sidnei da Silva wrote: On Mon, Oct 27, 2008 at 3:42 PM, Andreas Jung[EMAIL PROTECTED] wrote: Why do we need these backports on the current maintenance branches? They are small cleanups that could potentially allow someone to run Python 2.5 or 2.6 if they really really really wanted to, but note should be made that it would be completely and utterly unsupported. Please create branches first and then lets review the changes. What is the state of the compatability of Z3 modules with Python 2.5/2.6 as used in Zope 2.10/2.11? Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Make Zope2 smaller
On 26.10.2008 16:37 Uhr, Hanno Schlichting wrote: Implementation This is not yet implemented but should be quite easy. Figuring out the exact packages which are required by Zope 2 is to be done. General +1 on getting rid of the dependencies which are actually no dependencies. However I have the feeling that there possibly only a small number of packages that are really have no dependency to Zope 2. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZCatalog caching with memcached
On 26.10.2008 18:43 Uhr, Roché Compaan wrote: On Sat, 2008-10-25 at 09:20 +0200, Hedley Roos wrote: I suspect specific indexes are just performing suboptimally and needs to be improved. ExtendPathIndex in Plone seems to be one of them. Path indexes and fulltext indexes have a much more complicated implementation compared to field or keyword indexes. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZCatalog caching with memcached
On 26.10.2008 19:05 Uhr, Roché Compaan wrote: On Sun, 2008-10-26 at 18:50 +0100, Andreas Jung wrote: On 26.10.2008 18:43 Uhr, Roché Compaan wrote: On Sat, 2008-10-25 at 09:20 +0200, Hedley Roos wrote: I suspect specific indexes are just performing suboptimally and needs to be improved. ExtendPathIndex in Plone seems to be one of them. Path indexes and fulltext indexes have a much more complicated implementation compared to field or keyword indexes. I know, and this alone makes a good argument for caching at catalog level. In our case we used membrane, which makes an excessive amount of catalog queries when looking up users so some level of caching was essential. First caching is good thing :-) But how about the following issue: CMF/Plone inject additional subqueries for expires/effective/typesAndRoles. At least the security related aubqueries make a cached catalog result very specific to a particular user. That seems to be very ok for a site with lots of anonymous users - it might be an issue with lots of authenticated users. It might be necessary to add some kind of intelligence to decide what to cache and what not. I don't think it does not make sense to cache the result of a fulltext search. I am just thinking if it would make sense to cache on the index level instead of catalog level? So you could for example cache expensive index queries (path index) and combine them with uncached index which are supposed to be fast..however such decisions require detailed mesurements on real systems. One other thing concerning memcached: there is obviously a limit to 1MB for data you can store as a value. We have not found an obvious way for increasing this limit other by patching the memcached sources. We came up with an implementation where data 1MB is split up into individual junks (we have a dedicated set_huge(), get_huge()) implementation. Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZCatalog caching with memcached
On 25.10.2008 8:48 Uhr, Hedley Roos wrote: The usual Plone catalogs (portal_catalog, uid_catalog, reference_catalog and membrane_tool) all run above 90% hit rate if the server is up to it. portal_catalog is invalidated the most so it fluctuates the most. If the server is severely underpowered then catalogcache is much less effective. portal_catalog hit rates will degrade over time. This is the situation I'm currently facing with on one site, but more servers will fix that. It's quite easy to benchmark / load test with funkload. What I've found is that memcached is very light on CPU, but if the Zope processes are constantly using all CPU it is starved and runs into trouble. As long as you avoid that case (which would be fatal without catalogcache in any case) then everything works perfectly. Have you measures the time needs for some standard ZCatalog queries used with a Plone site with the communication overhead with memcached? Generally spoken: I think the ZCatalog is in general fast. Queries using a fulltext index are known to be more expensive or if you have to deal with large resultsets or complex queries. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZCatalog caching with memcached
On 25.10.2008 14:53 Uhr, Hedley Roos wrote: I'd love if this wouldn't be a monkey patch. So would I, but I couldn't find another way in this case. Also, there is nothing that makes this integrate correctly with transactions. Your cache will happily deliver never-committed data and also it will not isolate transactions from each other. I patched 4 methods - clear, search, catalogObject, uncatalogObject. Method clear is the simplest one - I simply flush the cache. Methods catalogObject and uncatalogObject both invalidate the cache. Should the transaction fail later the only drawback is that you threw a few things out of the cache. They'll soon be re-entered by subsequent searches. Using a DataManager is likely the better and more safe choice. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] use new() function of md5
On 21.10.2008 12:33 Uhr, milind jagtap wrote: when i tried to use hash =md5.new() in (script)python zope .it gives me an error as you are not authorized to use new in this context . If you have any idea regarding hot to resolve this pls help me. FAQ http://plone.org/search?SearchableText=allow_module -aj begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.container won't compile
On 20.10.2008 15:45 Uhr, Tres Seaver wrote: Did you look at the include' directories? $ svn propget svn:externals $ZSVN/zope.app.container/tags/3.5.6/include persistent svn://svn.zope.org/repos/main/ZODB/trunk/src/persistent zope.proxy \ svn://svn.zope.org/repos/main/zope.proxy/trunk/src/zope/proxy $ svn propget svn:externals $ZSVN/zope.app.container/tags/3.6.1/include persistent -r 71248 \ svn://svn.zope.org/repos/main/ZODB/branches/3.7/src/persistent zope.proxy \ svn://svn.zope.org/repos/main/zope.proxy/trunk/src/zope/proxy Two observations: - - No released version should have 'trunk' externals for anything. - - The 3.5.6 version is pulling in a 'cPersistence.h' which has a '#include py24compat.h' in it. Of course, if everybody's just annoyed and wants to move on, I'll be happy to create another 3.6.2 release with Sidnei's fix in it. We should fix the externals for both 3.5.x and 3.6.x and re-release both. Can someone with zope-app-container zen will fix the mess and do new releases? Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.container won't compile
Tnx! Andreas On 21.10.2008 21:46 Uhr, Alexander J Smith wrote: I just tagged a 3.6.2 version with Sidnei's fix and pushed it to PyPI. However, the problem of depending on SVN 'trunk' externals is still present and will have to be addressed at some point. Alexander J Smith Software Engineer Zope Corporation On Oct 21, 2008, at 11:58 AM, Andreas Jung wrote: On 20.10.2008 15:45 Uhr, Tres Seaver wrote: Did you look at the include' directories? $ svn propget svn:externals $ZSVN/zope.app.container/tags/3.5.6/include persistent svn://svn.zope.org/repos/main/ZODB/trunk/src/persistent zope.proxy \ svn://svn.zope.org/repos/main/zope.proxy/trunk/src/zope/proxy $ svn propget svn:externals $ZSVN/zope.app.container/tags/3.6.1/include persistent -r 71248 \ svn://svn.zope.org/repos/main/ZODB/branches/3.7/src/persistent zope.proxy \ svn://svn.zope.org/repos/main/zope.proxy/trunk/src/zope/proxy Two observations: - - No released version should have 'trunk' externals for anything. - - The 3.5.6 version is pulling in a 'cPersistence.h' which has a '#include py24compat.h' in it. Of course, if everybody's just annoyed and wants to move on, I'll be happy to create another 3.6.2 release with Sidnei's fix in it. We should fix the externals for both 3.5.x and 3.6.x and re-release both. Can someone with zope-app-container zen will fix the mess and do new releases? Andreas lists.vcf___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.app.container won't compile
A buildout fails reproducable both on Mac and Linux...how is the guilty? Andreas -- Develop: '/Users/ajung/src/svn.zope.org/zopyx.smartprintng.core/trunk/zopyx.convert2' Unused options for buildout: 'download-directory'. Installing test. Getting distribution for 'zope.app.container'. In file included from src/zope/app/container/_zope_app_container_contained.c:64: src/zope/app/container/_zope_proxy_proxy.c:616: error: syntax error before 'wrap_length' src/zope/app/container/_zope_proxy_proxy.c:617: warning: return type defaults to 'int' src/zope/app/container/_zope_proxy_proxy.c:622: error: syntax error before 'Py_ssize_t' src/zope/app/container/_zope_proxy_proxy.c:623: warning: function declaration isn't a prototype src/zope/app/container/_zope_proxy_proxy.c: In function 'wrap_slice': src/zope/app/container/_zope_proxy_proxy.c:624: error: 'self' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c:624: error: (Each undeclared identifier is reported only once src/zope/app/container/_zope_proxy_proxy.c:624: error: for each function it appears in.) src/zope/app/container/_zope_proxy_proxy.c:624: error: 'start' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c:624: error: 'end' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c: At top level: src/zope/app/container/_zope_proxy_proxy.c:628: error: syntax error before 'Py_ssize_t' src/zope/app/container/_zope_proxy_proxy.c:629: warning: function declaration isn't a prototype src/zope/app/container/_zope_proxy_proxy.c: In function 'wrap_ass_slice': src/zope/app/container/_zope_proxy_proxy.c:630: error: 'self' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c:630: error: 'i' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c:630: error: 'j' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c:630: error: 'value' undeclared (first use in this function) error: Setup script exited with error: command 'gcc' failed with exit status 1 An error occured when trying to install zope.app.container 3.6.1.Look above this message for any errors thatwere output by easy_install. While: Installing test. Getting distribution for 'zope.app.container'. begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.container won't compile
On 19.10.2008 14:04 Uhr, Roger Ineichen wrote: Hi Andreas Betreff: [Zope-dev] zope.app.container won't compile A buildout fails reproducable both on Mac and Linux...how is the guilty? Same on windows with Python 2.4. I think this is a Python 2.4 to Python 2.5 migration issue and not platform dependent. Are you using Python 2.4? Sure. If someone made Python 2.4 incompatible changes then they have to reverted :- Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.container won't compile
On 19.10.2008 14:14 Uhr, Andreas Jung wrote: On 19.10.2008 14:04 Uhr, Roger Ineichen wrote: Hi Andreas Betreff: [Zope-dev] zope.app.container won't compile A buildout fails reproducable both on Mac and Linux...how is the guilty? Same on windows with Python 2.4. I think this is a Python 2.4 to Python 2.5 migration issue and not platform dependent. Are you using Python 2.4? Sure. If someone made Python 2.4 incompatible changes then they have to reverted :- [EMAIL PROTECTED] neither compiles directly using python setup.py build - neither with Python 2.4 nor 2.5 nor 2.6. Also running the bootstrap.py; bin/buildout dance does not work in any way...wtf??? Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.container won't compile
On 19.10.2008 17:13 Uhr, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: A buildout fails reproducable both on Mac and Linux...how is the guilty? Andreas -- Develop: '/Users/ajung/src/svn.zope.org/zopyx.smartprintng.core/trunk/zopyx.convert2' Unused options for buildout: 'download-directory'. Installing test. Getting distribution for 'zope.app.container'. In file included from src/zope/app/container/_zope_app_container_contained.c:64: src/zope/app/container/_zope_proxy_proxy.c:616: error: syntax error before 'wrap_length' src/zope/app/container/_zope_proxy_proxy.c:617: warning: return type defaults to 'int' src/zope/app/container/_zope_proxy_proxy.c:622: error: syntax error before 'Py_ssize_t' src/zope/app/container/_zope_proxy_proxy.c:623: warning: function declaration isn't a prototype src/zope/app/container/_zope_proxy_proxy.c: In function 'wrap_slice': src/zope/app/container/_zope_proxy_proxy.c:624: error: 'self' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c:624: error: (Each undeclared identifier is reported only once src/zope/app/container/_zope_proxy_proxy.c:624: error: for each function it appears in.) src/zope/app/container/_zope_proxy_proxy.c:624: error: 'start' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c:624: error: 'end' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c: At top level: src/zope/app/container/_zope_proxy_proxy.c:628: error: syntax error before 'Py_ssize_t' src/zope/app/container/_zope_proxy_proxy.c:629: warning: function declaration isn't a prototype src/zope/app/container/_zope_proxy_proxy.c: In function 'wrap_ass_slice': src/zope/app/container/_zope_proxy_proxy.c:630: error: 'self' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c:630: error: 'i' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c:630: error: 'j' undeclared (first use in this function) src/zope/app/container/_zope_proxy_proxy.c:630: error: 'value' undeclared (first use in this function) error: Setup script exited with error: command 'gcc' failed with exit status 1 An error occured when trying to install zope.app.container 3.6.1.Look above this message for any errors thatwere output by easy_install. While: Installing test. Getting distribution for 'zope.app.container'. A trunk checkout compiles cleanly on Python 2.4: Sidnei checked in a fix for this problem on Thursday. I assume this made it into zope.app.container 3.6.1 released on October 15th: http://pypi.python.org/pypi/zope.app.container So why won't this version build with Python 2.4? In addition this release has a source dist and two eggs (for 2.4 and 2.5). Wasn't there consensus to upload sdists only (except for Windows)? Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 - supported Python versions
On 15.10.2008 14:25 Uhr, Martijn Faassen wrote: Sidnei da Silva wrote: On Tue, Oct 14, 2008 at 2:16 PM, Andreas Jung[EMAIL PROTECTED] wrote: Thanks for starting the discussion. Going for Python 2.6 also requires that we get the ZCA running on top of Python 2.6 until some time next year. FWIW, that's what I've been working on. There's enough of the the ZCA working on Python 2.6 to run Zope 2. Would anything else be needed? I would say we are pretty much done as far as Zope 2 is concerned. Concerning the component architecture or the entire port? If the latter, what about the security review for untrusted code? You mean the review of RestrictedPython? Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 - supported Python versions
On 15.10.2008 14:44 Uhr, Martijn Faassen wrote: Hi there, On Wed, Oct 15, 2008 at 2:30 PM, Andreas Jung[EMAIL PROTECTED] wrote: If the latter, what about the security review for untrusted code? You mean the review of RestrictedPython? Yes. If RestrictedPython is to be reviewed for changes, it *might* be easier to do this for 2.4 - 2.5 instead of the big leap of two python versions. This depends a bit on how such a review is structured. If Python 2.6 is the latest official Python version of the 2.X line that there is a chance that this version will be supported by the Python community in the long term. So supporting Python 2.4 or Python 2.5 does not make much sense to me. RestrictedPython: I talked with Alan Runyan about this topic at the Plone conferenceif we are serious then RP has to be reviewed. But who can review it and how long would it take. There are possibly only a limited number of people with the experience and skills for performing such a review. The last review took several person days (as far as I can remember). So the review process is possibly tied to some financial resource in order to sponsor the review. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: Zope/branches/gsoc-python-2.5/utilities/mkzopeinstance.py sha - hashlib
On 14.10.2008 19:03 Uhr, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: Log message for revision 92197: sha - hashlib That needs to be a conditional import, with a fallback to the old sha module: hashlib is not present in python 2.4. E.g.: try: import hashlib except ImportError: # Python 2.5 import sha _sha = sha.new else: _sha = hashlib.sha1 and then use '_sha' in the code. Depends on which Python versions we want/must support for the future. One option would to jump on Python 2.6 for the next releases (skipping Python 2.5 and dropping Python 2.4 support). Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Upcoming Zope 2.9-2.11 release
Hi there, I intended to work on new releases for Zope 2.9 - 2.11 starting next weekend. If there are any pending fixes I am not aware of, please let me know. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 - supported Python versions
On 14.10.2008 19:12 Uhr, Hanno Schlichting wrote: Andreas Jung wrote: Depends on which Python versions we want/must support for the future. One option would to jump on Python 2.6 for the next releases (skipping Python 2.5 and dropping Python 2.4 support). Just as a voice from the Plone crowd. With our current planned roadmap we won't move to Zope 2.12 / trunk until sometime next year at the earliest. A hard requirement of Python 2.6 would be fine with us. Thanks for starting the discussion. Going for Python 2.6 also requires that we get the ZCA running on top of Python 2.6 until some time next year. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.12 - supported Python versions
On 14.10.2008 19:56 Uhr, Sidnei da Silva wrote: On Tue, Oct 14, 2008 at 2:16 PM, Andreas Jung[EMAIL PROTECTED] wrote: Thanks for starting the discussion. Going for Python 2.6 also requires that we get the ZCA running on top of Python 2.6 until some time next year. FWIW, that's what I've been working on. There's enough of the the ZCA working on Python 2.6 to run Zope 2. Would anything else be needed? not sure I would say we are pretty much done as far as Zope 2 is concerned. Cool. Thanks for your efforts and the guys working on this GSOC project. Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [Fwd: [Bug 279981] Re: zope.app.testing use of 'with' keyword breaks with Python 2.6]
Who is committing code that is incompatible with Python 2.4? I think it is not acceptable - even for code on the trunk of a package. Andreas Original-Nachricht Betreff: [Bug 279981] Re: zope.app.testing use of 'with' keyword breaks with Python 2.6 Datum: Wed, 08 Oct 2008 04:13:52 - Von: Sidnei da Silva [EMAIL PROTECTED] Antwort an: Bug 279981 [EMAIL PROTECTED] An: [EMAIL PROTECTED] Referenzen: [EMAIL PROTECTED] ** Also affects: zope.app.testing Importance: Undecided Status: New ** Also affects: zope2 Importance: Undecided Status: New -- zope.app.testing use of 'with' keyword breaks with Python 2.6 https://bugs.launchpad.net/bugs/279981 You received this bug notification because you are a member of Zope 3 Developers, which is subscribed to Zope 3. -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:[EMAIL PROTECTED] title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zc.recipe.testrunner 1.1.0 requires zope.testing 3.6.0, but not released
--On 4. September 2008 13:38:27 +0200 Martijn Faassen [EMAIL PROTECTED] wrote: Hi there, There appears to be a release of zc.recipe.testrunner 1.1.0 which requires zope.testing 3.6.0, but zope.testing 3.6.0 was not released as far as I can see. This means zc.recipe.testrunner 1.1.0 cannot be installed. zope.testing 3.6.0 was marked as hidden on PyPI. It's now visible again - together with 3.5.6. Andreas pgpCkZWLLvn2R.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Dependencies and future of zope 3
--On 3. September 2008 08:04:00 +0200 Lennart Regebro [EMAIL PROTECTED] wrote: On Wed, Sep 3, 2008 at 02:54, David Pratt [EMAIL PROTECTED] wrote: In any case I am interested in hearing from folks about what can or ought to be done or whether there is interest in this direction. Many thanks. That the packages are too dependent on each other today, and that this means a base installation of Zope3 is too big is well known. So I think I can definitely say Yes to that answer. This is a big issue? I don't think so. Disks are cheap and usually you don't get in touch with the dependent modules under the hood - except for debugging :-) -aj pgpxtUxyMr9Bj.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Dependencies and future of zope 3
--On 3. September 2008 12:17:56 +0200 Roger Ineichen [EMAIL PROTECTED] wrote: My personal meaning is, we already have a component architecture but we need to split it in a different way into reusable components. Such a split could probably not be done earlier because we didn't see all the usecases. But now since we have grok, repoze and z3c we have many more options to reuse other components and this makes it much clearer what we have to provide as reusable and what not. Sounds like a task for someone to build a dependency graph in order to generate a visualization in order to figure out where to break the dependency chain. Andreas pgpMA8Yhb21vr.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Increasing the Zope Security [EMAIL PROTECTED]
Hi there, I just submitted a possible security related Zope issue on Launchpad and noticed that the bug has been assigned to the Zope Security Team which consists only of Jim. I suggest that a number of competent developers of the Zope 2 and Zope 3 world volunteer to join the team in order to make sense to the Zope Security team. Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting pgpQYCuQcW5L0.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZPT and strict namespace mapping
--On 30. August 2008 07:39:05 +0200 Wichert Akkerman [EMAIL PROTECTED] wrote: Previously Malthe Borch wrote: Trying to get a feeling here on whether we want to require proper XML namespace definition (current z3c.pt behavior) or implicitly fallback to the standard mappings (current zope.pagetemplate behavior). +1 for requiring proper XML namespace. Tools like xmllint which are incredibly practical to validate your templates require this as well. -1 for having to write boilerplate code. Andreas pgpSeMGlHPHyr.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZPT and strict namespace mapping
--On 29. August 2008 12:31:21 +0200 Malthe Borch [EMAIL PROTECTED] wrote: Trying to get a feeling here on whether we want to require proper XML namespace definition (current z3c.pt behavior) or implicitly fallback to the standard mappings (current zope.pagetemplate behavior). Can you elaborate this statement? Andreas pgpwl01UqfQrT.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZPT and strict namespace mapping
--On 29. August 2008 13:20:38 +0200 Malthe Borch [EMAIL PROTECTED] wrote: 2008/8/29 Andreas Jung [EMAIL PROTECTED]: --On 29. August 2008 12:31:21 +0200 Malthe Borch [EMAIL PROTECTED] wrote: Trying to get a feeling here on whether we want to require proper XML namespace definition (current z3c.pt behavior) or implicitly fallback to the standard mappings (current zope.pagetemplate behavior). Can you elaborate this statement? Right, so this is basically a question of whether the following template is legal or not: div tal:replace=string:hello world! / In ZPT it would be, because it automatically assumes this namespace declaration: xmlns=http://www.w3.org/1999/xhtml; xmlns:tal=http://xml.zope. org/namespaces/tal xmlns:metal=http://xml.zope.org/namespaces/metal; . z3c.pt otoh, does not make such an assumption. For convenience: z3c.pt should/could make such an assumption :-) Andreas pgpCwfAxhpKkh.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZODB3 3.9.0-dev-r77011 egg?!
--On 19. August 2008 12:56:43 -0400 Tres Seaver [EMAIL PROTECTED] wrote: and why does buildout pick it over a stable release? Because buildout, like easy_install, will pick the newest available version for a distribution. Fortunately, buildout has a prefer-stable option so that you can tell it to prefer stable over alpha/beta/dev releases. Also, in any serious situtation you'd want to pin your versions, e.g. using the KGS [2] or a manual list. Uploading non-releases like this to public index locations has *got* to stop. Frankly, they should all be removed: anybody who is depending on them needs to run their own index. +oo Package sanity and package hygiene is the most important issue of PyPI right now. PyPI requires a strong policy in order to keep PypI possible: no uploading of development releases, no uploading for packages without a minimum set of metadata. PyPI has become a data toilet - unfortunately it is often hard to convinced people that their package uploads without metadata are crap. Andreas pgpSkU7QQimZh.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 4 OK, 1 Unknown
--On 16. August 2008 17:18:56 +0200 Philipp von Weitershausen [EMAIL PROTECTED] wrote: Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Fri Aug 15 11:00:00 2008 UTC to Sat Aug 16 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Unknown --- Subject: UNKNOWN : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Aug 15 20:40:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010015.html I can't reproduce this failure on my box (self-compiled Python 2.3.5, Ubuntu). Does anyone have a clue why the 'encodings.aliases' module would be different? I certainly don't, but apparently there was a bug report [1] which caused Andreas to fix it in Hotfix (see r89881), but not the Zope 2.8 branch. hmm? The 2.8 branch contains the original code of the Hotfix + Tres' fix for the _aliases problem. I also can not reproduce this failure with Python 2.3 + Zope 2.8. The fix for https://bugs.edge.launchpad.net/zope2/+bug/258154 was to include Tres' fix for Python 2.3 with the hotfix - but only for Python 2.3 interpreters (based on sys.version_info). Andreas pgp4vO6zzYfea.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] New zope.interface 3.4.2 release
--On 28. Juli 2008 17:39:52 -0700 Stephan Richter [EMAIL PROTECTED] wrote: On Saturday 26 July 2008, Hanno Schlichting wrote: Would someone (Jim, Philikon, Fred) be willing to do a new zope.interface release or give me access rights on PyPi to do it myself? Or could someone of the three make me an owner of the package? :-) It is one of the few packages I cannot release or give someone else access to. offtopic wishlist for=pypi group accounts /wishlist /offtopic Andreas pgp14frRUHznV.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Tesing a module against against dependencies in different versions
Hi there, we maintain some modules that should work against different versions of dependent module. E.g. my z3c.sqlalchemy module should work with Sqlalchemy 0.3.X and zope.interface 3.0.X or SQLAlchemy =0.4.X and zope.interface=3.3.0 The codebase right works with both combinations. I am not sure how test such configurations automatically because the dependent modules and their versions are fixed within the setup.py. Is there some way together with Buildout, zope.testing friends? Andreas - pgpjLL1OF2aDJ.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.11.1
--On 14. Juli 2008 13:23:03 -0400 Tres Seaver [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: Andreas Jung wrote: If there are no objections I plan to release a bug-fix release of Zope 2.11.1 on Wednesday. Any chance you could make sure Zope itself doesn't issue any deprecation warnings as part of this? I have committed a change which suppresses the DeprecationWarning raised during the import of ZPublisher.Iterators: it needs to use Z2-style interfaces in 2.11, but the Interface module raises DW on import. http://svn.zope.org/Zope/branches/2.11/?rev=88361view=rev All tests pass, and a newly-created appserver instance starts, without logging any DWs. Thanks. Andreas pgpqGvH9lZYt0.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope 2.11.1
If there are no objections I plan to release a bug-fix release of Zope 2.11.1 on Wednesday. Andreas pgpeAIhLs0PAG.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Re: [Plone-developers] PAULA: bringing Zope 3's authentication to Plone and beyond
--On 13. Juli 2008 19:38:01 +0300 Mark Hammond [EMAIL PROTECTED] wrote: Since Zope3 is not a successor to Zope2 but a completely different thing I do not think this is problematic. That too seems a shame to me. So if I found myself with an investment in Zope2 but was looking to the future, Zope3 will not even *attempt* to provide a smoother path for me than, say, moving to django or another alternative framework? How about GROK? I guess the fact the first 4 letters of zope2 and zope3 being the same did imply some sense of continuation in at least *some* things... That's reason why the term zope 3 should be phased out and replaced with Zope web components or something similar. You're not the only one being confused by this. -aj pgpSnPc9uOJ95.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Plone-developers] PAULA: bringing Zope 3's authentication to Plone and beyond
--On 11. Juli 2008 18:04:16 -0700 Florian Friesdorf [EMAIL PROTECTED] wrote: On Thu, Jul 10, 2008 at 10:56:19PM +0200, Wichert Akkerman wrote: Previously Florian Friesdorf wrote: Hi *, within the scope of google summer of code I am integrating zope 3's PAU with Plone's PAS and further enable (non-AT) content objects as source for users and groups. All functionality is developed in pure zope3, the plone integration is happening in a separate packages. All documents describing the project, as well as links to the code can be found here: https://chaoflow.net/projects/gsoc2008/z3membrane-ldap The one thing I am missing is: why? Well, Zope moved onwards from PAS to PAU and I think Plone should too, because: - PAU is way more pythonic and cleaner than PAS/PlonePAS, it is easier to write stuff for PAU; More pythonic or not...writing a PAS plugin is fairly easy and trivial. We have to maintain APIs that we were using for a long time for the sake of backward compatibility (for the sake of plone users and the sake of plone PAS developers). I want API stability. I don't want to change my code just because someone means that a layer would be nice. We already have enough various spots in side Plone where you have at least two choice for implementing things with different technologies..please not yet another such spot. Andreas - we should use as much as possible of Zope3 and avoid custom solutions, increasing the mutual benefit of all Zope3-based projects. pgp78NTSmm6w9.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZCatalog sorting issue
--On 10. Juli 2008 15:06:53 +0200 Martijn Jacobs [EMAIL PROTECTED] wrote: Wat denk je hiervan? Hello. In zope 2.10.5 (and probably 2.10.6 and 2.11 and, as I've read, all releases above 2.7) we've encountered a sorting bug in a dtml-in call when querying the catalog. I don't think it's dtml only related, but I'm not sure about that. It is the same bug as found on : https://bugs.launchpad.net/zope2/+bug/143504 seems to correct the problem though and I was wondering why this isn't added in the zope core. Does it break other stuff or should the problem fixed somewhere else? Somebody has some thoughts? Here is the deal: you provide a unittest for the patch and I commit the patch + tests. Andreas pgpjOA2XtXB7c.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] transaction.doom() and ZPublisher
--On 10. Juli 2008 17:09:36 +0200 Brian Sutherland [EMAIL PROTECTED] wrote: On Thu, Jul 10, 2008 at 12:12:06AM -0400, Paul Winkler wrote: Hi, I havn't investigated properly, but it may be necessary to do the isDoomed() check at a higher level where you can abort. What do you mean by higher level? I think that the check within the ZPublisher is the highest and right place. Code running after the commit() expects a new transaction and now will not get that. You refer to code executed as part of a ZODB post-commit handler? If a transaction is doomed then such handlers should never be executed - right? Andreas pgpKkDXi6hGoS.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.testing releases on PyPI
Hi, the zope.testing releases on PyPI are apparently a bit weird. - zope.testing 3.5.1 has been the latest released version on PyPI last week - I created V 3.5.2 on Sunday. Phillip granted me access to the zope.testing package on PyPI in order to upload 3.5.2 (which worked) - I created V 3.5.3 yesterday morning. Uploading the egg was impossible because I had no longer rights (in fact permissions are currentl only granted to Jim and Fred Drake (not even Phillip) - search for zope.testing on PyPI leads me to version 3.0 instead of 3.5.1 Does anyone know what happened here? Andreas pgp459Jz1XjNk.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: zope.testing releases missing on pypi
In fact I uploaded zope.testing 3.5.2 on Sunday to PyPI. However I also noticed that 3.5.2 disappeared this morning and that I had no longer permissions on zope.testing...no idea what's going on. Andreas --On 8. Juli 2008 14:13:35 +0200 Wichert Akkerman [EMAIL PROTECTED] wrote: I see zope.testing 3.5.2 and 3.5.3 in svn and used by Zope2 but the latest version on pypi is 3.5.1. Why is that? And can that be corrected? Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting pgpmT2YVj6tnw.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] TALES iterator odd/even reversal
--On 4. Juli 2008 02:05:30 +0300 Marius Gedminas [EMAIL PROTECTED] wrote: Recently I migrated a large-ish app built on Zope 3.2 to Zope 3.4. (About time I hear someone mumbling in the audience.) One strange difference was that TALES iterators swapped the meaning of odd and even, i.e. p tal:repeat=item python: [1, 2, 3, 4] span tal:condition=repeat/var/oddoddspan span tal:condition=repeat/var/evenevenspan /p produces different results on Zope 3.4 than it did on 3.2. First, your example does not work (must be repeat/item instead of repeat/var). Does anyone know why this is? Is this a bug? Should it be fixed? Where exactly is the bug? The output is even-odd-even-odd. The even/odd methods apply to the current iteration number afaik - but not to the variable within the current iteration itself. Or? Andreas pgpRMGppHEz20.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Retrieve Zope data
--On 24. Juni 2008 12:36:59 +0530 Charith Paranaliyanage [EMAIL PROTECTED] wrote: Hi, Can someone help me on this, I need to import objects and interfaces in Zope to another program. Say I have created some objects in Zope and then I need to retrieve them from other application running separately. How can I do this? Let me know it such application is available and other resources if available. Please be specific: access from where, access through which protocol, access through which programming language? P.S. This issue belongs to the [EMAIL PROTECTED] mailing list, not on the zope-dev list. Andreas pgpGuDPDkRkzC.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] buildbot news: sending notifications and current broken builds
--On 6. Juni 2008 08:23:40 +0200 Christian Theune [EMAIL PROTECTED] wrote: Hi, I've watched my buildbot send out notifications for a while and pondered how to make them available to more people. I decided to send them to this list on a 'problem' level. The 'problem' level sends a message when a builder changes from a good state to a bad state but doesn't send a new message on subsequent failing builds. For me this has been reasonably quiet over the last two weeks although about 60 builders are broken. The risk of sending mail here is that a massive build failure can cause about 200 messages being send at once. If anybody knows a better approach with buildbot, please let me know, I'd be happy to implement it. For everyone else: please have a look at the list of broken builds: http://zopebuildbot.whq.gocept.com/cruise A minor usability suggestion: please provide links at the top of the page for every top-level namespace that would setup the filter for this namespace. Andreas pgpWwlSf7m9np.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] setuptools extension for buildout old-style tar-balls?
Hi, lots of old-style Zope products are now available as eggs. However a lot of people still don't work with buildout and need the old-style tar-balls. Does anyone know of a setuptools extension for generating and upload the tar-balls directly from a Products. package? Using the 'sdist' command is not suitable since it includes the 'Products' top-level directory which is not what we want. Andreas -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK E-Publishing, Python, Zope Plone development, Consulting pgpYYwYetJCxy.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope3 on Google AppEngine
--On 24. Mai 2008 15:44:01 +0200 Hermann Himmelbauer [EMAIL PROTECTED] wrote: I currently use SQLAlchemy, but it seems that transactions are managed on the RDB-level only, which means that the object state is not in the transaction scope. Huh? If you use one of the integration framework for sqlalchemy-within-zope then SQLAlchemy is fully integrated with the Zope transaction system. Andreas pgpbhiBAcII26.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope and Storm (SQL)
--On 24. Mai 2008 10:47:54 +0200 Jürgen kartnaller [EMAIL PROTECTED] wrote: There seems to be some interest on the use of SQL databases with Zope. Lovelysystems is now using SQL databases as the primary storage for their applications. We use Zope and Postgres with Storm as ORM. The main reason for switching to SQL database were speed issues with queries. Thanks for this interesting mail. Some questions: - how to you deal with binary large objects? - how do you deal with changes in the data model and related migrations? - how do you deal with hierarchical or semi-structured data (e.g. SGML, XML)? We are working and building hybrid solutions on top of Zope 2 since years where parts of the data is stored within the ZODB and metadata is stored within Postgres and this worked out pretty well. I would disagree that a RDBMS is the best solution for every particular usecase. The decision for the backend storage must be made for every project - either use the ZODB, a RDBMS or a mixture of both. Andreas pgpcqhwfWJbE9.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope 2.11.0c1 released
Hi, I just released Zope 2.11.0c1 in order to get the final release of 2.11.0 out of the door as soon as possible: http://www.zope.org/Products/Zope/2.11.0c1 This releases contains the latest official Zope 3.4.0 codebase. I plan to release Zope 2.11.0 final in roughly three weeks from now (around June 14th). Andreas pgp1zFqWnEShu.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope and Storm (SQL)
--On 24. Mai 2008 17:57:17 +0200 Brian Sutherland [EMAIL PROTECTED] wrote: On Sat, May 24, 2008 at 11:28:37AM +0200, Andreas Jung wrote: - how do you deal with hierarchical or semi-structured data (e.g. SGML, XML)? As a side note, PostgreSQL 8.3 has a native XML column type. It's fairly basic still, but you can create indexes based on xpath queries. Jup. Postgres already had in version 7 XML support as an add-on...but pretty much unusable for the production and the functionality of the XML type in Postgres 8 looks similarly (feature-wise). Andreas pgpnHAvGgycYX.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.11.0c1 released
--On 24. Mai 2008 18:08:06 -0700 Alexander Limi [EMAIL PROTECTED] wrote: On Sat, 24 May 2008 04:57:35 -0700, Andreas Jung [EMAIL PROTECTED] wrote: I just released Zope 2.11.0c1 in order to get the final release of 2.11.0 out of the door as soon as possible: http://www.zope.org/Products/Zope/2.11.0c1 Since I didn't see a clear consensus on the Z2 interfaces thread — does this release emit deprecation warnings for the Z2 interfaces? No. Someone might add the deprecation warnings as needed (I won't do that). Otherwise this release will go out as it is right now. Andreas pgp4vdWWYAoRA.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Multiple file upload in a single form
--On 13. Mai 2008 12:01:28 +0530 Suresh V. [EMAIL PROTECTED] wrote: Has anyone come across a Multiple File field type that be used in a form , specifically with z3c.form? This will enable an unlimited number of files to be uploaded in a single form. I know this exists in the Plone world. Just wanted to check for an analogous field for a zope3 application. Integrating something like JUpload should be fairly trivial. -aj pgpPxRi1Pk36S.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope2 monitoring
Hanno Schlichting wrote: Nice. We are already using supervisord for this project. Even more off-topic that's why we added the new 'console' command to the zopectl-like script in the zope2instance recipe, to have Zope running in fg mode without the forced automatic development mode. yay, finally! :) andi -- zeidler it consulting - http://zitc.de/ - [EMAIL PROTECTED] friedelstraße 31 - 12047 berlin - telefon +49 30 25563779 pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/ plone 3.1rc1 released! -- http://plone.org/products/plone/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [ANN] Blackforest Sprint 2008 in Freiburg, Germany - August 25-27th
On behalf of Haufe Mediengruppe, Freiburg, Germany I am pleased to announce the BLACKFOREST SPRINT 2008 August 25-27th in Freiburg, Germany. The sprint is focused on topics like enterprise-level Zope, high-availablity, scalability, Buildout, Grok technology in Zope 2 and other hot topics that are of interest for big Zope users. The official sprint project page is hosted on Openplans: http://www.openplans.org/projects/black-forest-sprint/project-home Feel free to register or get in touch with me if you have question or need further assistance. Andreas pgpQyrM2e3cBY.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: zope.sqlalchemy
--On 9. Mai 2008 11:20:31 +0100 Laurence Rowe [EMAIL PROTECTED] wrote: You need an svn checkout of SQLAlchemy until 0.4.6 is released. Laurence Great, that worked and made all tests pass. Andreas pgpEracgwI4qR.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.sqlalchemy
--On 6. Mai 2008 06:01:14 +0200 Andreas Jung [EMAIL PROTECTED] wrote: --On 6. Mai 2008 02:26:58 +0100 Laurence Rowe [EMAIL PROTECTED] wrote: Following discussions with Kapil, Christian and Martin I've developed zope.sqlalchemy. The aim is to provide a common base for transaction integration. It does not attempt to define any particular way to handle database configuration as there is not yet consensus on the best way to handle it. Looks great (on the paper :-)). Trying to integrate it with z3c.sqlalchemy over the weekend. Thanks Laurence. I got a big stuck with the zope.sa integration in z3c.sa. Two tests of my testsuite fail (likely related to a session.save() operation): Error in test testXXMapperGetMapper (z3c.sqlalchemy.tests.testSQLAlchemy.WrapperTests) Traceback (most recent call last): File /opt/python-2.4.4/lib/python2.4/unittest.py, line 260, in run testMethod() File /Users/ajung/sandboxes/z3c.sqlalchemy/lib/python/z3c/sqlalchemy/tests/testSQLAlchemy.py, line 168, in testXXMapperGetMapper user = session.query(User).filter_by(firstname='foo')[0] File /opt/python-2.4.4/lib/python2.4/site-packages/SQLAlchemy-0.4.5-py2.4.egg/sqlalchemy/orm/query.py, line 834, in __getitem__ return list(self[item:item+1])[0] File /opt/python-2.4.4/lib/python2.4/site-packages/SQLAlchemy-0.4.5-py2.4.egg/sqlalchemy/orm/query.py, line 925, in __iter__ self.session._autoflush() File /opt/python-2.4.4/lib/python2.4/site-packages/SQLAlchemy-0.4.5-py2.4.egg/sqlalchemy/orm/session.py, line 747, in _autoflush self.flush() File /opt/python-2.4.4/lib/python2.4/site-packages/SQLAlchemy-0.4.5-py2.4.egg/sqlalchemy/orm/session.py, line 757, in flush self.uow.flush(self, objects) File /opt/python-2.4.4/lib/python2.4/site-packages/SQLAlchemy-0.4.5-py2.4.egg/sqlalchemy/orm/unitofwork.py, line 236, in flush session.extension.after_flush(session, flush_context) File /opt/python-2.4.4/lib/python2.4/site-packages/zope.sqlalchemy-0.1dev_r86482-py2.4.egg/zope/sqlalchemy/datamanager.py, line 187, in after_flush invalidate(session) File /opt/python-2.4.4/lib/python2.4/site-packages/zope.sqlalchemy-0.1dev_r86482-py2.4.egg/zope/sqlalchemy/datamanager.py, line 170, in invalidate assert _SESSION_STATE[id(session)] is not STATUS_READONLY KeyError: 32500656 The integration code follows your documentation; http://svn.zope.org/z3c.sqlalchemy/branches/zope.sqlalchemy-integration/src/z3c/sqlalchemy/base.py?rev=86543view=auto And the tests are here: http://svn.zope.org/z3c.sqlalchemy/branches/zope.sqlalchemy-integration/src/z3c/sqlalchemy/tests/testSQLAlchemy.py?rev=86552view=markup Any idea? Andreas pgpDIQhCri8MD.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.sqlalchemy
--On 6. Mai 2008 02:26:58 +0100 Laurence Rowe [EMAIL PROTECTED] wrote:
Following discussions with Kapil, Christian and Martin I've developed
zope.sqlalchemy. The aim is to provide a common base for transaction
integration. It does not attempt to define any particular way to handle
database configuration as there is not yet consensus on the best way to
handle it.
I've uploaded it to zope svn and pypi. See
http://pypi.python.org/pypi/zope.sqlalchemy
Currently it depends on a development version of SQLAlchemy. I hope to
make a release following the 0.4.6 release of SQLAlchemy.
See pypi or the readme for details, but briefly usage is something like:
engine = create_engine('sqlite:///')
Session = scoped_session(sessionmaker(
... bind=engine, transactional=True, autoflush=True,
... extension=ZopeTransactionExtension()))
session = Session()
session.save(User(name='bob'))
transaction.commit()
Any comments appreciated.
Looks great (on the paper :-)). Trying to integrate it with z3c.sqlalchemy
over the weekend. Thanks Laurence.
Andreas
pgpZKhiINSlh6.pgp
Description: PGP signature
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope(2|3) on Python 2.5
--On 28. April 2008 14:43:31 +0100 Chris Withers [EMAIL PROTECTED] wrote: Hi All, Since it appears everything Zope-ish now runs on Python 2.5, what's still stopping a release of Zope 2 and Zope 3 which recommends or support Python 2.5? Zope 2 does *not* run on Python 2.5 so far. There is someone working on this issue as part of a summer of google project. Andreas pgpszPwRke93D.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope2 interfaces delenda est!
--On 25. April 2008 21:39:14 +0200 Stefan H. Holek [EMAIL PROTECTED] wrote: +1 for trunk -1 for 2.11 branch Same vote from my side. The 2.11 branch is in beta state and for this reason no major changes for 2.11 please. Andreas pgphPwqNpCYq2.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] comments on DateTime(DateTime()) preserving timezone? (launchpad 200007)
--On 25. April 2008 17:07:29 -0400 Paul Winkler [EMAIL PROTECTED] wrote: I've got a fix, with tests, for https://bugs.launchpad.net/zope2/+bug/27 checked in at Zope/branches/slinkp-datetime-27 If nobody objects in the next few days, I'd like to merge this to trunk, and the 2.11, 2.10, and 2.9 branches. Thanks Paul for fixing this. Go ahead with merging. Andreas pgpeqXM19kU30.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope 2.9.9/Zope 2.10.6 releases
Hi, if there are no objections I'll do bugfixes releases for Zope 2.9 and 2.10 around May 11th. So fix what you have to fix in advance :-) Andreas pgpFxSb2U5HM0.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] paver: buildout is utterly doomed
--On 22. April 2008 17:14:49 -0600 Shane Hathaway [EMAIL PROTECTED] wrote: Kent Tenney wrote: From Kevin's blog http://www.blueskyonmars.com/2008/04/22/paver-and-the-building-distribut ion-deployment-etc-of-python-projects/ (http://tinyurl.com/68sz6u) The idea is to use zc.buildout's machinery, not reinvent it. I agree, it sounds like Kevin wants to take the best parts of zc.buildout and make something more complete. Assuming Paver matures, why not switch Zope to use Paver when it's ready? You don't have to jump on any train just because it passes by. Competition is a good thing and having several alternatives for a particular problem is not bad by design. The basic problem within the Python community is the inflation of alternatives - I would call it also unnecessary inflation of alternatives). Unnecessary alternatives means: bad designed, bad implemented. Some examples: every week new tiny Python ORMs pop up (we have strong implementations like SQLALchemy, Storm, SQLObject), we have an inflation of zc.buildout recipes doing nearly the same (svn checkouts, executing command line commands). Andreas pgpmpV4ntJezN.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope 3.4 final schedule?
Hi, I asked already six weeks ago about the schedule for the final 3.4 release and got no reply so far. So once again the same question...how is in charge for doing the 3.4 release? Thanks, Andreas pgp51ZKZkiEQk.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Proposal: Merge philikon-aq branch into Zope trunk
Christian Theune wrote: On Thu, Apr 17, 2008 at 12:43:25PM +0200, Martijn Pieters wrote: On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote: I would like to do the merge as soon as possible, so people can easily test it against all their applications and report back problems. Merging it into Zope trunk will get it into the Zope 2.12 release which is at this point not scheduled yet, but is unlikely to get a release before early 2009. This should give us plenty of time to test. Opinions, votes? +sys.maxint! Darn. My +1 won't fit in there anymore! perhaps martijn's still on 32-bit? :) anyway, +1 from me as well. andi -- zeidler it consulting - http://zitc.de/ - [EMAIL PROTECTED] friedelstraße 31 - 12047 berlin - telefon +49 30 25563779 pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/ plone 3.1rc1 released! -- http://plone.org/products/plone/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Proposal: Merge philikon-aq branch into Zope trunk
--On 17. April 2008 12:27:42 +0200 Hanno Schlichting [EMAIL PROTECTED] wrote: Hi. I'd like to propose to merge the philikon-aq branch into Zope trunk aka Zope 2.12. Go ahead. Andreas pgphIV5gzoW65.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Non-ASCII characters in URLs
--On 12. April 2008 21:43:40 -0400 Tres Seaver [EMAIL PROTECTED] wrote: This is becoming increasingly painful I will soon have a patch against Zope 2.11b1 which gets rid of this restriction. If there is consense, I can add it to the Zope repository. +1 from my side. Saves me the work to cleanup my own dirty patch :-)) - -1 without *careful* analysis of how the patch is going to break existing applications which rely on the fact that IDs are only ASCII (and therefore don't need to be quoted). At a minimum, this kind of change is going to require documenting the risks, and getting soem feedback, before any merge to a production release. Please check the patch in on a private branch and ask for comments here. @Dieter: please create a branch for this (and not as patch for Launchpad) The patch is working for long time (possibly several years) within our private Zope. So I would not expect much problems. Of course it needs testing and documentation. Andreas pgp33OXmU7CcU.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [Launchpad] Permissions for changing status of a ticket?
Hi, last night, roughly 20 tickets of the Zope 2 tracker were marked as Invalid by a person (never heard its name) which is no part of the Zope 2 developers group on LP. Independent of each ticket I am a bit surprised that obviously any authenticated LP user is able to change the workflow state of a ticket. Is there a configuration option on LP for changing this behavior? Andreas pgplhyuDpqjSG.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: straighting out the SQLAlchemy integration mess
--On 11. April 2008 10:09:16 +0200 Brian Sutherland [EMAIL PROTECTED] wrote: On Fri, Apr 11, 2008 at 05:07:56AM +0200, Andreas Jung wrote: --On 10. April 2008 21:29:43 +0200 Brian Sutherland [EMAIL PROTECTED] wrote: What defines if something is the instance configuration? Isn't ZCML just another format of configuration file? I agree it's evil to hardcode database connections in the application as they must be under the control of the sysadmin. But that doesn't preclude them from being expressed in zcml. The point is: we don't need yet another configuration language for the configuration of a site. ZCML should be used for the purpose it has been intended for: for the configuration of the components of your site (easily spoken). This kind of configuration is static if you setup a site for project X. But settings like ports, paths etc. often differ between dev, test and production environments. We already have ZConfig as standard cofniguration language for instance specific configuration aspects. In addition: we often do use environment variables and .ini files for additional configurations. Introducing another configuration language is stupid. Especially because system administrators or co-workers know little or nothing about ZCML. This is an unnecessary introduction of complexity. Setting an environment variable with a DSN is much easier then having to fiddle around with ZCML and XML...totally unnecessary overheadkeep it simple ...using ZCML in this configuration context is only for XML masochists. Unfortunately, it doesn't seem an option, right now, to avoid using ZCML to setup database connections. So I'm not sure how you want to implement your ideas? I have no need for ideas to be implemented. We're using SA within in several large projects based on z3c.sqlalchemy. And nothing beats the simplicity of of an .ini file or an environment variable. In general, I think if you want your configuration expressed in ZConfig and available as a utility, you have a problem. I'm not sure of: * How do I register a utility in ZConfig? z3c.sqlalchemy provides a method for registering a SA connection as a named utility. This code is usually called during the startup phase of Zope within the related initialize() methds of our products. The DSN are acquired from well-known environment variables...this just works - easy, simple, reliable. * How will the above registration work properly in functional tests (especially with tearing down and setting up layers)? Functional tests in our company are tests done by humans. Why? Our applications are very complex with lots of dependencies. Not speaking of lots of involved databases, big storages.. Andreas pgp98vhOQjdEm.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: straighting out the SQLAlchemy integration mess
--On 11. April 2008 08:36:43 +0100 Martin Aspeli [EMAIL PROTECTED] wrote: Martijn Faassen wrote: Andreas Jung wrote: --On 10. April 2008 19:10:49 +0200 Brian Sutherland [EMAIL PROTECTED] wrote: Just adding my few requirements: - Integration into the component architecture in such a way that I can specify the db connection parameters in ZCML and that database reflection still works. I want to be able to get a handle on SQLAlchemy things by calling getUtility. Please *NO* database specific configurations within ZCML. We're running applications in up three or four different environments and I don't want to maintain instance specific configurations within ZCML. Either we pass such informations through environment variables or the database connections parameters are read from a configuration within the instance configuration. As long as it can also be specified in the code, that way people can build UIs to set up the connection. Perhaps that's what you mean by a configuration within the instance configuration. The way I use collective.lead in my book is to have it look up the database settings in a local utility. That utility is editable via a control panel page in Plone. I suspect that it'd be quite easy to do something similar where the settings were deferred to a global utility configured with ZCML or looked up in a config file of some sort. Once the config is available, it's all about calling getUtility() to get hold of a database connection/session. Possibly a sane and clean solution but way of over-designed. I am interested in simple and robust solutions that work and not in a solution that adds more and more unnecessary layers just the sake of having them :-) Andreas pgpZS98rSgYnq.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: straighting out the SQLAlchemy integration mess
--On 10. April 2008 19:10:49 +0200 Brian Sutherland [EMAIL PROTECTED] wrote: Just adding my few requirements: - Integration into the component architecture in such a way that I can specify the db connection parameters in ZCML and that database reflection still works. I want to be able to get a handle on SQLAlchemy things by calling getUtility. Please *NO* database specific configurations within ZCML. We're running applications in up three or four different environments and I don't want to maintain instance specific configurations within ZCML. Either we pass such informations through environment variables or the database connections parameters are read from a configuration within the instance configuration. Andreas pgpPVek73cZst.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: straighting out the SQLAlchemy integration mess
--On 10. April 2008 21:29:43 +0200 Brian Sutherland [EMAIL PROTECTED] wrote: On Thu, Apr 10, 2008 at 07:31:54PM +0200, Andreas Jung wrote: --On 10. April 2008 19:10:49 +0200 Brian Sutherland [EMAIL PROTECTED] wrote: Just adding my few requirements: - Integration into the component architecture in such a way that I can specify the db connection parameters in ZCML and that database reflection still works. I want to be able to get a handle on SQLAlchemy things by calling getUtility. Please *NO* database specific configurations within ZCML. We're running applications in up three or four different environments and I don't want to maintain instance specific configurations within ZCML. Either we pass such informations through environment variables or the database connections parameters are read from a configuration within the instance configuration. What defines if something is the instance configuration? Isn't ZCML just another format of configuration file? I agree it's evil to hardcode database connections in the application as they must be under the control of the sysadmin. But that doesn't preclude them from being expressed in zcml. The point is: we don't need yet another configuration language for the configuration of a site. ZCML should be used for the purpose it has been intended for: for the configuration of the components of your site (easily spoken). This kind of configuration is static if you setup a site for project X. But settings like ports, paths etc. often differ between dev, test and production environments. We already have ZConfig as standard cofniguration language for instance specific configuration aspects. In addition: we often do use environment variables and .ini files for additional configurations. Introducing another configuration language is stupid. Especially because system administrators or co-workers know little or nothing about ZCML. This is an unnecessary introduction of complexity. Setting an environment variable with a DSN is much easier then having to fiddle around with ZCML and XML...totally unnecessary overheadkeep it simple ...using ZCML in this configuration context is only for XML masochists. Andreas pgpyigxtKwGmK.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: straighting out the SQLAlchemy integration mess
--On 9. April 2008 14:15:38 +0100 Laurence Rowe [EMAIL PROTECTED] wrote: @everyone: If we can all agree to use the same basic session and transaction management then we should probably push for it to be included as a sqlalchemy extension module. I would be happy with such a solution. As said, I am not into the datamanager-building business and more interested in application-integration issues. The basic requirements I have for our applications: - having the same session within one ZODB transaction (per thread) - need to get hold of the underlying database connection for a given session Andreas pgpFEZVYm6t1t.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] straighting out the SQLAlchemy integration mess
--On 9. April 2008 20:28:18 +0200 Dieter Maurer [EMAIL PROTECTED] wrote: Martijn Faassen wrote at 2008-4-8 23:54 +0200: ... There are at least three approaches to SQLAlchemy integration with Zope: Quite possibly z3c.sqlalchemy has a release that actually works. The current release is not very robust against some kinds of temporary problems. When e.g. the database is restarted, z3c.sqlalchemy may enter a state where all database interactions raise an exception until Zope is restarted. This is very likely an issue of the underlying SA implementation. None of the existing wrappers deal with this kind of problems. In fact I've never seen such issues within applications under my control :-) -aj pgp3gi0Wmd3B5.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: straighting out the SQLAlchemy integration mess
--On 10. April 2008 01:57:12 +0100 Martin Aspeli [EMAIL PROTECTED] wrote: Andreas Jung wrote: --On 9. April 2008 14:15:38 +0100 Laurence Rowe [EMAIL PROTECTED] wrote: @everyone: If we can all agree to use the same basic session and transaction management then we should probably push for it to be included as a sqlalchemy extension module. I would be happy with such a solution. As said, I am not into the datamanager-building business and more interested in application-integration issues. The basic requirements I have for our applications: - having the same session within one ZODB transaction (per thread) - need to get hold of the underlying database connection for a given session I think that's very much the business collective.lead wants to be in. :) You know what was first :-) Even with the collective.lead and z3c.zalchemy datamanager...still two instead of one :-) -aj pgpBydBlV3U6n.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: What happened to the infrae.subversion and py eggs?
--On 8. April 2008 21:39:14 -0400 Tres Seaver [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 1.0dev-r27844 seems to be gone from PyPI. Such a version should *never* have been released to PyPI (any egg / source dist with an SVN revision number in its filename is *not* suitable for sharing with the wider world). Pushing such distributions out to PyPI, rather than sharing them in a more restricted / private location, induces pain on the wrong parties (those who innocently rely on PiPI, rather than those perpetrating the risky behavior). Amen. Lots of people are misusing PyPI right now for uploading their broken packages: lots of dev-packages in some weird state, packages without metadata, packages without URL, packages with descriptions..that's a pretty big pain in the *** right now. I currently working on the buildout infrastructure for three of our major Zope projects (which lots of externals dependencies) and I am sometimes really annoyed that stuffs works some day and not the other day because packages appearently come and go. I'm CCing Sylvain who I believe made the last release. Maybe we can even convince him to make a proper release, not an SVN snapshot. :-) Of course, we should also make sure that the latest version works properly with its pinned py dependency. Amen! Also Amen on this. Andreas pgpYknzKbfp9V.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Non-ASCII characters in URLs
--On 6. April 2008 16:37:22 -0700 Alexander Limi [EMAIL PROTECTED] wrote: Hi, Is there a good technical explanation for why Zope doesn't allow non-ASCII characters in URLs? I'd like to be able to let URLs work like this example from Wikipedia: http://ja.wikipedia.org/wiki/メインページ When I try adding an object with ID メインページ in Zope 2, I get the following error message: Error Type: BadRequest Error Value: The id amp;#12513;amp;#12452;amp;#12531;amp;#12506;amp;#12540;amp;#12472; contains characters illegal in URLs. Is there a fundamental reason (ie. Python objects can only be ASCII) or is it simply bugs that need to be fixed? As Paul indicated: the issue dates back to the times when there was only ASCII in the URL world. Especially object IDs have to be ascii - well...Zope came from US :-) Andreas pgpJMq7CsKKOG.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Packaging Zope for Fedora
--On 27. März 2008 20:42:50 +0200 Marius Gedminas [EMAIL PROTECTED] wrote: On Wed, Mar 26, 2008 at 09:20:27PM +0100, Dieter Maurer wrote: Timothy Selivanow wrote at 2008-3-25 17:12 -0700: ... Now when I say rip out, I don't mean repackage (make a sub RPM), I mean remove from the RPM that I am making. I don't want to provide a new Docutils. That Zope ships with its own Docutils comes from the fact that the standard one has a big security hole. Which one? The one that lets you embed any file on the filesystem into a web page? http://docutils.sourceforge.net/docs/howto/security.html I didn't know Zope's bundled version of docutils fixed that. In any case, the src/docutils in the Zope 3.2 tree either doesn't have the fix, or it doesn't work. I tested it and ended up closing that hole in an application myself. At least Zope 2 uses Docutils with the related options disabled. No idea about Zope 3.2. -aj pgpK98dCDd36X.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Problems installing ZODB under Windows
Hello, I have some troubles installing ZODB under Windows with Python 2.5.1. Benji York recommended to post here. The following it the problem: I downloaded the egg file for ZODB from http://pypi.python.org/packages/2.5/Z/ZODB3/ZODB3-3.8.0-py2.5-win32.egg#md5=2a7c8eb2ad6304a859ffdf5e2b9a075f and tried to install it with easy_install. It quits with the following message: Installed c:\python25\lib\site-packages\zodb3-3.8.0-py2.5-win32.egg Processing dependencies for ZODB3==3.8.0 Searching for zope.interface Reading http://pypi.python.org/simple/zope.interface/ Reading http://zope.org/Wikis/Interfaces/FrontPage Best match: zope.interface 3.4.1 Downloading http://pypi.python.org/packages/source/z/zope.interface/zope.interface-3.4.1.tar.gz#md5= b085f4a774adab688e037ad32fbbf08e Processing zope.interface-3.4.1.tar.gz Running zope.interface-3.4.1\setup.py -q bdist_egg --dist-dir c:\docume~1\holtza\locals~1\temp\easy_ install-9zm01c\zope.interface-3.4.1\egg-dist-tmp-8pfxjw error: Setup script exited with error: Python was built with Visual Studio 2003; extensions must be built with a compiler than can generate compatible binaries. Visual Studio 2003 was not found on this system. If you have Cygwin installed, you can try compiling with MingW32, by passing -c mingw32 to setup.py. Can somebody please create an egg for zope.interfaces 3.4.1 and other dependencies of ZODB? Will I have the same problems if I install the complete zope framework? I don't want to install Visual Studio or any other C-compiler. Thank you very much Andreas Holtz PS: The changelog for ZODB 3.8 does not work either: See http://svn.zope.org/ZODB/trunk/NEWS.txt?view=markup -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [Zope 2.12] Eggification of Zope 2 - pros and cons?
Hi, during the latest 'zope.publisher' thread on zope-dev I came up with the proposal to eggify the Zope core for the Zope 2.12 release. I would like to start a discussion about the pros and cons, risks and advantages of any eggification effort. Chris favors a 'big' Zope egg with some dependencies (like ZODB) stripped out. I would prefer a more broader approach. One of the reasons are company-internals modifications to the Zope core. Right now we maintain a more or less heavy modified version of Zope 2.8 in our repos (making Zope upgrades pretty hard). A better modularization would help us here. Another example: the Plone people maintained a Zope 2.10 branch with experimental ZODB blob support. With an eggified version of ZODB you could easily switch the eggs (easily spoken). So before promoting the eggification as an ultimate goal, let's discuss what we really need and want. A complete eggification just for the sake of eggs is possibly not the goal :-) Andreas pgppXfc9cvnRV.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Packaging Zope for Fedora
--On 21. März 2008 13:39:08 -0700 Timothy Selivanow [EMAIL PROTECTED] wrote: On Fri, 2008-03-21 at 20:09 +0100, Andreas Jung wrote: Hi, speaking as the Zope 2 release manager: I am strongly opposed against splitting Zope yourself into different packages and modules. With Zope 2 depending from various Zope 3 packages (roughly 80-90) we have already the situation to keep track which packages belong together. My concern is more with striping out the non-Zope pieces. If there are pieces of Zope that are useful outside of Zope (e.g. in some other project, or someones personal code...) I thought it would be nice to offer those as a separate piece so that someone could use just that piece. Having 80-90 different RPMs _would_ be rather unmaintainable. I'd only pull out the first few useful ones, and then others by-demand. My biggest concern is removing the non-Zope parts. In general we want to get rid of 3rd-party packages we don't want to maintain on our own. Right now we have several 3rd-party packages like Docutils in our svn for several reasons. Some of those packages are basically frozen (because we made local changes e.g. for security reasons). So if you rip out those packages you have to guarantee that they will _never_ be updated by a new official package (because local changes might get lost). On the other hand you must ensure that changes to our local 3rd-party packages will be available through your packaging mechanism. As said: this is a challenging task for us right now - it will be even more challenging and more error-prone for outsiders. As far as Zope2 is concerned, I'll cross that bridge later. Newest technology is /generally/ the focus of Fedora. This will become even more complicated when each Zope 3 package will have its own life-cycle. I doubt that you as a package can keep track in a reliable way with those requirements. It is somewhat hard for me to follow. The Eclipse project has done an awesome job, and so has Fedora in keeping up with it (they actually work very closely together). I'm not concerned with ripping Zope /completely/ apart, but rather I thought /some/ parts might be useful by themselves, like the ZODB for example. Since Zope (2+3) are officially only blessed for Python 2.4 you'll have problems if you're going with the newest Python 2.5 or even 2.6 version. The trend in all Zope-related projects (Zope 2,3, Grok, Plone) is definitely: self-contained installation. Why self-contained? Different projects require different modules in different versions. Messing a Python installation with e.g. ZODB from different versions will end up in an disaster. So the message of the Zope community is in general: keep your Python installation clean and use zc.buildout or virtualenv for installing your other modules within an isolated environment. This is meanwhile considered best-practice. Using Python eggs and easy_install you have _the official_ tools in your hand for installing 3rd-party packages..that's the Pythonic way to do it, not using some distro packaging tool. So why can't you leave the Zope source packages as they are? Splitting up Zope into even more packages is even more error-prone. Re-packaged Zope distributions always raised more problems in the past than they really solved. The deployment for Zope-based applications is nowadays based on zc.buildout. So, are you saying that you would rather Zope not be in Fedora, or any other distro, and just leave it up to the user? This was never my point. For me it would make more sense that the packages would take the official release and re-package it as a whole without splitting it up. Dependency management should happen on our side as a whole, not on the distribution site. I don't know how important Zope distro packages are for users. My personal impression is: not so important. Zope packages at this point might be good for getting into touch with Zope but for deployment packages are basically no used - but correct me if I should be wrong. Since a while we have tools in place to bootstrap Zope 2/3 projects, Plone installations and Grok installations very easily and in a reliable way. I know that those approaches don't comply directly with your package mechanisms but I would expect that the offical installation and deployment stories by the Zope community should be taken into account (in some way). Serious solutions providers never go with distribution-specific packages. Some do, but that's not the focus of me packaging Zope. Since Fedora's focus is not for production (yes, people do use Fedora in production, e.g. NASA, but that is their onus), but rather development and blazing new trails. This would provide more code and utilities for people to use and experiment with. See above. Distro specific package are perhaps another change for gettting into touch with Zope but I am not sure how important that is. I can imagine that people hear of Zope technology
Re: [Zope-dev] zope.interface compatibility question
--On 21. März 2008 23:17:51 +0100 Felix Schwarz [EMAIL PROTECTED] wrote: I hope this is the right list for my question related to zope.interface: I use some (non-zope) software which uses zope.interface (currently 3.0.1). Now there is another software which needs a newer version of zope.interface. Is the zope.interface library (3.4) backwards compatible with 3.0.1? Can I expect that the old software will still work if I install the new library? The best thing is: try it out! Since your application has unittests, it should be easy to verify the functionality against a new version :-) -aj pgpCXM5z0w0Lq.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: zope.interface compatibility question
--On 22. März 2008 11:00:00 +0100 Felix Schwarz [EMAIL PROTECTED] wrote: Andreas Jung schrieb: The best thing is: try it out! Since your application has unittests, it should be easy to verify the functionality against a new version :-) The problem is more complicated unfortunately: I want to use z3c.rml which needs zope.schema, zope.interface and other packages. Fedora currently ships the old zope.interface (3.0) which seems to be too old for zope.schema 3.4. I built RPM packages for myself but thought about submitting these to Fedora. Therefore I have an undefined set of applications possible using zope.interface 3.0 (and relying on this version). Even if my custom application has a very good unit test coverage, this does not help the Fedora Project. On the other hand if there was a commitment to a stable (downwards compatible) API in 3.x, I think it would be much easier to get my RPMs into Fedora. Use buildout or virtualenv and don't care about your package restrictions. -aj pgpucyQaWNdj8.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Packaging Zope for Fedora
Hi, speaking as the Zope 2 release manager: I am strongly opposed against splitting Zope yourself into different packages and modules. With Zope 2 depending from various Zope 3 packages (roughly 80-90) we have already the situation to keep track which packages belong together. This will become even more complicated when each Zope 3 package will have its own life-cycle. I doubt that you as a package can keep track in a reliable way with those requirements. It is somewhat hard for me to follow. So why can't you leave the Zope source packages as they are? Splitting up Zope into even more packages is even more error-prone. Re-packaged Zope distributions always raised more problems in the past than they really solved. The deployment for Zope-based applications is nowadays based on zc.buildout. Serious solutions providers never go with distribution-specific packages. Andreas --On 21. März 2008 11:57:31 -0700 Timothy Selivanow [EMAIL PROTECTED] wrote: As the subject implies, I'm working on a package for Fedora. I've come across some missing dependencies, and some that are different versions. Because of the way that Python packages are put together (shared library environment), I'm trying to strip out everything that is not Zope specific (e.g. mechanize, docutils, etc.) that way Zope won't clobber already existing packages, and new packages won't clobber Zope. Here is my list (that I've discovered so far...) and some notes and questions. I would appreciate any information on resolving these. My list was taken from Zope-3.4.0c1/build/lib.linux-x86_64-2.5 (in my arch specific case...) after doing a `python install.py build` (side note, why is it called install.py and not setup.py?). BTrees -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? ClientForm -- This currently exists in Fedora (version 0.2.7) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? twisted -- This currently exists in Fedora (version 2.4.0) Diffing the directories reveals that is it mostly compatible, however, missing some features (I have a list). What parts are required by Zope? Some of the missing parts are no longer being maintained, or are incompatible with newest Twisted (2.5.0). Thoughts? mechanize -- This currently exists in Fedora (version 0.1.6) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? persistent -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? pytz -- This currently exists in Fedora (version 2006p) Diffing the directories and files reveals differences. What version is required for Zope? What about newer versions? The Zope versions do not have the .py extension. Possible problems with Zope if they do (i.e., lib resolving)? RestrictedPython -- Does not currently exist in Fedora as a separate package. Is this it? http://pypi.python.org/pypi/RestrictedPython/3.4.2 Required version for Zope? What about newer versions? ThreadedAsync -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If Zope origin, is it useful outside of Zope? transaction -- Does not currently exist in Fedora as a separate package. Is this of Zope origin? (If not, where? Required version?) If not Zope origin, is it useful outside of Zope? Also, there is an existing package in Fedora called python-zope-interface, version 3.0.1 I assume (in F8), and I'm wondering if it would be worth keeping separate (or at least available, updated, maybe with a Conflicts: zope) in Fedora and are there other parts of Zope (e.g. ZODB, ZEO) that would be useful by themselves? I'm sorry if this seems daunting (it is on my side ;) and/or demanding, but I would like this packaged the best possible way for both projects. Who knows, this might show up in future RHEL versions (maybe I'm delusional ;) Thank you for your time and patience. --Tim _ / According to Kentucky state law, every person must take a bath at least \ \ once a year. / -\ \ \ \ /\ ( ) .( o ). ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org
Re: [Zope-dev] Re: Reducing dependencies of zope.publisher
--On 21. März 2008 19:20:46 + Martin Aspeli [EMAIL PROTECTED] wrote: One thing that sucks right now for the repoze.zope2 story is that Zope 2 isn't officially packaged in an egg-friendly form so the Repoze guys have to repackage it. It'd be great to be able to get Zope 2 released in a way that can at least optionally be installable as eggs. I think this should be a major goal for Zope 2.12. We possibly will have a Zope-(2 oriented) sprint in summer in Germany. If there are volunteers and interest I could add this to the possible sprint topics. Feedback welcome. Andreas pgpgRkQooVauX.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Building / installing Zope on AIX 5.3
--On 19. März 2008 09:31:42 -0300 Marcello Bax [EMAIL PROTECTED] wrote: Hello, I compiled Python 2.4.4 on AIX 5.3, with cc_r compiler, installed Zope-2.9.8and Plone-2.5.1. Everything seems work well, excepted when I call Plone on the browser or click on the view tab inside one Plone site at the ZMI. When I do this, I get a Segmentation fault on the server. Can anyone help me with this issue? Are there many AIX and Zope box running Plone? no I found this text in at Zope-2.9/doc/PLATFORMS/AIX.txt : from Wolfgang Roesner (reporting segfaults and a fix) The default stack size for a pthread on AIX (at least in my configuration) is 96kB. On Solaris it's 1M. As soon as I explicitly set the initial stack size to 1M the problem went away and it appears as if Zope is up and running. Unfortunately I really had to change thread_pthread.h in Python which obviously is not a nice thing to do as I now have a need for my own private version of Python. But at least I have a running version of Zope on AIX. I tested Plone on AIX lately with some pre-build binary from IBM...pretty much unusable. After compiling Python on my own: no further problems. Private Python installations are in general considered being best-practice. -aj pgpD4r6OpnvZB.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: zope.sendmail Retry fixes and new state machine.
--On 11. März 2008 09:42:11 -0300 David Pratt [EMAIL PROTECTED] wrote: Hi Andreas. I think your response gets to the heart of the issue. For software to be useful, it is often more important for folks other than the author to understand it. This can only occur with communication. Sometimes it is the understanding of edgecases in particular, that gets lost over time. I find generally that I cannot keep in memory all of the details of the code I write. Several months afterwards without my own documentation, these details can be lost. So it is just important if I need to come back to it myself as for anyone else. You can also document your edgecase in the same way as comments within your unittests. It matters that you have tests for the related edgecases. It's up to every developer to decide which test type is best for the individual case. If you're good in story telling (I am not so good), go with doctest but there can not be law that everything must be in doctests. If the test is worth writing, it is not difficult to add a small amount of text to communicate about it. If the software is worth writing in the first place, I consider the code incomplete without doctests. For community projects, it is often the case that it is not the author maintaining the code in the future. This only strengthens the argument for doctests and the reason this has become the standard for zope. Agreed. But unittests are for certain tests more suitable. E.g. if you need a complex and bigger fixture or something like that. Andreas pgpD0OJ80QkUV.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: zope.sendmail Retry fixes and new state machine.
--On 10. März 2008 22:33:13 -0500 Stephan Richter [EMAIL PROTECTED] wrote: On Monday 10 March 2008, Wichert Akkerman wrote: Indeed, and for that reason this can't be said enough. Doctests are useful to create testable documentation. They are not the right tool to create isolated, debuggable tests. Huh? I totally disagree. If you cannot explain your software in words, you do not understand it. As there are different kinds of programmatic tests, you can easily write different levels of doctests that have different audiences. This sounds like writing doctests just for sake of having doctests for all and everything. I completely disagree with that. In complex algorithms edgecases are often only of interest for the person implementing the code in order for having a safety belt. For writing good doctests you have to be a good (English) writer at some point. Doctests come into the game if you want to tell other people about the usage of your module. It's basically not of interest for telling them all edgecases. Addressing edgecase is unittests is basically good enough for me. They sometime require more code to test and put this into a doctest is often just overhead. Andreas pgpNQuUhN2HLl.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.sendmail Retry fixes and new state machine.
--On 9. März 2008 21:11:21 +1300 Matthew Grant [EMAIL PROTECTED] wrote: Hi! Just created a new branch for zope.sendmail. This is a result of the state machine analysis work I did on it after finding that it was creating problems on sending mail to our smart host... svn+ssh://[EMAIL PROTECTED]/repos/main/zope.sendmail/branches/grantma- retryfixes with lots of juicy new fixes including: - Restructured SMTP mailer and QueueProcessorThread so that all SMTP error logic is in the mailer. Clears the way for another mailer for /usr/sbin/sendmail command line can be used with QueueProcessorThread. - Added ability for QueueProcessorThread so that it can handle temporary failures in delivery to its smart host - ie administrator reconfiguring mailserver, mail server reboot/restart This was the main error path that was missing from the trunk code's state machine. - Formatted log messages in a consistent fashion so that they can be grepped out of z3.log - Added maildir message filename to log messages as message id - allows easy analysis/triage of mail message sending problems - Added optional cleaning of lock links to QueueProcessorThread so that messages can be resent immediately on Zope3 restart. - Added pollingInterval (ms), cleanLockLinks (boolean), and retryInterval (seconds) configure options to configure.zcml. Comments welcomed. I know it is a major portion of code and a bit of a restructure, but I have created unit tests for all my major changes. It includes all the stuff that was missing and that was needed for our production server. This sounds pretty impressing! Tnx, Andreas pgpvMnCWGxMaB.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
