Re: [Zope-dev] procedures for moving package to github and porting to Python 3
On 3/1/13 5:29 PM, Stephan Richter wrote: On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote: megrok.menu It's done now, but it lost its 0.1 tag due to a conversion issue. Great! And thanks again! regards, jw ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 18, OK: 13
On Mon, Mar 04, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Repository policy check found errors in 436 projects Contains a broken link to http://uter.gocept.com/~ctheune/report-2013-03-03T02:15:02.792640.txt (Host uter.gocept.com not found: 3(NXDOMAIN)) I suspect the script doesn't know about MOVED_TO_GITHUB and therefore complains about missing LICENCE.txt etc. [2]Still Failing - zopetoolkit_trunk - Build # 190 Early in the build there's + ./bin/develop up -f /tmp/hudson7093928157358980278.sh: 1: ./bin/develop: not found what's that about? It doesn't seem to break the build (and the develop script is, apparently, generated later and then executed successfully). The failure is here: + ./bin/buildout -t 3 -v -c development-python.cfg While: Initializing. Error: Couldn't open /home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/development-python.cfg [3]Total languishing bugs for zope: 69 I think it was the first time I read this summary (shame on me etc. etc.), it was rather interesting. I closed https://bugs.launchpad.net/z3c.form/+bug/1125906 (please move to github) [4]Total languishing bugs for zopeapp: 1 [5]Total languishing bugs for zopetoolkit: 205 I closed https://bugs.launchpad.net/zope.datetime/+bug/642474 (please make setup.py test work[1]), because it was fixed during the porting effort. [1] Here I use quotation marks for my paraphrasings instead of actual citations. Apologies for playing fast an loose with punctuation. There are a lot of Turn package documentation into Sphinx style bugs. I think a http://zope3.pov.lt/py3/ style summary page might be more useful for tracking this, but maybe that's just me. I closed https://bugs.launchpad.net/zope.interface/+bug/140875 because binary Windows eggs for zope.interface exist (and have existed for quite a while). Closed https://bugs.launchpad.net/zope.interface/+bug/911995 (class-advice decorators should fail loudly, not silently, in Python 3) because it's been fixed in 4.0.0 AFAIU. Marked https://bugs.launchpad.net/zope.interface/+bug/1090762 as incomplete because it's about zope.interface 4.0.2 and now 4.0.5 is out, and also because I don't understand what the problem is. My, those Turn package documentation into Sphinx style bugs aren't helpful at all. Closed https://bugs.launchpad.net/zope.sequencesort/+bug/642481 (make setup.py test work) by applying the supplied patch. This also made tests fail under Python 3 and confirmed the recent report about the port being somewhat incomplete. tox/detox make it easy to not notice when your test setup is incorrect (e.g. no tests are run, or test failures do not cause sys.exit(1)). I tripped on this thing with zope.testrunner once. I tried to fix the tests under Python 3.[23], but got bogged down in the various TypeError: unorderable types: dict() dict() errors. Help? Closed https://bugs.launchpad.net/zope.session/+bug/353647 (zope.session 3.6 doesn't work on Python 2.4) because there's a comment claiming 3.6.1 fixed that. In 2009. And nobody ever contradicted. Closed https://bugs.launchpad.net/zope.structuredtext/+bug/642481 because it's been fixed. Reassigned 16 zope.testing bugs dealing with the test runner to zope.testrunner. Noticed that I cannot change the importance field of zope.testrunner's bugs (I can change it for zope.testing's bugs). *whew* That was a bit depressing. [6]winbot / z3c.contents_py_265_32 [7]winbot / z3c.form_py_265_32 [8]winbot / z3c.formui_py_265_32 [10] winbot / z3c.pagelet_py_265_32 lxml [9]winbot / z3c.language.switch_py_265_32 ImportError: No module named (zope.app.)testing [11] winbot / zc.resourcelibrary_py_265_32 WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\temp\\buildout-l9qzwt' [12] winbot / zope.app.authentication_py_265_32 Unicode principal IDs [13] winbot / zope.app.http_py_265_32 [15] winbot / zope.app.publication_py_265_32 ImportError: No module named webtest [14] winbot / zope.app.pagetemplate_py_265_32 \r\n [16] winbot / zope.app.renderer_py_265_32 Initialized empty Git repository in c:/buildslave/zope.app.renderer/source/.git/ fatal: remote error: Repository not found. [17] winbot / zope.browserpage_py_265_32 \r\n [18] winbot / zope.formlib_py_265_32 Moved to github a while ago Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Switching zope.testbrowser to webtest instead of mechanize
Hello zope-dev, As you may already know, there is an effort to port zope packages to Python 3 going on. As part of this effort we want to port zope.testbrowser. Unfortunately, mechanize package, that zope.testbrowser depends on has no py3 support. There is an unfinished effort at [1], however, after closer examination of the codebase and state of the port, it seems more practical to switch internal implementation of zope.testbrowser to webtest. So far, it seems webtest has all the features needed to do the switch. I started a branch at github ([2]) to track work in progress. The goal is to make most (say 80%) of existing tests to work without modifications under new implementation. [1] http://web.cecs.pdx.edu/~adevore/mechanize/ [2] https://github.com/zopefoundation/zope.testbrowser/tree/webtest -- Andrey Lebedev aka -.- . -.. -.. . .-. Software engineer Homepage: http://lebedev.lt/ Jabber ID: ked...@jabber.ru ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] GitHub and Travis CI
Hi everyone, I have invested some time today to implement the Travis CI hook setup for GitHub. I can now turn on and update Travis CI for any package. Right now, there is no reporting setup. But Travis CI can be configured to send out E-mails and give IRC notifications. In addition, Marius added this to his sample project: https://github.com/zopefoundation/zope.dottedname See the ``README.rst`` file. So my question is: What do we want to do? I would suggest E-mails on status change should be sufficient. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] GitHub and Travis CI
On Mon, Mar 4, 2013 at 8:00 PM, Stephan Richter stephan.rich...@gmail.com wrote: So my question is: What do we want to do? I would suggest E-mails on status change should be sufficient. Cool, but please change the default email notification, it's set to spam everyone all the time. See http://about.travis-ci.org/docs/user/notifications/#Notifications So until we have a good policy, please use: notifications: email: false Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] ZTK 2.0: Deprecate zope.sequencesort
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2013 10:34 PM, Arfrever Frehtes Taifersar Arahesis wrote: 2013-02-28 21:04:33 Tres Seaver napisa?(a): I have ported it to Python 3.2 and 3.3 and released a 4.0.0 version. There are still multiple problems (types.TupleType, sys.modules.has_key etc.): $ PYTHONPATH=src python3.3 -c import zope.sequencesort Traceback (most recent call last): File string, line 1, in module File /tmp/zope.sequencesort/src/zope/sequencesort/__init__.py, line 14, in module from zope.sequencesort.ssort import sort File /tmp/zope.sequencesort/src/zope/sequencesort/ssort.py, line 17, in module from types import TupleType ImportError: cannot import name TupleType Weird: the tests seemed to run, but only the 'coverage' section was actually running. I just released 4.0.1 which fixes the remaining test breakage under Py3k. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlE1DswACgkQ+gerLs4ltQ4kuwCffWRNVmRlWxJ1TEUOGMlFiRWV ZAUAoIcnx6EYG4EyiyxeNGmm7GWj+yFu =5NvX -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 15, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-03-03 00:00:00 UTC and 2013-03-04 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 # 191 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 / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 [4]winbot / z3c.formui_py_265_32 [5]winbot / z3c.language.switch_py_265_32 [6]winbot / z3c.menu.ready2go_py_265_32 [7]winbot / z3c.pagelet_py_265_32 [8]winbot / zc.resourcelibrary_py_265_32 [9]winbot / zope.app.authentication_py_265_32 [10] winbot / zope.app.http_py_265_32 [11] winbot / zope.app.pagetemplate_py_265_32 [12] winbot / zope.app.publication_py_265_32 [13] winbot / zope.app.renderer_py_265_32 [14] winbot / zope.browserpage_py_265_32 [15] winbot / zope.formlib_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 # 191 https://mail.zope.org/pipermail/zope-tests/2013-March/073041.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073039.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073034.html [4]FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073038.html [5]FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073040.html [6]FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073035.html [7]FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073032.html [8]FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073058.html [9]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073056.html [10] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073057.html [11] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073036.html [12] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073055.html [13] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073033.html [14] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073054.html [15] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073037.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 15, OK: 12
On Tue, Mar 05, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 191 Error: Couldn't open /home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/development-python.cfg [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 [4]winbot / z3c.formui_py_265_32 [7]winbot / z3c.pagelet_py_265_32 lxml [5]winbot / z3c.language.switch_py_265_32 ImportError: No module named (zope.app.)testing [6]winbot / z3c.menu.ready2go_py_265_32 [15] winbot / zope.formlib_py_265_32 Moved to github. [8]winbot / zc.resourcelibrary_py_265_32 WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\temp\\buildout-l9qzwt' Strange. Adam rebooted winbot last morning, so it's not some hung old process holding a file open. [9]winbot / zope.app.authentication_py_265_32o Unicode principal IDs [10] winbot / zope.app.http_py_265_32 [12] winbot / zope.app.publication_py_265_32 ImportError: No module named webtest [11] winbot / zope.app.pagetemplate_py_265_32 [14] winbot / zope.browserpage_py_265_32 \r\n [13] winbot / zope.app.renderer_py_265_32 It's been renamed to zope.renderer; winbot needs to be told (and I'd like a BBB release on PyPI that urges every user to change their imports via DeprecationWarnings) Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] GitHub and Travis CI
On 03/04/2013 08:00 PM, Stephan Richter wrote: So my question is: What do we want to do? I would suggest E-mails on status change should be sufficient. And probably include the status in the usual daily zope-test email. Tho no idea where that script is running and where the source is. -- Best regards, Adam GROSZER -- Quote of the day: What makes the universe so hard to comprehend is that there's nothing to compare it with. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Who has the winbot/rackspace creds?
Hello, It would be time to do a backup/snapshot of the VM. -- Best regards, Adam GROSZER -- Quote of the day: The man who smiles when things go wrong has thought of someone he can blame it on. - Jones' Law ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
