Zope-Dev February 2013

zope-dev@zope.dev

24 participants
68 discussions

Re: [Zope-dev] zope.security with Py3
by Tres Seaver 08 Mar '13

08 Mar '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/12/2013 10:47 PM, Stephan Richter wrote: > I saw you finished test coverage tonight for zope.security. What is > your timeline to do the port to Python 3? Our efforts are blocked > until we get zope.security going. We would be willing to take a shot > at the port, but you have just done all the hard work writing the > tests, so I do not want to steal the momentum from you. Now that the test coverage is in place, I plan to finish the Py3k conversion today, or tomorrow at the latest. 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 undefined - http://www.enigmail.net/ iEYEARECAAYFAlEbuYMACgkQ+gerLs4ltQ4s3wCbBYky/rRSkkTnQPfkq6IJqwpq OQIAniAIFP3aBX/grlHM7wFcSYzknfCg =l8QV -----END PGP SIGNATURE-----

2 5

ZTK 2.0: Deprecate zope.sequencesort
by Stephan Richter 04 Mar '13

04 Mar '13

Hi everyone, I would like to deprecate zope.sequencesort in ZTK 2.0, since it cannot properly ported to Python 3, since it depends heavily on the cmp() way of sorting. I am also not a user of the package and I only tried to port the package for completeness sake. Thoughts? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

9 20

Zope2 git mirror not updating?
by Wichert Akkerman 02 Mar '13

02 Mar '13

I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly? Wichert.

3 3

ZTK Porting Status
by Stephan Richter 28 Feb '13

28 Feb '13

Hi all, I went through the ztk-versions.cfg file and verified availability of a Python 3 port. I commented the ztk-versions.cfg file. Below are the relevant sections. If we remove all deprecated pacakges and packages that should not be in use anymore, only the following dependencies/toolchain packages require a Python 3 port: z3c.checkversions z3c.recipe.compattest zope.kgs zc.resourcelibrary zope.mkzeoinstance ZODB (awaiting merge of py3 branch) Luckily we control all these packages. These packages should just be removed from the file: # Deprecating # zope.broken was only needed for ZODB3. zope.broken = 3.6.0 # zope.server has been forked and ported to Py3 under the name "waitress". zope.server = 3.8.6 # RestrictedPython and thus zope.untrustedpython are hard to port to Py3. zope.untrustedpython = 4.0.0 # No package should depend on ZODB3 anymore. ZODB3 = 3.11.0a2 # mechanize should only be needed for testbrowser. mechanize = 0.2.5 Dependencies missing a Python 3 port: # XXX: Where do we need that? Paste = 1.7.5.1 # PasteScript should not be needed anymore, since zope.paste supports serving # directly now. PasteScript = 1.7.5 # Fix by removing it from the ZTK? RestrictedPython = 3.6.0 # XXX: Where is this needed? unittest2 = 0.5.1 # Should just be ported. zc.resourcelibrary = 1.3.4 zope.mkzeoinstance = 3.9.5 # Needs merge of py3 branch. ZODB = 4.0.0a4 # toolchain # Missing py3 port z3c.checkversions = 0.4.1 # Missing py3 port z3c.recipe.compattest = 0.13.1 # Should not be needed anymore: z3c.recipe.scripts = 1.0.1 # Missing py3 port zope.kgs = 1.2.0 Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

2 1

zope-tests - FAILED: 22, OK: 12, UNKNOWN: 2
by Zope tests summarizer 28 Feb '13

28 Feb '13

