February 2013 - Zope-Dev

Re: [Zope-dev] zdaemon test dependencies
by Jim Fulton 13 Feb '13

13 Feb '13

On Wed, Feb 13, 2013 at 12:16 PM, Stephan Richter <stephan.richter(a)gmail.com> wrote: > On Wednesday, February 13, 2013 09:27:46 AM Jim Fulton wrote: >> > Both options are fine with me. Your choice. :-) >> >> Ah. For now, I'd skip the JS-integration tests for Python 3. > > Okay, all done. Can you make me an PyPI owner of zc.customdoctests? My > username is 'srichter'. Done. Thanks. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm

1 0

Re: [Zope-dev] zdaemon test dependencies
by Jim Fulton 13 Feb '13

13 Feb '13

On Wed, Feb 13, 2013 at 9:39 AM, Stephan Richter <stephan.richter(a)gmail.com> wrote: > On Wednesday, February 13, 2013 09:27:46 AM Jim Fulton wrote: >> OT, will you volunteer for the ZF board? > > I would. Thanks! > Feel free to nominate me, Done. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm

1 0

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

13 Feb '13

This is the summary for test reports received on the zope-tests list between 2013-02-11 00:00:00 UTC and 2013-02-12 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] Failure - zopetoolkit_trunk - Build # 170 [2] Failure - zopetoolkit_trunk_app - Build # 153 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.datagenerator_py_265_32 [4] winbot / z3c.recipe.paster_py_265_32 [5] winbot / z3c.recipe.paster_py_265_32 [6] winbot / zope.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 Failure - zopetoolkit_trunk - Build # 170 https://mail.zope.org/pipermail/zope-tests/2013-February/072242.html [2] FAILED Failure - zopetoolkit_trunk_app - Build # 153 https://mail.zope.org/pipermail/zope-tests/2013-February/072243.html [3] FAILED winbot / z3c.datagenerator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072265.html [4] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072263.html [5] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072241.html [6] FAILED winbot / zope.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072264.html

2 1

Re: [Zope-dev] zdaemon test dependencies
by Jim Fulton 13 Feb '13

13 Feb '13

On Wed, Feb 13, 2013 at 9:21 AM, Stephan Richter <stephan.richter(a)gmail.com> wrote: > On Wednesday, February 13, 2013 09:13:52 AM Jim Fulton wrote: >> On Wed, Feb 13, 2013 at 8:36 AM, Stephan Richter >> >> <stephan.richter(a)gmail.com> wrote: >> > On Wednesday, February 13, 2013 07:16:03 AM Jim Fulton wrote: >> >> I would make a javascript extra for customdoctests that requires >> >> spidermonkey. >> > >> > Okay, and then have two test runners, one running without spidermonkey and >> > one with and conditionalize the tests? >> >> I wouldn't bother. > > But in order to test zc.customdoctests' Py3 compatibility I need to run its > tests. So I have 2 choices: > > 1. Remove all spidermonkey integration tests. > 2. Run all spidermonkey integration tests only on Python 2. > > Both options are fine with me. Your choice. :-) Ah. For now, I'd skip the JS-integration tests for Python 3. OT, will you volunteer for the ZF board? Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm

1 0

Re: [Zope-dev] zdaemon test dependencies
by Jim Fulton 13 Feb '13

13 Feb '13

On Wed, Feb 13, 2013 at 8:36 AM, Stephan Richter <stephan.richter(a)gmail.com> wrote: > On Wednesday, February 13, 2013 07:16:03 AM Jim Fulton wrote: >> I would make a javascript extra for customdoctests that requires >> spidermonkey. > > Okay, and then have two test runners, one running without spidermonkey and one > with and conditionalize the tests? I wouldn't bother. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm

1 0

Git conversion with svn-all-fast-export
by Marius Gedminas 13 Feb '13

13 Feb '13

