Re: [Zope3-dev] 'thread_local' AttributeError in zope.security.checker
Previously Paul Carduner wrote: Hello zope3-dev, I came across an error I have not seen before. Just for reference, here is the last snippet from the traceback: File /home/pcardune/Work/ZContact/zcontact-lp/eggs/tmpgwuq6O/zope.security-3.4.0b4-py2.4-linux-i686.egg/zope/security/checker.py, line 420, in ? AttributeError: 'module' object has no attribute 'thread_local' I see the same thing: create a new project with grokproject, run bin/zopectl fg and it aborts with that error. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Proposal: Move ISite to zope.location was: [Zope3-dev] ISite misplaced in zope.app.component.interfaces
Hi, after thinking the problem over at gocept we came to the following suggestion: - A site is a place which gives acces to a component registry. - ISite isn't a good name for the concept behind it, because it is connected too tight to a website and on having hierarchical structures (at least in the code). - In long term a more abstract concept for ISite could be added. - In short term, for cleaning up dependencies, I propose to move ISite to zope.location, because it is the only package outside of of zope.app.* which uses ISite and defindes a method to get the nearest site. We think this is the right place because ISite is about component registries in the context of location. - zope.app.component.interfaces then can import ISite from the new place to avoid deprectation. -- Yours sincerely, Michael Howitz gocept gmbh co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon: +49 345 12298898 · fax: +49 345 12298891 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zope.annotation dependency to zope.app.container.contained
On 2007-08-09 20:51:26 +0200, Philipp von Weitershausen [EMAIL PROTECTED] said: Roman Joost wrote: we're doing some dependency checking at gocept and I discovered that zope.annotation depends on zope.app.container in its factory. What shall we do with this dependency to zope.app.container? Moving this factory to zope.app is probably not the best solution. To be clear, zope.annotation doesn't depend on zope.app, it depends on zope.app.container which is its own package and egg (and in fact, zope.annotation's dependencies are refreshingly few). The real problem is that zope.app.container depends on a whole bunch of other things. The question is why. Okay, actually I think that zope.annotation uses IContained. This is just wrong but also results in an underspecification of IContained: class IContained(ILocation): Objects contained in containers. When you read it very carefully you figure that it actually says is that object.__parent__[object.__name__] would result in the object again. IContained states how you can get the object from the __parent__. ILocation doesn't do that. For the annotation factory using zope.location and ILocatable would be sufficient. So we could get rid of the zope.app.container dependency. We should be a bit more specific about the IContained interface. Does it make any sense to have an IContained object without __name__. I think not. Chaning that would make __name__ a required attribute on IContained. Comments? -- Christian Zagrodnick gocept gmbh co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Dependency cleanup: zope.traversing
Hi, zope.traversing has a dependency to zope.app.applicationcontroller. This is because zope.traversing implements the etc namespace and has a hard coded reference to applicationcontrol there. In the same place it also looks up site managers (in a hard coded way). As a strategy to remove this dependency we should move the etc namespace to some other place in zope.app. I did not find reasonable candidates to move this two. Bad candidates are zope.app.publisher or zope.app.publication, zope.app.applicationcontrol. A new package could be created for the etc namespace too, but I'd like to avoid that. Christian ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Removed zope.security 3.4b4
Hi, I saw the error reports about zope.security and got talked to from a few people that they had severe problems managing around this. I removed the 3.4b4 distribution from download.zope.org to allow them to continue using zopeproject and grokproject until we find a fix. I wasn't sure about that, so if someone has even worse problems now, please speak up and I'll put the package back into place again. I hope I didn't cause any more problems than exist already. Christian ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Dependency cleanup: zope.traversing
On Wednesday 15 August 2007 08:01, Christian Theune wrote: zope.traversing has a dependency to zope.app.applicationcontroller. This is because zope.traversing implements the etc namespace and has a hard coded reference to applicationcontrol there. In the same place it also looks up site managers (in a hard coded way). As a strategy to remove this dependency we should move the etc namespace to some other place in zope.app. I did not find reasonable candidates to move this two. Bad candidates are zope.app.publisher or zope.app.publication, zope.app.applicationcontrol. A new package could be created for the etc namespace too, but I'd like to avoid that. I think that zope.app.component would be a good candidate, because etc is pretty much about accessing the local site. I know it was originally designed for allowing many different non-content things to be plugged in, but this has not materialized. An alternative would be to get rid of ++etc++ and implement ++site++ and ++control++. Now that I think about it, I actually favor this. ;-) Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
zope.security problems related to Python 2.5 update? (Was: [Zope3-dev] Removed zope.security 3.4b4)
Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune: Hi, I saw the error reports about zope.security and got talked to from a few people that they had severe problems managing around this. I removed the 3.4b4 distribution from download.zope.org to allow them to continue using zopeproject and grokproject until we find a fix. I wasn't sure about that, so if someone has even worse problems now, please speak up and I'll put the package back into place again. I hope I didn't cause any more problems than exist already. This is deeper than I thought. b3 doesn't work either. It looks like the merge from the branch with support for Python 2.5 is causing the problems. Christian ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: zope.security problems related to Python 2.5 update? (Was: [Zope3-dev] Removed zope.security 3.4b4)
Previously Christian Theune wrote: Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune: Hi, I saw the error reports about zope.security and got talked to from a few people that they had severe problems managing around this. I removed the 3.4b4 distribution from download.zope.org to allow them to continue using zopeproject and grokproject until we find a fix. I wasn't sure about that, so if someone has even worse problems now, please speak up and I'll put the package back into place again. I hope I didn't cause any more problems than exist already. This is deeper than I thought. b3 doesn't work either. It looks like the merge from the branch with support for Python 2.5 is causing the problems. I can confirm that the last release before the python 2.5 support was added (3.4.0-b2) works correctly. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Removed zope.security 3.4b4
Hey, Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune: Hi, I saw the error reports about zope.security and got talked to from a few people that they had severe problems managing around this. I removed the 3.4b4 distribution from download.zope.org to allow them to continue using zopeproject and grokproject until we find a fix. I wasn't sure about that, so if someone has even worse problems now, please speak up and I'll put the package back into place again. I hope I didn't cause any more problems than exist already. Ok. As this affected more packages and Wichert found out how to deal with this in the buildout.cfg of grokproject (zopeproject and other buildout-based projects should be able to derive a workaround for this until it's fixed.) See http://paste.plone.org/16261 for the full buildout.cfg. The most important lines are 11 to 15: [app] recipe = zc.zope3recipes=0.5.3:application eggs = test zope.security==3.4.0b2 Christian ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: Proposal: Move ISite to zope.location was: [Zope3-dev] ISite misplaced in zope.app.component.interfaces
On Wednesday 15 August 2007 07:41, Michael Howitz wrote: - ISite isn't a good name for the concept behind it, because it is connected too tight to a website and on having hierarchical structures (at least in the code). I think this is a matter of documentation and explanation. Anyone working longer than a week with Zope 3 knows what our extended concept for a site is. Terms always overlap accross problem domains, this is nothing new. We need to stop thinking that our branch of engineering/science is special and that we have to reinvent everything. - In short term, for cleaning up dependencies, I propose to move ISite to zope.location, because it is the only package outside of of zope.app.* which uses ISite and defindes a method to get the nearest site. We think this is the right place because ISite is about component registries in the context of location. After reading the first sentence, I was against it. After reading your explanation this sounds like a good idea, so +1 from me. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.annotation dependency to zope.app.container.contained
On Wednesday 15 August 2007 07:43, Christian Zagrodnick wrote: For the annotation factory using zope.location and ILocatable would be sufficient. So we could get rid of the zope.app.container dependency. +1 We should be a bit more specific about the IContained interface. Does it make any sense to have an IContained object without __name__. I think not. Chaning that would make __name__ a required attribute on IContained. +1 Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] 'thread_local' AttributeError in zope.security.checker
On Aug 14, 2007, at 7:32 PM, Paul Carduner wrote: Hello zope3-dev, I came across an error I have not seen before. Just for reference, here is the last snippet from the traceback: File /home/pcardune/Work/ZContact/zcontact-lp/eggs/tmpgwuq6O/ zope.security-3.4.0b4-py2.4-linux-i686.egg/zope/security/checker.py, line 420, in ? AttributeError: 'module' object has no attribute 'thread_local' I wish you had included the whole traceback. The interesting part to me is that it was so easy to fix. Here is a snippet of the relevant area of failing code from zope/security/checker.py # Get optimized versions try: import zope.security._zope_security_checker except ImportError: pass else: from zope.security._zope_security_checker import _checkers, selectChecker from zope.security._zope_security_checker import NoProxy, Checker from zope.security._zope_security_checker import _defaultChecker from zope.security._zope_security_checker import _available_by_default zope.interface.classImplements(Checker, INameBasedChecker) The very first import statement is throwing the error, but alas, it is not an ImportError. If I patch this code by catching the AttributeError in the same way the ImportError is caught, then everything works fine. Except you don't get the C optimizations. IOW, you would just be covering up a real error. I tried looking into the c code, but after years of python development, the c code just frightens me (a bit). That said, I would really appreciate any pointers people might be able to give me on what thread_local is for and why I (don't) need it. I rearranged the imports in zope.security yesterday. I apparently broke your usage, but I can't tell what your usage is. I'll need to see the whole traceback. In particular, I'll need to see the import order. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] 'thread_local' AttributeError in zope.security.checker
Previously Jim Fulton wrote: On Aug 14, 2007, at 7:32 PM, Paul Carduner wrote: Hello zope3-dev, I came across an error I have not seen before. Just for reference, here is the last snippet from the traceback: File /home/pcardune/Work/ZContact/zcontact-lp/eggs/tmpgwuq6O/ zope.security-3.4.0b4-py2.4-linux-i686.egg/zope/security/checker.py, line 420, in ? AttributeError: 'module' object has no attribute 'thread_local' I wish you had included the whole traceback. Here you are: [snow;/tmp/test]-119 bin/zopectl fg /tmp/test/parts/app/runzope -C /tmp/test/parts/zopectl/zope.conf Traceback (most recent call last): File /tmp/test/parts/app/runzope, line 97, in ? import zope.app.twisted.main File /home/wichert/buildout-eggs/tmp-GMMRj/zope.app.twisted-3.4.0b1_r76119-py2.4.egg/zope/app/twisted/main.py, line 32, in ? File /usr/lib/python2.4/site-packages/PIL/__init__.py, line 22, in ? File /home/wichert/buildout-eggs/tmpzGONPg/zope.app.appsetup-3.4.0a1-py2.4.egg/zope/app/appsetup/appsetup.py, line 25, in ? File /home/wichert/buildout-eggs/tmpG_NQ4q/zope.security-3.4.0b3-py2.4-linux-i686.egg/zope/security/management.py, line 25, in ? File /home/wichert/buildout-eggs/tmpG_NQ4q/zope.security-3.4.0b3-py2.4-linux-i686.egg/zope/security/checker.py, line 420, in ? AttributeError: 'module' object has no attribute 'thread_local' Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Proposal: Move ISite to zope.location was: ISite misplaced in zope.app.component.interfaces
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Howitz wrote: Hi, after thinking the problem over at gocept we came to the following suggestion: - A site is a place which gives acces to a component registry. - ISite isn't a good name for the concept behind it, because it is connected too tight to a website and on having hierarchical structures (at least in the code). - In long term a more abstract concept for ISite could be added. It is a place, in the classic Zope2 sense, as implied by placeful / placeless: a location-specificpolicy configuration point, which can acquire further policy configuration from above. In Zope2, nearly every persistent object is a place, at least for purposes of configuring security. - In short term, for cleaning up dependencies, I propose to move ISite to zope.location, because it is the only package outside of of zope.app.* which uses ISite and defindes a method to get the nearest site. We think this is the right place because ISite is about component registries in the context of location. +1 - zope.app.component.interfaces then can import ISite from the new place to avoid deprectation. +1. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGww5D+gerLs4ltQ4RAsP2AJ4lN1SCb+3mhPyaWolWrXjOIwDLIQCfTpax xDIRflBduAg55RDp3axNohI= =1VKk -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: 'thread_local' AttributeError in zope.security.checker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Fulton wrote: On Aug 14, 2007, at 7:32 PM, Paul Carduner wrote: Hello zope3-dev, I came across an error I have not seen before. Just for reference, here is the last snippet from the traceback: File /home/pcardune/Work/ZContact/zcontact-lp/eggs/tmpgwuq6O/ zope.security-3.4.0b4-py2.4-linux-i686.egg/zope/security/checker.py, line 420, in ? AttributeError: 'module' object has no attribute 'thread_local' I wish you had included the whole traceback. The interesting part to me is that it was so easy to fix. Here is a snippet of the relevant area of failing code from zope/security/checker.py # Get optimized versions try: import zope.security._zope_security_checker except ImportError: pass else: from zope.security._zope_security_checker import _checkers, selectChecker from zope.security._zope_security_checker import NoProxy, Checker from zope.security._zope_security_checker import _defaultChecker from zope.security._zope_security_checker import _available_by_default zope.interface.classImplements(Checker, INameBasedChecker) The very first import statement is throwing the error, but alas, it is not an ImportError. If I patch this code by catching the AttributeError in the same way the ImportError is caught, then everything works fine. Except you don't get the C optimizations. IOW, you would just be covering up a real error. I tried looking into the c code, but after years of python development, the c code just frightens me (a bit). That said, I would really appreciate any pointers people might be able to give me on what thread_local is for and why I (don't) need it. I rearranged the imports in zope.security yesterday. I apparently broke your usage, but I can't tell what your usage is. I'll need to see the whole traceback. In particular, I'll need to see the import order. We badly need to get a handle on how we expect people to fetch eggs for packages: having such a refactoring affect an indirect client (one not expecting to track day-to-day development) is a disaster. Dumping revision-stamped (unreleased) eggs into a directory used by unsuspecting users is a recipe for bringing *all* development to a screeching halt. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGww8E+gerLs4ltQ4RAizUAJ4/g04M14f9pI2QA/NAub2CwrVtDwCfQ2cD dQNNFuvkirf3sbAWOuC7/VE= =YjyB -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Dependency cleanup: zope.traversing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Wednesday 15 August 2007 08:01, Christian Theune wrote: zope.traversing has a dependency to zope.app.applicationcontroller. This is because zope.traversing implements the etc namespace and has a hard coded reference to applicationcontrol there. In the same place it also looks up site managers (in a hard coded way). As a strategy to remove this dependency we should move the etc namespace to some other place in zope.app. I did not find reasonable candidates to move this two. Bad candidates are zope.app.publisher or zope.app.publication, zope.app.applicationcontrol. A new package could be created for the etc namespace too, but I'd like to avoid that. I think that zope.app.component would be a good candidate, because etc is pretty much about accessing the local site. I know it was originally designed for allowing many different non-content things to be plugged in, but this has not materialized. An alternative would be to get rid of ++etc++ and implement ++site++ and ++control++. Now that I think about it, I actually favor this. ;-) Or change zope.traversing such that it looks up namespace-based stuff via a named utility / adapter; then packages which supply a namespace are not dependencies at all. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGww/h+gerLs4ltQ4RAm0LAJ491mh0nC4XbsX/SEG+d/0VHRUhBwCgoPkp XMLdvvMdQkoL2DKDfvQXA8s= =nvgz -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: 'thread_local' AttributeError in zope.security.checker
On Aug 15, 2007, at 10:34 AM, Tres Seaver wrote: ... We badly need to get a handle on how we expect people to fetch eggs for packages: having such a refactoring affect an indirect client (one not expecting to track day-to-day development) is a disaster. I'm not sure disaster is the word I'd use, but in general, I agree. Dumping revision-stamped (unreleased) eggs into a directory used by unsuspecting users is a recipe for bringing *all* development to a screeching halt. Yeah, I need to release the buildout changes that makes buildout prefer released eggs. Note that in this particular case, the real problem was circular imports. Circular imports create bugs that are hard or impossible to test for. I'd love to outlaw them. I wish we at least had a tool to warn about circular imports when testing. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] 'thread_local' AttributeError in zope.security.checker
I've just released a b5 egg which should correct the problem. Jim On Aug 15, 2007, at 9:51 AM, Wichert Akkerman wrote: Previously Jim Fulton wrote: On Aug 14, 2007, at 7:32 PM, Paul Carduner wrote: Hello zope3-dev, I came across an error I have not seen before. Just for reference, here is the last snippet from the traceback: File /home/pcardune/Work/ZContact/zcontact-lp/eggs/tmpgwuq6O/ zope.security-3.4.0b4-py2.4-linux-i686.egg/zope/security/ checker.py, line 420, in ? AttributeError: 'module' object has no attribute 'thread_local' I wish you had included the whole traceback. Here you are: [snow;/tmp/test]-119 bin/zopectl fg /tmp/test/parts/app/runzope -C /tmp/test/parts/zopectl/zope.conf Traceback (most recent call last): File /tmp/test/parts/app/runzope, line 97, in ? import zope.app.twisted.main File /home/wichert/buildout-eggs/tmp-GMMRj/ zope.app.twisted-3.4.0b1_r76119-py2.4.egg/zope/app/twisted/ main.py, line 32, in ? File /usr/lib/python2.4/site-packages/PIL/__init__.py, line 22, in ? File /home/wichert/buildout-eggs/tmpzGONPg/ zope.app.appsetup-3.4.0a1-py2.4.egg/zope/app/appsetup/appsetup.py, line 25, in ? File /home/wichert/buildout-eggs/tmpG_NQ4q/zope.security-3.4.0b3- py2.4-linux-i686.egg/zope/security/management.py, line 25, in ? File /home/wichert/buildout-eggs/tmpG_NQ4q/zope.security-3.4.0b3- py2.4-linux-i686.egg/zope/security/checker.py, line 420, in ? AttributeError: 'module' object has no attribute 'thread_local' Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/jim%40zope.com -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zope.security problems related to Python 2.5 update? (Was: Removed zope.security 3.4b4)
Wichert Akkerman wrote: Previously Christian Theune wrote: Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune: Hi, I saw the error reports about zope.security and got talked to from a few people that they had severe problems managing around this. I removed the 3.4b4 distribution from download.zope.org to allow them to continue using zopeproject and grokproject until we find a fix. I wasn't sure about that, so if someone has even worse problems now, please speak up and I'll put the package back into place again. I hope I didn't cause any more problems than exist already. This is deeper than I thought. b3 doesn't work either. It looks like the merge from the branch with support for Python 2.5 is causing the problems. I can confirm that the last release before the python 2.5 support was added (3.4.0-b2) works correctly. Just ran into this one. I think removing it is the right decision. b2 did work for me, but b4 just broke on me. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Removed zope.security 3.4b4
Christian Theune wrote: Hey, Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune: Hi, I saw the error reports about zope.security and got talked to from a few people that they had severe problems managing around this. I removed the 3.4b4 distribution from download.zope.org to allow them to continue using zopeproject and grokproject until we find a fix. I wasn't sure about that, so if someone has even worse problems now, please speak up and I'll put the package back into place again. I hope I didn't cause any more problems than exist already. Ok. As this affected more packages and Wichert found out how to deal with this in the buildout.cfg of grokproject (zopeproject and other buildout-based projects should be able to derive a workaround for this until it's fixed.) See http://paste.plone.org/16261 for the full buildout.cfg. The most important lines are 11 to 15: [app] recipe = zc.zope3recipes=0.5.3:application eggs = test zope.security==3.4.0b2 Does this mean the package won't get removed? I just prefer to use a situation where I don't get the broken egg in the first place. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.security problems related to Python 2.5 update? (Was: Removed zope.security 3.4b4)
Am Mittwoch, den 15.08.2007, 17:52 +0200 schrieb Martijn Faassen: Wichert Akkerman wrote: Previously Christian Theune wrote: Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune: Hi, I saw the error reports about zope.security and got talked to from a few people that they had severe problems managing around this. I removed the 3.4b4 distribution from download.zope.org to allow them to continue using zopeproject and grokproject until we find a fix. I wasn't sure about that, so if someone has even worse problems now, please speak up and I'll put the package back into place again. I hope I didn't cause any more problems than exist already. This is deeper than I thought. b3 doesn't work either. It looks like the merge from the branch with support for Python 2.5 is causing the problems. I can confirm that the last release before the python 2.5 support was added (3.4.0-b2) works correctly. Just ran into this one. I think removing it is the right decision. b2 did work for me, but b4 just broke on me. b5 is available already, so the problem should be over. Just delete b3 and b4 from your egg caches. I'm not sure that we should have to rely on removing packages like those. As Tres pointed out we should just avoid that everybody gets those immediately anyway, but we should keep them as historic releases in general. Christian ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.security problems related to Python 2.5 update? (Was: Removed zope.security 3.4b4)
On Aug 15, 2007, at 11:52 AM, Martijn Faassen wrote: Wichert Akkerman wrote: Previously Christian Theune wrote: Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune: Hi, I saw the error reports about zope.security and got talked to from a few people that they had severe problems managing around this. I removed the 3.4b4 distribution from download.zope.org to allow them to continue using zopeproject and grokproject until we find a fix. I wasn't sure about that, so if someone has even worse problems now, please speak up and I'll put the package back into place again. I hope I didn't cause any more problems than exist already. This is deeper than I thought. b3 doesn't work either. It looks like the merge from the branch with support for Python 2.5 is causing the problems. I can confirm that the last release before the python 2.5 support was added (3.4.0-b2) works correctly. Just ran into this one. I think removing it is the right decision. b2 did work for me, but b4 just broke on me. Try b5. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.security problems related to Python 2.5 update? (Was: Removed zope.security 3.4b4)
On Aug 15, 2007, at 11:56 AM, Christian Theune wrote: I'm not sure that we should have to rely on removing packages like those. I'm fairly sure that removing them is *not* the right solution. For example, that might have broken other applications. (After all, I released b4 for a reason.) The right short-term fix in this case was to use b2 in grok until b5 was released. As Tres pointed out we should just avoid that everybody gets those immediately anyway, but we should keep them as historic releases in general. Only getting released versions would probably have just delayed the problem until it would have been harder to solve. I was able to address this quickly because the changes that caused it were fresh in my mind. It would have been harder if the problem were reported much later. This particular problem was due to a circular import, which is a very hard thing to test for sadly. We need to fix this. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.security problems related to Python 2.5 update? (Was: Removed zope.security 3.4b4)
Am Mittwoch, den 15.08.2007, 17:59 +0200 schrieb Martijn Faassen: Where is this b5? I am still getting b4, not b5. I can't find b5 on the server. I've put it there now. The actual distribution was missing. I've created the b5 tag and uploaded the sdist package. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zope.security problems related to Python 2.5 update? (Was: Removed zope.security 3.4b4)
Jim Fulton wrote: [snip] Just ran into this one. I think removing it is the right decision. b2 did work for me, but b4 just broke on me. Try b5. I'd love to try the mysterious b5, but it's just not there. :) Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.security problems related to Python 2.5 update? (Was: Removed zope.security 3.4b4)
On Aug 15, 2007, at 12:00 PM, Martijn Faassen wrote: Jim Fulton wrote: [snip] Just ran into this one. I think removing it is the right decision. b2 did work for me, but b4 just broke on me. Try b5. I'd love to try the mysterious b5, but it's just not there. :) I tried to put it there, but my scp missfired. Christian uploaded it and it is there now. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: zope.security problems related to Python 2.5 update? (Was: Removed zope.security 3.4b4)
Am Mittwoch, den 15.08.2007, 12:02 -0400 schrieb Jim Fulton: On Aug 15, 2007, at 11:56 AM, Christian Theune wrote: I'm not sure that we should have to rely on removing packages like those. I'm fairly sure that removing them is *not* the right solution. For example, that might have broken other applications. (After all, I released b4 for a reason.) The right short-term fix in this case was to use b2 in grok until b5 was released. Right. I wasn't sure that people had a way to actually deal with this. I didn't like my approach either and it didn't help anyway. :/ As Tres pointed out we should just avoid that everybody gets those immediately anyway, but we should keep them as historic releases in general. Only getting released versions would probably have just delayed the problem until it would have been harder to solve. I was able to address this quickly because the changes that caused it were fresh in my mind. It would have been harder if the problem were reported much later. Hmm. Well. OTOH we just can't let *every* unsuspected user get that. That's bad from multiple points of view like experience, marketing, ... ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: zope.security problems related to Python 2.5 update? (Was: Removed zope.security 3.4b4)
Christian Theune wrote: Am Mittwoch, den 15.08.2007, 17:52 +0200 schrieb Martijn Faassen: Wichert Akkerman wrote: Previously Christian Theune wrote: Am Mittwoch, den 15.08.2007, 14:15 +0200 schrieb Christian Theune: Hi, I saw the error reports about zope.security and got talked to from a few people that they had severe problems managing around this. I removed the 3.4b4 distribution from download.zope.org to allow them to continue using zopeproject and grokproject until we find a fix. I wasn't sure about that, so if someone has even worse problems now, please speak up and I'll put the package back into place again. I hope I didn't cause any more problems than exist already. This is deeper than I thought. b3 doesn't work either. It looks like the merge from the branch with support for Python 2.5 is causing the problems. I can confirm that the last release before the python 2.5 support was added (3.4.0-b2) works correctly. Just ran into this one. I think removing it is the right decision. b2 did work for me, but b4 just broke on me. b5 is available already, so the problem should be over. Just delete b3 and b4 from your egg caches. Where is this b5? I am still getting b4, not b5. I can't find b5 on the server. I'm not sure that we should have to rely on removing packages like those. As Tres pointed out we should just avoid that everybody gets those immediately anyway, but we should keep them as historic releases in general. I just want my problem to go away with a minimum of fuss. :) Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] 'thread_local' AttributeError in zope.security.checker
Thanks for the quick response everybody. Next time I'll be sure to include the full traceback. - Paul On 8/15/07, Jim Fulton [EMAIL PROTECTED] wrote: I've just released a b5 egg which should correct the problem. Jim On Aug 15, 2007, at 9:51 AM, Wichert Akkerman wrote: Previously Jim Fulton wrote: On Aug 14, 2007, at 7:32 PM, Paul Carduner wrote: Hello zope3-dev, I came across an error I have not seen before. Just for reference, here is the last snippet from the traceback: File /home/pcardune/Work/ZContact/zcontact-lp/eggs/tmpgwuq6O/ zope.security-3.4.0b4-py2.4-linux-i686.egg/zope/security/ checker.py, line 420, in ? AttributeError: 'module' object has no attribute 'thread_local' I wish you had included the whole traceback. Here you are: [snow;/tmp/test]-119 bin/zopectl fg /tmp/test/parts/app/runzope -C /tmp/test/parts/zopectl/zope.conf Traceback (most recent call last): File /tmp/test/parts/app/runzope, line 97, in ? import zope.app.twisted.main File /home/wichert/buildout-eggs/tmp-GMMRj/ zope.app.twisted-3.4.0b1_r76119-py2.4.egg/zope/app/twisted/ main.py, line 32, in ? File /usr/lib/python2.4/site-packages/PIL/__init__.py, line 22, in ? File /home/wichert/buildout-eggs/tmpzGONPg/ zope.app.appsetup-3.4.0a1-py2.4.egg/zope/app/appsetup/appsetup.py, line 25, in ? File /home/wichert/buildout-eggs/tmpG_NQ4q/zope.security-3.4.0b3- py2.4-linux-i686.egg/zope/security/management.py, line 25, in ? File /home/wichert/buildout-eggs/tmpG_NQ4q/zope.security-3.4.0b3- py2.4-linux-i686.egg/zope/security/checker.py, line 420, in ? AttributeError: 'module' object has no attribute 'thread_local' Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/jim%40zope.com -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/paulcarduner%40gmail.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
