July 2012 - Zope-Dev

zope.intid and zope.keyreference.interfaces.NotYet exception (patch)
by Cykooz 04 Jul '12

04 Jul '12

Hi, I created a patch for a package zope.intid that almost completely solves the problem with the zope.keyreference.interfaces.NotYet exception. I implemented a deferred indexing of objects added to the container which is not connected to the ZODB. As soon as the container is added to the ZODB - all deferred objects will be indexed. I also added a marker IIntIdsDisabled for marking objects that must not be indexed. I would be grateful if someone could look at my changes and merge them into the main branch. My fork of zope.intid - https://bitbucket.org/cykooz/zope.intid/src PS: Sorry for my English. ------------------- Cykooz (Kirill Kuzminykh)

7 12

Re: [Zope-dev] [ZODB-Dev] RFC: release persistent as a standalone package
by Alan Runyan 03 Jul '12

03 Jul '12

> I would like to release a '4.0.0' version of the package, and switch > the ZODB trunk to pull it in as a dependency (deleting the currently > included (older) copy of persistent). One possible issue is that I > have not (yet) made the C extensions work under Python 3.2: I don't > know whether that should be a blocker for a release. I do not believe its a blocker. That is a "feature" that could be added. > Comments? You rock. -- Alan Runyan Skype/Twitter:: runyaga Office:: 713.942.2377 ext 111 http://ploud.com/ Plone site in less than 10 seconds

2 1

Re: [Zope-dev] SVN: zope.app.locales/trunk/ In version 3.7.2 msgids and default values where forced to be unicodes. This
by Tres Seaver 03 Jul '12

03 Jul '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/14/2012 08:13 AM, Michael Howitz wrote: > Log message for revision 125861: In version 3.7.2 msgids and default > values where forced to be unicodes. This was too strict because at > least the TAL extractor returns UTF-8 encoded default values. Fixed > this by allowing the default value to be a string again. <snip> > --- zope.app.locales/trunk/src/zope/app/locales/extract.py 2012-05-14 > 08:50:08 UTC (rev 125860) +++ > zope.app.locales/trunk/src/zope/app/locales/extract.py 2012-05-14 > 12:13:47 UTC (rev 125861) @@ -97,7 +97,7 @@ msgstr "" <BLANKLINE> > > - Unicode can be used in msgids and default values + Unicode can > be used in msgids and default values: > >>>> entry = POTEntry(Message(u"\u263B", default=u"\u253A")) >>>> entry.write(FakeFile()) > @@ -106,6 +106,16 @@ msgstr "" <BLANKLINE> > > + But msgid might be an ascii encoded string and `default` might be > a + string with the DEFAULT_ENCODING, too: + + >>> entry = > POTEntry(Message("Oe", default="\xd6")) + >>> > entry.write(FakeFile()) + #. Default: "\326" + msgid "Oe" + > msgstr "" + <BLANKLINE> + """ Hmm, I'm running into a test failure where the Message constructor blows up with a decode error for the 'default' value here. Does that ring any bells for anyone? I know we can't be depending on a sys.setdefaultencoding hack. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/t6b4ACgkQ+gerLs4ltQ4OAwCeK2Cm+Xm/OLy+adZGfOkQx/hk CakAoLQFXbtqQU9Jlm1ZfgtD58RwJ7wE =kFK2 -----END PGP SIGNATURE-----

2 2

zope-tests - FAILED: 2, OK: 22
by Zope tests summarizer 03 Jul '12

03 Jul '12

This is the summary for test reports received on the zope-tests list between 2012-07-01 00:00:00 UTC and 2012-07-02 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Zope 3.4 Known Good Set / py2.4-32bit-linux [1] Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / zope.app.container_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED Zope 3.4 Known Good Set / py2.4-64bit-linux https://mail.zope.org/pipermail/zope-tests/2012-July/064968.html [2] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064969.html

3 2

Re: [Zope-dev] RFC: release persistent as a standalone package
by Wolfgang Schnerring 02 Jul '12

02 Jul '12

* Tres Seaver <tseaver(a)palladion.com> [2012-06-30 20:02]: > I have completed the work needed to make 'persistent' distributable > as a standalone package. The effort (begun almost four years ago!) > includes the following highlights: > > I would like to release a '4.0.0' version of the package, and switch > the ZODB trunk to pull it in as a dependency (deleting the currently > included (older) copy of persistent). +1, please do. This seems like a(nother! :) Good Thing(tm) to me. Wolfgang

1 0

zope-tests - FAILED: 5, OK: 24
by Zope tests summarizer 02 Jul '12

02 Jul '12

This is the summary for test reports received on the zope-tests list between 2012-06-30 00:00:00 UTC and 2012-07-01 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] Repository policy check found errors in 274 projects Total languishing bugs for zope2: 0 [2] Total languishing bugs for zope: 62 [3] Total languishing bugs for zopeapp: 1 [4] Total languishing bugs for zopetoolkit: 198 Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [5] winbot / zope.app.container_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED Repository policy check found errors in 274 projects https://mail.zope.org/pipermail/zope-tests/2012-July/064944.html [2] FAILED Total languishing bugs for zope: 62 https://mail.zope.org/pipermail/zope-tests/2012-July/064941.html [3] FAILED Total languishing bugs for zopeapp: 1 https://mail.zope.org/pipermail/zope-tests/2012-July/064938.html [4] FAILED Total languishing bugs for zopetoolkit: 198 https://mail.zope.org/pipermail/zope-tests/2012-July/064939.html [5] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-July/064945.html