You need: - svn-all-fast-export (from the Debian/Ubuntu package of the same name; upstream homepage is http://gitorious.org/svn2git, not related to a Ruby tool of the same name) - a copy of the Subversion repository Good thing I have one set up, using svnsync: # http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposa… svnadmin create /stuff/zope-mirror svnadmin setuuid /stuff/zope-mirror 62d5b8a3-27da-0310-9561-8e5933582275 svnsync init file:///stuff/zope-mirror svn://svn.zope.org/repos/main/ svnsync sync file:///stuff/zope-mirror # repeat last command periodically It needs about 3.3 gigs of disk space. - a copy of authors.txt that maps svn usernames to real names and emails (ask Tres or Jim) - an empty repository on Github (ask Tres or Jim to create one at https://github.com/zopefoundation) Speaking of this, could somebody create a zope.dottedname repo? Thanks. The conversion process goes like this: - write a rules.txt like this one I used for zope.dottedname: create repository zope.dottedname end repository # feel free to create multiple repositories in one go # order of matches matters in this file # trailing slashes in match rules are very important match / # skip revisions 129030, 129031 and 129032, since they're empty # in my svn mirror (no files, no committer, no date) for some reason # (bug in svnsync?), and they make svn-all-fast-export segfault min revision 129030 max revision 129032 end match match /(zope\.dottedname)/trunk/ repository \1 branch master end match match /(zope\.dottedname)/branches/([^/]+)/ repository \1 branch \2 end match match /(zope\.dottedname)/tags/([^/]+)/ repository \1 branch refs/tags/\2 end match match / # ignore all other projects end match - run svn-all-fast-export --identity-map=authors.txt --rules=rules.txt --stats \ /path/to/your/zope-svn-mirror - wait a bit The first time I ran it it took ~18 wall clock minutes (~4 CPU minutes) and ended in a segfault. The second run took 12 wall clock minutes (hot disk cache, I suppose) and also ended in a segfault. Then I discovered that if I don't remove the git repository, svn-all-fast-export will resume the process (a few thousand revisions before it crashed, or maybe that just happened to be the last successfully converted commit before the crash), which is considerably faster than starting from scratch. - inspect ./zope.dottedname for sanity I recommend tig as a very nice console-mode interactive git history viewer. For an example of things to inspect, e.g., there was a deleted 3.4.1 tag from http://zope3.pov.lt/trac/changeset/80495, which shouldn't have been deleted, according to http://zope3.pov.lt/trac/changeset/80499, so I've re-created the tag from refs/backups/r80495/tags/3.4.1 that was left by the conversion tool. - upload to github Advantages of svn-all-fast-export - it's fast (<5 CPU minutes for 129128 svn revisions; I wish I had an SSD on the server that hosts my svn mirror) - it can simultaneously convert multiple packages (add more 'create repository/end repository' statements to rules.txt, and extend the match regexps to catch the packages you're interested in) - it's very flexible and can handle gnarly repository history, if you write rules for it - it was written for and used by the KDE project to convert and explode their humongous svn repository into a multitude of git projects, so it's been stress-tested rather well Disadvantages of svn-all-fast-export - it requires a local copy of the entire subversion repository - it doesn't produce error messages if something's wrong, instead it segfaults Incidentally, I'd like to hear reports about conversion speed from people (e.g. Jim ;-) who have used Jim's conversion script. Is 12 minutes fast or slow? zope.dottedname is not a very large package; it had merely 34 revisions in trunk's history. I would also like to offer my services as a git conversion specialist, since I have access to an svn mirror. Ask me for a package by name, and I'll send you a git repository in a few days. It'll be up to you to inspect the fidelity of the conversion, though; I don't have the spare cycles for that. Regards, Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development

2 5

Style guide update?
by Fred Drake 13 Feb '13

13 Feb '13

At one point, we had a style guide that recommended simple "import <module>" import statements for Zope code: http://wiki.zope.org/zope3/ZopePythonStyleGuide Today, I'm noticing a lot of commits with the change note "Normalize imports" that change all imports to "from <module> import whatever", like this one: https://github.com/zopefoundation/zope.security/commit/115691fce9c80a340f27… Do we still have an agreed-upon style guide, or are we moving to a last-touched-by approach? -Fred -- Fred L. Drake, Jr. <fred at fdrake.net> "A storm broke loose in my mind." --Albert Einstein

3 2

Re: [Zope-dev] zdaemon test dependencies
by Jim Fulton 13 Feb '13

13 Feb '13

On Tue, Feb 12, 2013 at 11:10 PM, Stephan Richter <stephan.richter(a)gmail.com> wrote: > Hi Jim, > > I am trying to get closer to get zope.site ported to Python 3. This requires > porting of ZODB, which in turn requires zdaemon to be ported. So far so good. > But then zdaemon has zc.customdoctests as a test requirement, which then needs > python-spidermonkey. That sounds like a bug. > Since we do not control python-spidermonkey, I would like to break the > dependency path somewhere. +1 > I was thinking about having the zdaemon tests that > require zc.customdoctests only run in Python 2. Does this sound good? No. I would make a javascript extra for customdoctests that requires spidermonkey. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm

1 0

Re: [Zope-dev] PyPI access to zc.lockfile
by Jim Fulton 12 Feb '13

12 Feb '13

On Tue, Feb 12, 2013 at 3:35 PM, Stephan Richter <stephan.richter(a)gmail.com> wrote: > On Tuesday, February 12, 2013 01:29:43 PM Jim Fulton wrote: >> > can you give me access to zc.lockfile, so I can upload a new release? >> >> PyPI id? > > srichter Done. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm

1 0

Re: [Zope-dev] [zopefoundation/zope.security] 390d12: zope.security.untrustedpython moved to separate pr...
by Tres Seaver 12 Feb '13

12 Feb '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/12/2013 12:23 PM, GitHub wrote: > Branch: refs/heads/master Home: > https://github.com/zopefoundation/zope.security Commit: > 390d1258382d5473388fb6d2fc80f392d4991cf8 > https://github.com/zopefoundation/zope.security/commit/390d1258382d5473388f… > > Author: Andrey Lebedev <andrey(a)lebedev.lt> > Date: 2013-02-12 (Tue, 12 Feb 2013) > > Changed paths: M CHANGES.rst M buildout.cfg M setup.py R > src/zope/security/untrustedpython/__init__.py R > src/zope/security/untrustedpython/builtins.py R > src/zope/security/untrustedpython/interpreter.py R > src/zope/security/untrustedpython/rcompile.py > > Log Message: ----------- zope.security.untrustedpython moved to > separate project > > The code was extracted to zope.untrustedpython project to simplify > porting zope.security to python-3.x. This change broke the doctest snippets in the Sphinx docs: Document: narr - -------------- ********************************************************************** File "narr.rst", line 571, in default Failed example: from zope.security.untrustedpython.builtins import SafeBuiltins Exception raised: Traceback (most recent call last): File "/opt/Python-2.6.8/lib/python2.6/doctest.py", line 1253, in __run compileflags, 1) in test.globs File "<doctest default[0]>", line 1, in <module> from zope.security.untrustedpython.builtins import SafeBuiltins ImportError: No module named untrustedpython.builtins (and many more failures after that) I'm guessing that those document sections (pretty much everything from "Safe Builtins" to the end of narr.rst) should all be moved to the new project's own Sphinx docs. 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/ iEYEARECAAYFAlEai5kACgkQ+gerLs4ltQ6TrgCgoJfzpZoXDsWpBtYQxUUk6sdr 5AQAnjQ0ayvAnmFrvZK1WpqUZyJk3nsf =1r9K -----END PGP SIGNATURE-----

1 0