Re: [Zope-dev] [zope2] Help needed with security checks and add views
On Thu, Jul 8, 2010 at 3:02 PM, Martin Aspeli optilude+li...@gmail.com wrote: Ideally I'd love to add support for the permission attribute, as clearly people have been using it. But if there's nobody who can figure out how to do that, I'd at least like to clarify the add view case. Why can't we just copy the relevant code from the browser:page directive? The ViewSecurityGrokker in http://svn.zope.org/five.grok/trunk/src/five/grok/meta.py?rev=112163view=auto may be useful reading too. It should be doing the same thing, no? It seems you have some idea about this code, so are you volunteering to implement this? Since we are dealing with a disclosed real security vulnerability here, I need to have some resolution by next Tuesday. Either that is disabling the functionality or protecting it with some security. 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] [zope2] Help needed with security checks and add views
On 9 July 2010 16:12, Hanno Schlichting ha...@hannosch.eu wrote: On Thu, Jul 8, 2010 at 3:02 PM, Martin Aspeli optilude+li...@gmail.com wrote: Ideally I'd love to add support for the permission attribute, as clearly people have been using it. But if there's nobody who can figure out how to do that, I'd at least like to clarify the add view case. Why can't we just copy the relevant code from the browser:page directive? The ViewSecurityGrokker in http://svn.zope.org/five.grok/trunk/src/five/grok/meta.py?rev=112163view=auto may be useful reading too. It should be doing the same thing, no? It seems you have some idea about this code, so are you volunteering to implement this? Possibly. I have client work that has to take priority right now. Since we are dealing with a disclosed real security vulnerability here, I need to have some resolution by next Tuesday. Either that is disabling the functionality or protecting it with some security. I'd appreciate it if someone who's getting more than four hours of sleep a night at the moment takes a stab. I'm happy to review/assist. Martin ___ 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.traversing's ILocation behavior
Hi all Betreff: Re: [Zope-dev] zope.traversing's ILocation behavior On Jul 8, 2010, at 11:04 AM, Martijn Faassen wrote: I propose the following adjustment: try: container = context.__parent__ except AttributeError: container = ILocation(context).__parent__ I'm fine with that too. But this will skip the __conform__ lookup, right? See: zope/interface/interfaces.py line: 167 class InterfaceBasePy(object): Base class that wants to be replaced with a C base :) def __call__(self, obj, alternate=_marker): Adapt an object to the interface conform = getattr(obj, '__conform__', None) if conform is not None: adapter = self._call_conform(conform) if adapter is not None: return adapter adapter = self.__adapt__(obj) if adapter is not None: return adapter elif alternate is not _marker: return alternate else: raise TypeError(Could not adapt, obj, self) But anyway, also the initial implementation which we used a long time whould skip such __conform__ call. In my point of view is the usage of the absoluteURL method an explicit pypass of the ILocation adaption and an improved speedup lookup based on the directly __parent__ attribute access. Probably we should add a comment about that in the absoluteURL method. Regards Roger Ineichen ___ 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: 39 OK, 12 Failed, 3 Unknown
Summary of messages to the zope-tests list. Period Thu Jul 8 12:00:00 2010 UTC to Fri Jul 9 12:00:00 2010 UTC. There were 54 messages: 6 from Zope Tests, 3 from buildbot at enfoldsystems.com, 4 from buildbot at pov.lt, 17 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 1 from ct at gocept.com, 12 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Thu Jul 8 18:58:05 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016265.html Subject: FAILED: Repository policy check found errors in 416 projects From: ct at gocept.com Date: Thu Jul 8 21:18:18 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016267.html Subject: FAILED : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Thu Jul 8 22:58:12 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016281.html Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Thu Jul 8 23:09:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016282.html Subject: FAILED : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Thu Jul 8 23:18:06 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016283.html Subject: FAILED : winbot / ztk_10 py_270_win32 From: buildbot at winbot.zope.org Date: Thu Jul 8 23:46:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016287.html Subject: FAILED : winbot / ztk_10 py_270_win64 From: buildbot at winbot.zope.org Date: Thu Jul 8 23:53:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016288.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Fri Jul 9 03:34:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016307.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Fri Jul 9 04:29:47 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016308.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Fri Jul 9 07:19:12 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016312.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Fri Jul 9 07:53:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016316.html Subject: FAILED : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Fri Jul 9 07:58:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016317.html Unknown --- Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.6-maestro From: buildbot at enfoldsystems.com Date: Fri Jul 9 02:02:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016303.html Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.5-maestro From: buildbot at enfoldsystems.com Date: Fri Jul 9 02:03:59 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016305.html Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.4-maestro From: buildbot at enfoldsystems.com Date: Fri Jul 9 02:05:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016304.html Tests passed OK --- Subject: OK : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Thu Jul 8 18:58:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016264.html Subject: OK : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Thu Jul 8 18:59:20 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016266.html Subject: OK : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Thu Jul 8 21:09:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016296.html Subject: OK : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Thu Jul 8 21:30:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016297.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Thu Jul 8 21:32:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016268.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Jul 8 21:34:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016269.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Thu Jul 8 21:36:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016270.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Thu Jul 8 21:38:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016271.html Subject: OK : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Thu Jul 8 21:40:08 EDT 2010 URL:
Re: [Zope-dev] zope.traversing's ILocation behavior
Hey, [zope.traversing absolute URL behavior] I've applied the fix to zope.traversing and added a test as well. It's released as zope.traversing. I've also updated the ZTK to use this version. (initially I used checkversions to update a few other packages too, namely zope.dublincore, zope.index, zope.pagetemplate and zope.testing, but this *did* result in zopeapp breakages, so I reverted that quickly. Someone needs to look into this to see what can be upgraded and what causes the break later) Regards, Martijn ___ 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.traversing's ILocation behavior
On Fri, Jul 9, 2010 at 2:03 PM, Martijn Faassen faas...@startifact.com wrote: [zope.traversing absolute URL behavior] I've applied the fix to zope.traversing and added a test as well. It's released as zope.traversing. I've also updated the ZTK to use this version. Thanks! (initially I used checkversions to update a few other packages too, namely zope.dublincore, zope.index, zope.pagetemplate and zope.testing, but this *did* result in zopeapp breakages, so I reverted that quickly. Someone needs to look into this to see what can be upgraded and what causes the break later) I think zope.dublincore causes the breakage in some zope.app packages. zope.index and zope.pagetemplate should be upgraded. zope.testing 3.9.5 will throw deprecation warnings for not using zope.testrunner. The release team decided to keep the current zope.testing / zc.testrunner recipe for the ZTK 1.0 release, so we stick to zope.testing 3.9.4 for the time being. 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] zope.traversing's ILocation behavior
On Fri, Jul 9, 2010 at 9:08 AM, Hanno Schlichting ha...@hannosch.eu wrote: I think zope.dublincore causes the breakage in some zope.app packages. This one's a sticking point for a large application here as well (one where we're trying to move to the ZTK as the base). I think I'm sticking to zope.dublincore 3.6.0 on that for now. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com A storm broke loose in my mind. --Albert Einstein ___ 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] audit of RestrictedPython for Python 2.7
Hi David, awesome work! Sidnei or Stephan, can one of you comment on David's approach or offer a review? Cheers, Hanno On Fri, Jul 9, 2010 at 5:42 AM, David Glick davidgl...@groundwire.org wrote: I am done (as far as I can tell) evaluating RestrictedPython to see if changes are needed to support Python 2.7. This is the first time I have done this, so would appreciate if someone else can look over my work to make sure I'm not missing something important. I'll describe my process and findings below. The basic summary is that Python 2.7 adds a small number of syntactic features and they are already handled adequately by RestrictedPython. I added some tests for these on a branch, http://svn.zope.org/repos/main/RestrictedPython/branches/davisagli-python27, which I can merge once someone else has looked over them. In addition, I discovered the omission of a name check for the from x import y style import; this is also fixed on the branch. To go into detail... I started by reading RestrictedPython (henceforth referred to as RP) to familiarize myself with how it works. Next I read the What's New in Python 2.7 document and noted features that might require changes in RP. Then I went through each of these and looked at the corresponding changes in the Python compiler, bytecode generator and evaluator to further check on whether changes were needed. Here are the items I checked and my conclusions... - dict and set comprehensions: These need to use RP's safe _getitem_ to iterate. This was already taken care of because these new comprehensions use the same ListCompFor AST node that list comprehensions do. - set literals: These build a new set based on the result of evaluating other AST nodes that RP already protects, so should be safe. - multiple context managers in one with statement: I wrote a test to confirm that the existing name check for context managers still works when there are multiple ones. - the 'with' statement now uses a new opcode SETUP_WITH that does an unprotected lookup of the '__enter__' and '__exit__' methods of the context manager. I don't think this is a problem, since methods starting with an underscore can't be defined in RP. - dictionary views: these don't introduce new builtins or syntax, so I don't think changes are necessary. To allow access to them in RP in Zope 2 we would need to adjust the dict method whitelist in AccessControl.ZopeGuards to allow viewitems, viewkeys, and viewvalues. - new builtins memoryview, bytes, and bytearray: For now I punted and these are not included in RP's safe_builtins list. memoryview and bytearray should probably not be added. bytes is just a synonym for str in Python 2.7 afaict, so would probably be okay to add. - explicit relative imports (from .x import y): These are covered by the name check I added (as noted above in the summary) for from x import y imports in general. - except x as y: Added a test to show that this is already covered. Finally, to double-check my work I did diffs of Lib/compiler/ast.py and Python/ceval.c in the Python source to check for any new AST nodes or opcodes that I had overlooked above. This didn't yield any new concerns that I hadn't already considered. peace, David ___ 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] audit of RestrictedPython for Python 2.7
On Thursday, July 08, 2010, David Glick wrote: I am done (as far as I can tell) evaluating RestrictedPython to see if changes are needed to support Python 2.7. This is the first time I have done this, so would appreciate if someone else can look over my work to make sure I'm not missing something important. I'll describe my process and findings below. This is a good analysis. I looked over your checkins as they came in and they look good. I am glad you caught the import problem. 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] Including Paste into the ZTK version list?
Hi. I noticed that all three frameworks (BB, Grok, Zope2) have version pins for Paste, PasteDeploy and PasteScript. Does anyone object to including them into the ztk-versions.cfg under dependencies? It's currently: Paste = 1.7.4 PasteDeploy = 1.3.3 PasteScript = 1.7.3 Note that Paste 1.7.4 addresses a security issue [1], so you should update it regardless. Hanno [1] http://pylonshq.com/articles/archives/2010/6/paste_174_released_addresses_xss_security_hole ___ 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] Including Paste into the ZTK version list?
Le 09/07/2010 16:50, Hanno Schlichting a écrit : Hi. I noticed that all three frameworks (BB, Grok, Zope2) have version pins for Paste, PasteDeploy and PasteScript. Does anyone object to including them into the ztk-versions.cfg under dependencies? It's currently: Paste = 1.7.4 PasteDeploy = 1.3.3 PasteScript = 1.7.3 OK for bluebream, I'm currently modifying it so that it depends on the ZTK, and I'll be happy with anything reducing the buildout. with the few remaining packages, I get errors on z3c.testsetup tests. Is there anyone else having this problem? Christophe Note that Paste 1.7.4 addresses a security issue [1], so you should update it regardless. Hanno [1] http://pylonshq.com/articles/archives/2010/6/paste_174_released_addresses_xss_security_hole ___ 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 )
Re: [Zope-dev] Including Paste into the ZTK version list?
On Friday, July 09, 2010, Hanno Schlichting wrote: I noticed that all three frameworks (BB, Grok, Zope2) have version pins for Paste, PasteDeploy and PasteScript. Does anyone object to including them into the ztk-versions.cfg under dependencies? +1 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] audit of RestrictedPython for Python 2.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Glick wrote: I am done (as far as I can tell) evaluating RestrictedPython to see if changes are needed to support Python 2.7. This is the first time I have done this, so would appreciate if someone else can look over my work to make sure I'm not missing something important. I'll describe my process and findings below. The basic summary is that Python 2.7 adds a small number of syntactic features and they are already handled adequately by RestrictedPython. I added some tests for these on a branch, http://svn.zope.org/repos/main/RestrictedPython/branches/davisagli-python27, which I can merge once someone else has looked over them. In addition, I discovered the omission of a name check for the from x import y style import; this is also fixed on the branch. To go into detail... I started by reading RestrictedPython (henceforth referred to as RP) to familiarize myself with how it works. Next I read the What's New in Python 2.7 document and noted features that might require changes in RP. Then I went through each of these and looked at the corresponding changes in the Python compiler, bytecode generator and evaluator to further check on whether changes were needed. Here are the items I checked and my conclusions... - dict and set comprehensions: These need to use RP's safe _getitem_ to iterate. This was already taken care of because these new comprehensions use the same ListCompFor AST node that list comprehensions do. - set literals: These build a new set based on the result of evaluating other AST nodes that RP already protects, so should be safe. - multiple context managers in one with statement: I wrote a test to confirm that the existing name check for context managers still works when there are multiple ones. - the 'with' statement now uses a new opcode SETUP_WITH that does an unprotected lookup of the '__enter__' and '__exit__' methods of the context manager. I don't think this is a problem, since methods starting with an underscore can't be defined in RP. - dictionary views: these don't introduce new builtins or syntax, so I don't think changes are necessary. To allow access to them in RP in Zope 2 we would need to adjust the dict method whitelist in AccessControl.ZopeGuards to allow viewitems, viewkeys, and viewvalues. - new builtins memoryview, bytes, and bytearray: For now I punted and these are not included in RP's safe_builtins list. memoryview and bytearray should probably not be added. bytes is just a synonym for str in Python 2.7 afaict, so would probably be okay to add. - explicit relative imports (from .x import y): These are covered by the name check I added (as noted above in the summary) for from x import y imports in general. - except x as y: Added a test to show that this is already covered. Finally, to double-check my work I did diffs of Lib/compiler/ast.py and Python/ceval.c in the Python source to check for any new AST nodes or opcodes that I had overlooked above. This didn't yield any new concerns that I hadn't already considered. First class work! Thanks very much for your careful attention to detail. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkw3T3MACgkQ+gerLs4ltQ5rwwCg2Wrwuykqo5xjWuewyfFv9tbK T3EAoMf8X6PhJxYXn7kARjhpofok+FVZ =z2oW -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] [ZTK] toolchain versions
Hi, http://svn.zope.org/zopetoolkit/trunk/ztk-versions.cfg?rev=114375view=auto is there any reason why the versions pinning of the toolchain are in the ztk-versions.cfg ? Packages such as z3c.recipe.depgraph, mr.developer, z3c.checkversions have nothing to do with the final frameworks nor the ZTK. Shouldn't they be isolated to a [versions] section in the buildout? Christophe ___ 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] toolchain versions
Hi. On Fri, Jul 9, 2010 at 6:37 PM, Christophe Combelles cc...@free.fr wrote: http://svn.zope.org/zopetoolkit/trunk/ztk-versions.cfg?rev=114375view=auto is there any reason why the versions pinning of the toolchain are in the ztk-versions.cfg ? Packages such as z3c.recipe.depgraph, mr.developer, z3c.checkversions have nothing to do with the final frameworks nor the ZTK. Shouldn't they be isolated to a [versions] section in the buildout? We talked about this in one of our meetings :) Having the toolchain inside the ztk-versions.cfg makes it easier to extend the ZTK. Zope 2 just has to use a single extends= line and Grok just two (for the additional zopeapp-versions.cfg). Since we all use the toolchain anyways, we didn't see a point in separating them out. 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] toolchain versions
Le 09/07/2010 18:44, Hanno Schlichting a écrit : Hi. On Fri, Jul 9, 2010 at 6:37 PM, Christophe Combellescc...@free.fr wrote: http://svn.zope.org/zopetoolkit/trunk/ztk-versions.cfg?rev=114375view=auto is there any reason why the versions pinning of the toolchain are in the ztk-versions.cfg ? Packages such as z3c.recipe.depgraph, mr.developer, z3c.checkversions have nothing to do with the final frameworks nor the ZTK. Shouldn't they be isolated to a [versions] section in the buildout? We talked about this in one of our meetings :) Having the toolchain inside the ztk-versions.cfg makes it easier to extend the ZTK. Zope 2 just has to use a single extends= line and Grok just two (for the additional zopeapp-versions.cfg). Since we all use the toolchain anyways, we didn't see a point in separating them out. ok, maybe it was the meeting when I was not there. I'm ok with it, because it (again) reduces the custom version list of everyone. But it looks like we have a list of 33 packages which are not really part of the ZTK, which is finally very close to having an extra.cfg :) 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 )
[Zope-dev] Python 2.7 on the apfy buildbots
The afpy buildbots now all run a slave with Python 2.7 final http://buildbot.afpy.org/ Christophe ___ 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] Python 2.7 on the apfy buildbots
On Fri, Jul 9, 2010 at 9:04 PM, Christophe Combelles cc...@free.fr wrote: The afpy buildbots now all run a slave with Python 2.7 final http://buildbot.afpy.org/ Yeah! Jan-Jaap and Sebastien, could you update your buildouts as well? Python 2.7 should run for the ZTK trunk, zc.buildout and Zope 2 trunk. I'm not sure about Grok. Thanks, 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] Python 2.7 on the apfy buildbots
Le 09/07/2010 21:04, Christophe Combelles a écrit : The afpy buildbots now all run a slave with Python 2.7 final http://buildbot.afpy.org/ However, the 2.7 slaves don't send any alert to the zope-tests list. Should I enable this? Christophe ___ 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 )
Re: [Zope-dev] Python 2.7 on the apfy buildbots
On Fri, Jul 9, 2010 at 9:17 PM, Christophe Combelles cc...@free.fr wrote: However, the 2.7 slaves don't send any alert to the zope-tests list. Should I enable this? The winbot already sends reports for Python 2.7, so I'd say go ahead and spam us :) More blame might get someone to fix those two last zope.app packages. 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] Including Paste into the ZTK version list?
On 07/09/2010 04:50 PM, Hanno Schlichting wrote: I noticed that all three frameworks (BB, Grok, Zope2) have version pins for Paste, PasteDeploy and PasteScript. Does anyone object to including them into the ztk-versions.cfg under dependencies? No objections from Grok. Regards, Martijn ___ 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] [zope2] Looking for a maintainer for ZSQLMethods / Shared.DC.ZRDB
Hi. Are you using Products.ZSQLMethods or DC.Shared.ZRDB? Are you interested in maintaining it? Starting with Zope 2.13 these packages are no longer part of the Zope 2 distribution. The code has moved to its own project, as the core Zope 2 developers haven't had a strong interest in it anymore. Please speak up if you want to take over maintenance of the code and I'll gladly hand over the keys. The projects is registered on PyPi at http://pypi.python.org/pypi/Products.ZSQLMethods, has a Launchpad bug tracker at https://launchpad.net/products.zsqlmethods (including some bugs moved over from the Zope2 project) and the code lives at svn+ssh://svn.zope.org/repos/main/Products.ZSQLMethods/trunk. Cheers, 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 )