This is the summary for test reports received on the zope-tests list between 2013-02-26 00:00:00 UTC and 2013-02-27 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] Still Failing - zopetoolkit_trunk - Build # 186 [2] Still Failing - zopetoolkit_trunk_app - Build # 168 [3] UNKNOWN : Zope-trunk Python-2.6.8 : Linux [4] UNKNOWN : Zope-trunk Python-2.7.3 : 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 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 / z3c.authenticator_py_265_32 [6] winbot / z3c.breadcrumb_py_265_32 [7] winbot / z3c.configurator_py_265_32 [8] winbot / z3c.contents_py_265_32 [9] winbot / z3c.form_py_265_32 [10] winbot / z3c.formui_py_265_32 [11] winbot / z3c.pagelet_py_265_32 [12] winbot / z3c.sampledata_py_265_32 [13] winbot / zc.resourcelibrary_py_265_32 [14] winbot / zope.app.pagetemplate_py_265_32 [15] winbot / zope.app.server_py_265_32 [16] winbot / zope.app.server_py_265_32 [17] winbot / zope.app.wsgi_py_265_32 [18] winbot / zope.browserpage_py_265_32 [19] winbot / zope.generations_py_265_32 [20] winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 [21] winbot / ztk_10 py_265_win64 [22] winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 [23] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [24] winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED Still Failing - zopetoolkit_trunk - Build # 186 https://mail.zope.org/pipermail/zope-tests/2013-February/072879.html [2] FAILED Still Failing - zopetoolkit_trunk_app - Build # 168 https://mail.zope.org/pipermail/zope-tests/2013-February/072878.html [3] UNKNOWN UNKNOWN : Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072885.html [4] UNKNOWN UNKNOWN : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072886.html [5] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072901.html [6] FAILED winbot / z3c.breadcrumb_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072899.html [7] FAILED winbot / z3c.configurator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072905.html [8] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072902.html [9] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072908.html [10] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072877.html [11] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072904.html [12] FAILED winbot / z3c.sampledata_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072907.html [13] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072906.html [14] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072875.html [15] FAILED winbot / zope.app.server_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072909.html [16] FAILED winbot / zope.app.server_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072874.html [17] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072900.html [18] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072903.html [19] FAILED winbot / zope.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072876.html [20] FAILED winbot / ztk_10 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072887.html [21] FAILED winbot / ztk_10 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072889.html [22] FAILED winbot / ztk_11 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072890.html [23] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072892.html [24] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072894.html

5 6

ZTK 2.0 process
by Stephan Richter 27 Feb '13

27 Feb '13

Hi everyone, what is the process to start working on ZTK 2.0? We are about 5-6 packages away from porting ZTK to Python 3 and I would like to start working on a new release. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

7 10

zope-tests - FAILED: 21, OK: 15, UNKNOWN: 1
by Zope tests summarizer 27 Feb '13

27 Feb '13

This is the summary for test reports received on the zope-tests list between 2013-02-25 00:00:00 UTC and 2013-02-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 ---------------- [1] FAILED (failures=1) : Zope-trunk Python-2.7.3 : Linux [2] Still Failing - zopetoolkit_trunk - Build # 185 [3] Still Failing - zopetoolkit_trunk_app - Build # 167 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 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [4] winbot / z3c.authenticator_py_265_32 [5] winbot / z3c.contents_py_265_32 [6] winbot / z3c.form_py_265_32 [7] winbot / z3c.form_py_265_32 [8] winbot / z3c.formui_py_265_32 [9] winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsontree_py_265_32 [11] winbot / zc.resourcelibrary_py_265_32 [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.authentication_py_265_32 [14] winbot / zope.app.pagetemplate_py_265_32 [15] winbot / zope.app.wsgi_py_265_32 [16] winbot / zope.browserpage_py_265_32 [17] winbot / zope.generations_py_265_32 [18] winbot / zope.ptresource_py_265_32 [19] winbot / zope.ptresource_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 [20] winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 [21] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [22] winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] UNKNOWN FAILED (failures=1) : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072853.html [2] FAILED Still Failing - zopetoolkit_trunk - Build # 185 https://mail.zope.org/pipermail/zope-tests/2013-February/072845.html [3] FAILED Still Failing - zopetoolkit_trunk_app - Build # 167 https://mail.zope.org/pipermail/zope-tests/2013-February/072846.html [4] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072868.html [5] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072866.html [6] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072872.html [7] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072839.html [8] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072843.html [9] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072838.html [10] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072840.html [11] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072870.html [12] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072871.html [13] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072837.html [14] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072841.html [15] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072867.html [16] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072869.html [17] FAILED winbot / zope.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072844.html [18] FAILED winbot / zope.ptresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072873.html [19] FAILED winbot / zope.ptresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072842.html [20] FAILED winbot / ztk_11 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072857.html [21] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072859.html [22] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072861.html