1 0

working with different requirements depending on python version
by Chris Withers 01 Jul '12

01 Jul '12

Hi All, While trying to debug another problem, I re-ran some Jenkins jobs for two of my packages, which promptly failed under Python 2.5: http://jenkins.simplistix.co.uk/job/testfixtures-buildout/ http://jenkins.simplistix.co.uk/job/checker-buildout/ Now, the issue here is that zope.interface 4.0 and above no longer supports Python 2.5: http://jenkins.simplistix.co.uk/job/checker-buildout/PYTHON=2.5,label=linux… http://pypi.python.org/pypi/zope.interface/4.0.0 That's fine, but I'd like the above projects to continue 2.5 support for the time being. The simple solution would be to add a versions section to the buildout here: https://github.com/Simplistix/checker/blob/master/buildout.cfg ...and pin the versions in the tox.ini here: https://github.com/Simplistix/checker/blob/master/tox.ini ...however, that doesn't give the correct result. The version requirement is "use the latest version of all packages that work with the Python version under test" and the changes I've suggested would mean that on Python 2.6 and 2.7, the latest version of zope.interface wouldn't be used. What makes this even more "interesting" is that zope.interface isn't a direct requirement of either of these projects, it's a dependency of a dependency in both cases. How have other people solved this? Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

2 2

Can't compile zope.interface 4.0.1 extensions on Mac OS with Py2.7
by Chris Withers 01 Jul '12

01 Jul '12

Hi All, Got this: Getting distribution for 'zope.interface'. In file included from /Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/unicodeobject.h:4, from /Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h:85, from src/zope/interface/_zope_interface_coptimizations.c:15: /Developer/SDKs/MacOSX10.6.sdk/usr/include/stdarg.h:4:25: error: stdarg.h: No such file or directory In file included from /Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/unicodeobject.h:4, from /Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h:85, from src/zope/interface/_zope_interface_coptimizations.c:15: /Developer/SDKs/MacOSX10.6.sdk/usr/include/stdarg.h:4:25: error: stdarg.h: No such file or directory lipo: can't figure out the architecture type of: /var/folders/m6/tsd59qsj7pd_lldh4mhwh6kh0000gn/T//cc4KmKtY.out ******************************************************************************** WARNING: An optional code optimization (C extension) could not be compiled. Optimizations for this package will not be available! () command 'gcc-4.2' failed with exit status 1 ******************************************************************************** Got zope.interface 4.0.1. Anyone seen that before? cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

1 0

Re: [Zope-dev] [ZODB-Dev] RFC: release persistent as a standalone package
by Leonardo Rochael Almeida 01 Jul '12

01 Jul '12

Hi Tres, I'm +1 on the change even without the answer to my next question, but can you elaborate on what is the advantage of releasing persistent appart from ZODB? Regards, Leo On Sat, Jun 30, 2012 at 8:02 PM, Tres Seaver <tseaver(a)palladion.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I have completed the work needed to make 'persistent' distributable > as a standalone package. The effort (begun almost four years ago!) > includes the following highlights: > > Platform Changes > - ---------------- > > - - Added explicit support for Python 3.2 and PyPy. > > - Note that the C implementations of Persistent, PickleCache, and > Timestamp are not built (yet) on these platforms. > > - - Dropped explicit support for Python < 2.6. > > - - Completed pure-Python reference implementations of 'Persistent', > 'PickleCache', and 'TimeStamp'. > > Testing Changes > - --------------- > > - - 100% unit test coverage. > > - - All covered platforms tested under 'tox'. > > - - Refactored some doctests as unittests. > > - - Removed all 'ZODB'-dependent tests: > > - Rewrote some to avoid the dependency > > - Cloned the remainder into new 'ZODB.tests' modules on the ZODB > trunk. > > - - Added support for continuous integration using 'tox' and 'jenkins'. > > - - Added 'setup.py dev' alias (installs 'nose' and 'coverage'). > > - - Dropped dependency on 'zope.testing' / 'zope.testrunner': tests now > run with 'setup.py test'. > > Documentation Changes > - --------------------- > > - - Refactored many doctests as Sphinx documentation > (snippets are exercised via 'tox'). > > - - Added 'setup.py docs' alias (installs 'Sphinx' and > 'repoze.sphinx.autointerface'). > > > I would like to release a '4.0.0' version of the package, and switch > the ZODB trunk to pull it in as a dependency (deleting the currently > included (older) copy of persistent). One possible issue is that I > have not (yet) made the C extensions work under Python 3.2: I don't > know whether that should be a blocker for a release. > > Comments? > > > Tres. > - -- > =================================================================== > Tres Seaver +1 540-429-0999 tseaver(a)palladion.com > Palladion Software "Excellence by Design" http://palladion.com > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk/vPyMACgkQ+gerLs4ltQ4DsgCfRsKhBzvTWHehVI86I5sryhjF > whQAoL3evyI6GKOfa7eDVjTUVh7B8Q+/ > =82vd > -----END PGP SIGNATURE----- > > _______________________________________________ > For more information about ZODB, see http://zodb.org/ > > ZODB-Dev mailing list - ZODB-Dev(a)zope.org > https://mail.zope.org/mailman/listinfo/zodb-dev

2 1

zope-tests - OK: 23
by Zope tests summarizer 01 Jul '12

01 Jul '12

This is the summary for test reports received on the zope-tests list between 2012-06-25 00:00:00 UTC and 2012-06-26 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results --------------

4 6