Re: [Zope-dev] ZTK 2.0: Deprecate zope.sequencesort
On Fri, Mar 1, 2013 at 4:04 AM, Tres Seaver tsea...@palladion.com wrote: Assuming an unsorted list of news stories, how would you use sorted to get them ordered by category (ascending) + publication date (descending)? This is the easiest, most obvious way: sorted(sorted(news_stories, lambda x: x.publication_date, reverse=True), lambda x: x.category) And yes, I have made performance analysis, and it is often faster two do two sorts than trying to compute a complex key. If you spend more than a minute on it (e.g., trying to come up with a bug-free way to compute negative dates) you've proved my mpoint. :) I haven't got a clue what negative dates are, unless you mean BC. But the above works (unless I got ascending and descending mixed up as usual). //Lennart ___ 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
I'm sorry, it's early in the morning. It is of course: sorted(sorted(news_stories, key=lambda x: x.publication_date, reverse=True), key=lambda x: x.category) I forgot the key= bit. ___ 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] procedures for moving package to github and porting to Python 3
Hi, Disclaimer: it's been a while since I actively followed zope-dev and grok-dev. So, please forgive me my ignorance. Spurred by the recent ZTK-2.0 discussion, I'm trying to get back on track on the topics of 1) migrating package to github and 2) porting packages to Python 3. As a first step, I'd like to get the packages directly related to Grok moved over to github. Could someone perhaps tell me if there's a guideline document, some kind of recipe, or perhaps a conclusive posting on the mailinglist on how to proceed on this topic? Thanks in advance for any pointers!! kind 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] procedures for moving package to github and porting to Python 3
On Fri, Mar 01, 2013 at 09:51:05AM +0100, Jan-Wijbrand Kolman wrote: Disclaimer: it's been a while since I actively followed zope-dev and grok-dev. So, please forgive me my ignorance. A single up-to-date web page sure beats reading months of list archives. Spurred by the recent ZTK-2.0 discussion, I'm trying to get back on track on the topics of 1) migrating package to github and 2) porting packages to Python 3. As a first step, I'd like to get the packages directly related to Grok moved over to github. Could someone perhaps tell me if there's a guideline document, some kind of recipe, or perhaps a conclusive posting on the mailinglist on how to proceed on this topic? My attempt at this: https://gist.github.com/mgedmin/4944724 AFAIK Stephan migrated most of the zope.* packages using this process. 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] procedures for moving package to github and porting to Python 3
On 3/1/13 10:17 AM, Marius Gedminas wrote: On Fri, Mar 01, 2013 at 09:51:05AM +0100, Jan-Wijbrand Kolman wrote: Disclaimer: it's been a while since I actively followed zope-dev and grok-dev. So, please forgive me my ignorance. A single up-to-date web page sure beats reading months of list archives. :-) Spurred by the recent ZTK-2.0 discussion, I'm trying to get back on track on the topics of 1) migrating package to github and 2) porting packages to Python 3. As a first step, I'd like to get the packages directly related to Grok moved over to github. Could someone perhaps tell me if there's a guideline document, some kind of recipe, or perhaps a conclusive posting on the mailinglist on how to proceed on this topic? My attempt at this: https://gist.github.com/mgedmin/4944724 AFAIK Stephan migrated most of the zope.* packages using this process. Ok, thanks. I've read it, but will need to re-read it a couple of times more I guess :) It seem to me the best next step would be to just pick a random grokcore.* package and to just try it. I'll pick, well, grokcore.component. If I understand correctly, there's two things I need to ask someone to do: * create a repository at https://github/zopefoundation/grokcore.component * ask permission to use the authors.txt mapping svn usernames to real names and email addresses. Again, thanks for the information. 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] procedures for moving package to github and porting to Python 3
On Friday, March 01, 2013 11:17:44 AM Marius Gedminas wrote: Could someone perhaps tell me if there's a guideline document, some kind of recipe, or perhaps a conclusive posting on the mailinglist on how to proceed on this topic? My attempt at this: https://gist.github.com/mgedmin/4944724 AFAIK Stephan migrated most of the zope.* packages using this process. Yes, I have, except that I use a one does it all script published here: https://github.com/zopefoundation/zope.githubsupport All you need to do is to create a zope.cfg that works for you. I can quickly create repositories for you if you send me a list of (pkg_name, pkg_title) tuples. Jim will announce a secret location for the authors.txt file in the next days on the ZF mailing list. 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] procedures for moving package to github and porting to Python 3
On Fri, Mar 01, 2013 at 11:24:31AM +0100, Jan-Wijbrand Kolman wrote: On 3/1/13 10:17 AM, Marius Gedminas wrote: My attempt at this: https://gist.github.com/mgedmin/4944724 AFAIK Stephan migrated most of the zope.* packages using this process. Stephan tells me there are scripts at https://github.com/zopefoundation/zope.githubsupport that can do the entire process (create repo, convert history, upload it), if you've the right permissions on Github (few people do). So perhaps the easiest thing is to ask for the package to be converted. 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] procedures for moving package to github and porting to Python 3
On 3/1/13 2:23 PM, Marius Gedminas wrote: On Fri, Mar 01, 2013 at 11:24:31AM +0100, Jan-Wijbrand Kolman wrote: On 3/1/13 10:17 AM, Marius Gedminas wrote: My attempt at this: https://gist.github.com/mgedmin/4944724 AFAIK Stephan migrated most of the zope.* packages using this process. Stephan tells me there are scripts at https://github.com/zopefoundation/zope.githubsupport that can do the entire process (create repo, convert history, upload it), if you've the right permissions on Github (few people do). So perhaps the easiest thing is to ask for the package to be converted. I just read Stephan's reply pointing to that script. I have no idea whether I have the right permissions. I do see someone just created an empty grokcore.component repository on github (thanks whoever did that! :-) ) I could surely ask others to do the work for me, though I had the impression everyone could take care of the packages he/she cares about :-) The list that I intended to start off with is roughly: grok grokcore.annotation grokcore.catalog grokcore.chameleon grokcore.component grokcore.content grokcore.formlib grokcore.json grokcore.layout grokcore.message grokcore.rest grokcore.security grokcore.site grokcore.startup grokcore.traverser grokcore.view grokcore.viewlet grokcore.xmlrpc grokproject grokui.admin grokui.base martian megrok.menu zope.errorview zope.fanstatic z3c.autoinclude z3c.evalexception z3c.flashmessage zc.catalog Since the grokcore.component repo is there now, I'll follow my initial plan and try to get that migrated from svn to github as a first step. kind 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] procedures for moving package to github and porting to Python 3
On 3/1/13 1:39 PM, Stephan Richter wrote: AFAIK Stephan migrated most of the zope.* packages using this process. Yes, I have, except that I use a one does it all script published here: https://github.com/zopefoundation/zope.githubsupport Aha, great! All you need to do is to create a zope.cfg that works for you. I can quickly create repositories for you if you send me a list of (pkg_name, pkg_title) tuples. I just compiled a list in another reply in this thread. Jim will announce a secret location for the authors.txt file in the next days on the ZF mailing list. You mean the ZF mailinglist that only ZF members can join? Thanks for the pointers so far! 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] procedures for moving package to github and porting to Python 3
On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote: I do see someone just created an empty grokcore.component repository on github (thanks whoever did that! :-) ) It is actually fully converted. :-) I am going to adjust my script to allow mutliple conversions at once. I will take care of your list. 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] procedures for moving package to github and porting to Python 3
On Friday, March 01, 2013 02:40:38 PM Jan-Wijbrand Kolman wrote: Jim will announce a secret location for the authors.txt file in the next days on the ZF mailing list. You mean the ZF mailinglist that only ZF members can join? Yeah, but if you are a committer, you are a member. :-) 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] procedures for moving package to github and porting to Python 3
On 3/1/13 2:49 PM, Stephan Richter wrote: On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote: I do see someone just created an empty grokcore.component repository on github (thanks whoever did that! :-) ) It is actually fully converted. :-) LOL - cool! I am going to adjust my script to allow mutliple conversions at once. I will take care of your list. Really?! Thanks!! 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] procedures for moving package to github and porting to Python 3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/01/2013 08:50 AM, Stephan Richter wrote: On Friday, March 01, 2013 02:40:38 PM Jan-Wijbrand Kolman wrote: Jim will announce a secret location for the authors.txt file in the next days on the ZF mailing list. You mean the ZF mailinglist that only ZF members can join? Yeah, but if you are a committer, you are a member. :-) Not so. Foundation members are listed here: http://foundation.zope.org/members/nominated_members The original group of what are now called nominated members was invited from the then-existing set of committers, but there is no necessary tie between the two. 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/ iEYEARECAAYFAlEwtfMACgkQ+gerLs4ltQ66bwCfTubHRqqMv3PkZemQgXwoIx4s n10An3Jd/08Vp8k28xPqOZta6Bbj/GRM =vuDU -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] Moving to Github: authors.txt (and svn12git.py)
I've created a private subversion repository containing the authors.txt file needed when converting subversion repository to git. svn+ssh://svn.zope.org/repos/2git It's a small repository that you can check out directly: svn co svn+ssh://svn.zope.org/repos/2git I've also included a small python script, svn2git.py. It: - builds on the git svn plugin, which you must have installed. - doesn't require that you have a local copy of the subversion repository. - is more reliable than the ruby version - It usually does it's work in a few minutes. - It has run into difficulty with one project, ZEO, where it got into some look and didn't finish. This is the script I use and I recommend it for individual repositories. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ 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] procedures for moving package to github and porting to Python 3
Everything but megrok.menu is now converted. GitHub did not like the fact that I tried to create 26 repos at once, so I had some startup issues. Regards, Stephan On Friday, March 01, 2013 02:37:34 PM Jan-Wijbrand Kolman wrote: grok grokcore.annotation grokcore.catalog grokcore.chameleon grokcore.component grokcore.content grokcore.formlib grokcore.json grokcore.layout grokcore.message grokcore.rest grokcore.security grokcore.site grokcore.startup grokcore.traverser grokcore.view grokcore.viewlet grokcore.xmlrpc grokproject grokui.admin grokui.base martian megrok.menu zope.errorview zope.fanstatic z3c.autoinclude z3c.evalexception z3c.flashmessage zc.catalog -- 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] procedures for moving package to github and porting to Python 3
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. 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] ZTK 2.0: Deprecate zope.sequencesort
On Mar 1, 2013, at 19:06, Suresh V. suresh...@yahoo.com wrote: On Friday 01 March 2013 02:15 PM, Lennart Regebro wrote: I'm sorry, it's early in the morning. It is of course: sorted(sorted(news_stories, key=lambda x: x.publication_date, reverse=True), key=lambda x: x.category) Won't the two sorteds step over each other? No: since Python 2.2 sorting is guaranteed to be stable. See http://wiki.python.org/moin/HowTo/Sorting/#Sort_Stability_and_Complex_Sorts for more information. Wichert. ___ 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
Hi Tres, Am 28.02.2013, 21:04 Uhr, schrieb Tres Seaver tsea...@palladion.com: The main export of the package is the 'sort' function, which takes a sequence, per-column sort specs (key/attr name, sort function, direction), and optional extra data (e.g., the DTML namespace) and a flag indicating whether to use key or attribute lookup. The 'SortBy' class is really just an implementation detail of that API. I guess the right way to port the package is to implement a sort API. I have ported it to Python 3.2 and 3.3 and released a 4.0.0 version. Thanks for the port. I guess the question is still whether it should still be in ZTK - providing DTML as an example suggests that this really is a Zope only library. Do you see use for it outside the Zope context? Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ 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
On Fri, Mar 1, 2013 at 7:06 PM, Suresh V. suresh...@yahoo.com wrote: On Friday 01 March 2013 02:15 PM, Lennart Regebro wrote: I'm sorry, it's early in the morning. It is of course: sorted(sorted(news_stories, key=lambda x: x.publication_date, reverse=True), key=lambda x: x.category) Won't the two sorteds step over each other? Nope. Timsort is a stable sort, so you get a list that is sorted first by category and then by publication_date. //Lennart ___ 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
On Thursday, February 28, 2013, Stephan Richter wrote: 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. You can always fall back to functools.cmp_to_key() to use cmp-based sorting in python 3: http://docs.python.org/3/library/functools.html#functools.cmp_to_key -- Martijn Pieters -- Martijn Pieters ___ 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] SVN to Git Conversion
Hi everyone, I am now feeling comfortable with my script to run conversions of many packages at once. Thus, if you want packages moved from SVN to GitHub just let me know and I will convert them for you. 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 )
[Zope-dev] Porting Zope to Python 3 Update
Hi everyone, as the week ends, I thought I might give a brief update on the Python 3 porting effort. According to the Unofficial Zope on Python 3 status page[1], about 110 packages are ported to Python 3.3. Hanno and I worked this week on updating the ZTK configuration files and I am happy to announce that the ZTK passes all tests on Python 3.3! So once the ZODB is ported, we can start on finalizing all releases, which would pave the way for a ZTK 2.0 release. Marius has made great efforts on finishing the port of ZODB. All the tests pass now on the py3 branch for Python 2.6, 2.7 and 3.3. He has also removed all resource warnings (he started at 400+). The final task will be to integrate zodbpickle. zodbpickle needs some changes to properly enable the noload() method. Luckily this work will entail rewriting the dump/load of persistent ids to be more efficient and compatible with cPickle 2.7 pickles. (We are working hard on making Python 2 pickles load on Python 3!) On Wednesday, I was able to run a first Zope 3 (or should I say Bluebream?) app on Python 3.3. Thanks to Andrey and Albertas for porting some of the complex application packages. The sample application can be found in ``zope.paste``[2]. Note the short ZCML[3] and Paster[4] files. Thanks goes to everyone who helped breaking unnecessary and circular dependencies to make this work so well! In the process of all of the above, we have also started moving all packages that we are ported to Python 3 over to GitHub. I have also ported the core packages for Zope 2/4 and Grok already. So what's next? I am in the process of trying to port a rather large demo application[5] to Python 3. We are about 20 packages (that we control) away from that goal. Andrey is currently working on porting zope.testbrowser to Python 3 by changing its internal implementation from mechanize to WebTest (since it is too hard to deal with mechanize). Also, we will have a serious look at ZEO. I hope I got some of you interested in thinking about porting applications to Python 3. [1] http://zope3.pov.lt/py3/ [2] https://github.com/zopefoundation/zope.paste [3] https://github.com/zopefoundation/zope.paste/blob/master/src/zope/paste/test_app/app.zcml [4] https://github.com/zopefoundation/zope.paste/blob/master/src/zope/paste/test_app/app.ini [5] https://github.com/CipherHealth/cipher.uibuilderdemo 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 )
[Zope-dev] zope-tests - FAILED: 18, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-02-28 00:00:00 UTC and 2013-03-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]Still Failing - zopetoolkit_trunk - Build # 188 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.layer.pagelet_py_265_32 [7]winbot / z3c.layer.pagelet_py_265_32 [8]winbot / z3c.pagelet_py_265_32 [9]winbot / z3c.recipe.paster_py_265_32 [10] winbot / zc.catalog_py_265_32 [11] winbot / zc.queue_py_265_32 [12] winbot / zc.resourcelibrary_py_265_32 [13] winbot / zope.app.authentication_py_265_32 [14] winbot / zope.app.http_py_265_32 [15] winbot / zope.app.pagetemplate_py_265_32 [16] winbot / zope.app.publication_py_265_32 [17] winbot / zope.browserpage_py_265_32 [18] 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 # 188 https://mail.zope.org/pipermail/zope-tests/2013-March/072952.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072949.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072945.html [4]FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072948.html [5]FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072951.html [6]FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072968.html [7]FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072950.html [8]FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072944.html [9]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072965.html [10] FAILED winbot / zc.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072966.html [11] FAILED winbot / zc.queue_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072973.html [12] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072972.html [13] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072970.html [14] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072971.html [15] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072946.html [16] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072969.html [17] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072967.html [18] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072947.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] SVN to Git Conversion
Hi Stephan Thanks a lot! Is there any information about what this means for zope contributers? What are the restrictions or any other relevant parts where we have to know additional to the git basics? I probably missed some mailinglist threads. Just let me know if everything was answered before and I'll grab the mailinglist threads. Regards Roger Ineichen _ END OF MESSAGE -Ursprüngliche Nachricht- Von: zope-dev-boun...@zope.org [mailto:zope-dev-boun...@zope.org] Im Auftrag von Stephan Richter Gesendet: Samstag, 2. März 2013 01:05 An: zope-dev@zope.org Betreff: [Zope-dev] SVN to Git Conversion Hi everyone, I am now feeling comfortable with my script to run conversions of many packages at once. Thus, if you want packages moved from SVN to GitHub just let me know and I will convert them for you. 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 ) ___ 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 )