4 5

zope-tests - FAILED: 21, OK: 19
by Zope tests summarizer 26 Feb '13

26 Feb '13

This is the summary for test reports received on the zope-tests list between 2013-02-24 00:00:00 UTC and 2013-02-25 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] Still Failing - zopetoolkit_trunk - Build # 184 [2] Still Failing - zopetoolkit_trunk_app - Build # 166 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 [3] winbot / z3c.authenticator_py_265_32 [4] winbot / z3c.authenticator_py_265_32 [5] winbot / z3c.contents_py_265_32 [6] winbot / z3c.contents_py_265_32 [7] winbot / z3c.form_py_265_32 [8] winbot / z3c.formui_py_265_32 [9] winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsontree_py_265_32 [11] winbot / z3c.layer.ready2go_py_265_32 [12] winbot / z3c.layer.ready2go_py_265_32 [13] winbot / z3c.recipe.paster_py_265_32 [14] winbot / zope.app.authentication_py_265_32 [15] winbot / zope.app.pagetemplate_py_265_32 [16] winbot / zope.app.wsgi_py_265_32 [17] winbot / zope.app.wsgi_py_265_32 [18] winbot / zope.browserpage_py_265_32 [19] winbot / zope.browserpage_py_265_32 [20] winbot / zope.sendmail_py_265_32 [21] winbot / zope.structuredtext_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 Still Failing - zopetoolkit_trunk - Build # 184 https://mail.zope.org/pipermail/zope-tests/2013-February/072810.html [2] FAILED Still Failing - zopetoolkit_trunk_app - Build # 166 https://mail.zope.org/pipermail/zope-tests/2013-February/072811.html [3] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072833.html [4] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072799.html [5] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072834.html [6] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072797.html [7] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072806.html [8] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072809.html [9] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072805.html [10] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072807.html [11] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072836.html [12] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072802.html [13] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072831.html [14] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072803.html [15] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072808.html [16] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072832.html [17] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072798.html [18] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072835.html [19] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072800.html [20] FAILED winbot / zope.sendmail_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072801.html [21] FAILED winbot / zope.structuredtext_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072804.html

4 7

Re: [Zope-dev] zope-tests - FAILED: 21, OK: 19
by Marius Gedminas 26 Feb '13

26 Feb '13

On Tue, Feb 26, 2013 at 08:48:10AM -0500, Stephan Richter wrote: > This brings up a bigger question: > > Even though, most ported packages are fully Python 3 compatible, they might > depend on packages that are not ready to get a final release. Those two are: > > * zope.security 4.0.0 (pending PyPy support from Tres) > * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.) > > Any package that depends directly or indirectly on those two packages has an > alpha release right now. Strictly speaking this is not necessary for any > package not depending on ZODB (ZODB is special because the dep changes from > ZODB3 to ZODB). > > If it is okay with everyone, we could change the releases to their final > version numbers with the understanding that Python 3 support will not be > available until all dependencies have their final release. Python 2 should work > just fine once we get the trunk builds back to green. I'm not a fan of non-alpha versions of packages depending on alpha versions of other packages, so -0.5. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development

1 0

Re: [Zope-dev] SVN: DateTime/trunk/ Moved to GitHub.
by Tres Seaver 25 Feb '13

25 Feb '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/25/2013 01:18 AM, Stephen Richter wrote: Premature. 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 undefined - http://www.enigmail.net/ iEYEARECAAYFAlEraxMACgkQ+gerLs4ltQ4kMwCgrOtFjTc3/ToGcLAmsRnZI1hB 8/0AoIP2T8BEoHEHlu7oKpkkWpJHRwOd =E33A -----END PGP SIGNATURE-----

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Zope-Dev February 2013