[Zope-dev] zope.app.module, zope.app.interface and zodb in KGS?
zope.app.module provides support for persistemt modules. zope.app.interface provides support for persistent interfaces. Both rely on a highly experimental zodbcode. I don't have a problem with these being projects, but I don't think they should be in the KGS. I don't think we should commit to supporting them, at least not as part of the KGS. Does anyone disagree? Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Some thoughts on KGS
I think the KGS should define 3 categories of packages: - ZTK packages These are packages we maintain and expect people to build things on. - Test packages These are packages that build on the ZTK. These are used to test the ZTK packages, but aren't part of the ZTK. - dependencies of ZTK packages or test packages. Note that the ZTK should probably avoid non-third-party dependencies that are not part of the ZTK. There are some fuzzy cases, like ZODB and ZConfig. I propose that any test infrastructure we come up with needs to handle these 3 cases. In any cases, the test infrastructure needs to fix version for all of the categories of packages and there needs to be a formal process (uh, like tests passing :) for updating the configuration. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.module, zope.app.interface and zodb in KGS?
On Thu, Jul 2, 2009 at 12:30 PM, Jim Fultonj...@zope.com wrote: zope.app.module provides support for persistemt modules. zope.app.interface provides support for persistent interfaces. Both rely on a highly experimental zodbcode. I don't have a problem with these being projects, but I don't think they should be in the KGS. I don't think we should commit to supporting them, at least not as part of the KGS. Does anyone disagree? +10 on removing those from the KGS. Right now both zope.app.zapi and zope.app.zcmlfiles still have a hard dependency on zope.app.interface though. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.module, zope.app.interface and zodb in KGS?
On Jul 2, 2009, at 7:58 AM, Hanno Schlichting wrote: On Thu, Jul 2, 2009 at 12:30 PM, Jim Fultonj...@zope.com wrote: zope.app.module provides support for persistemt modules. zope.app.interface provides support for persistent interfaces. Both rely on a highly experimental zodbcode. I don't have a problem with these being projects, but I don't think they should be in the KGS. I don't think we should commit to supporting them, at least not as part of the KGS. Does anyone disagree? +10 on removing those from the KGS. Right now both zope.app.zapi This was deprecated a long time ago. I think we should remove it from the kgs. Is anyone using it? and zope.app.zcmlfiles still have a hard dependency on zope.app.interface though. I don't think zope.app.zcml files should be in it either. It was intended as a bridge to get us from teh monolith world to the new world. Perhaps zope.app.zcml files should become a sort of meta package for some working set of the things it depends on, at some revision at which it worked, perhaps corresponding to the 3.4.0 release/kgs. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing 3.7.7
On Thu, 2009-07-02 at 09:59 -0400, Jim Fulton wrote: On Jul 2, 2009, at 9:55 AM, Christian Theune wrote: I just released zope.testing 3.7.7. It only contains a single change: installing the test runner callable via a console_script entry point to allow simple usage without buildout. Did you get the tests to pass on windows? Ugh. I didn't know they didn't pass currently. Did they pass for 3.7.6? At least that was released and there was only one change in between, so I didn't suspect failing tests there. /me wanders off to windows land. -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing 3.7.7
On Jul 2, 2009, at 10:06 AM, Christian Theune wrote: On Thu, 2009-07-02 at 09:59 -0400, Jim Fulton wrote: On Jul 2, 2009, at 9:55 AM, Christian Theune wrote: I just released zope.testing 3.7.7. It only contains a single change: installing the test runner callable via a console_script entry point to allow simple usage without buildout. Did you get the tests to pass on windows? Ugh. I didn't know they didn't pass currently. Did they pass for 3.7.6? At least that was released and there was only one change in between, so I didn't suspect failing tests there. To my very happy amazement, they pass for me with Python 2.4-2.5. I'm getting a test failure for Python 2.6, but that's on both Linux and Windows. :/ Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing 3.7.7
On Jul 2, 2009, at 9:55 AM, Christian Theune wrote: I just released zope.testing 3.7.7. It only contains a single change: installing the test runner callable via a console_script entry point to allow simple usage without buildout. Did you get the tests to pass on windows? Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Distutils] Where is the setuptools source repository?
Switching to zope-dev. On Jul 2, 2009, at 10:40 AM, Chris Withers wrote: Jim Fulton wrote: buildout works fine. The problem is the zope.testing test runner, which will find tests in your eggs directory if your buildout is in your software path. I'm safe from this one, since I store all my eggs in ~/buildout-eggs as specified in my ~/.buildout/default.cfg. However, the same problem occurs with the contents of the build directory :-( It is really rather shallow and should be easy to fix. The issue is that the test finder will descend into directories that don't have __init__.py files, and shouldn't. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.testing 3.7.7
I just released zope.testing 3.7.7. It only contains a single change: installing the test runner callable via a console_script entry point to allow simple usage without buildout. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] FYI: svn.zope.org change for svn:// protocol service
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, This is a heads-up that affects anyone accessing the SVN repositories using the svn:// protocol (so it does not affect anyone accessing SVN over HTTP, or svn+ssh): So far the svn service was run through xinetd. We had recurring problems where either during really busy times or when too many svn service processes hung for unknown reasons xinetd would refuse to start more of them. This would lead to strange errors for people accessing the service. To hopefully solve that problem, and maybe solve the hanging process issues as well, I have switched to using the svnserve process in daemon mode instead of using it through xinetd. If you do use the svn:// protocol (maybe directly, or indirectly through a svn:extrnals definition, or for replicating the repositories with svnsync) and see any issues please contact me directly off-list. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkpMwSkACgkQRAx5nvEhZLJgKwCglIvmEO9jeoEa3ZrYGo3fas+g 5LQAoJf+F7r4L31He5jrvubNqz7YnTpV =37QJ -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.testing 3.7.7
On Thu, 2009-07-02 at 10:41 -0400, Jim Fulton wrote: On Jul 2, 2009, at 10:06 AM, Christian Theune wrote: On Thu, 2009-07-02 at 09:59 -0400, Jim Fulton wrote: On Jul 2, 2009, at 9:55 AM, Christian Theune wrote: I just released zope.testing 3.7.7. It only contains a single change: installing the test runner callable via a console_script entry point to allow simple usage without buildout. Did you get the tests to pass on windows? Ugh. I didn't know they didn't pass currently. Did they pass for 3.7.6? At least that was released and there was only one change in between, so I didn't suspect failing tests there. To my very happy amazement, they pass for me with Python 2.4-2.5. I'm getting a test failure for Python 2.6, but that's on both Linux and Windows. :/ Yeah. I'm getting that one on 2.6. I'm also getting one on Python 2.4 on Linux which I remember as being spurious. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.module, zope.app.interface and zodb in KGS?
On Thu, Jul 2, 2009 at 3:41 PM, Jim Fultonj...@zope.com wrote: On Jul 2, 2009, at 7:58 AM, Hanno Schlichting wrote: and zope.app.zcmlfiles still have a hard dependency on zope.app.interface though. I don't think zope.app.zcml files should be in it either. It was intended as a bridge to get us from teh monolith world to the new world. Perhaps zope.app.zcml files should become a sort of meta package for some working set of the things it depends on, at some revision at which it worked, perhaps corresponding to the 3.4.0 release/kgs. I think zcmlfiles is still a testing dependency of quite a bit of stuff. Basically anything that tries to do functional testing sets up some kind of complete test fixture based on this IIRC. And we haven't yet gotten rid of all zope.app.* packages that do this. I'm not saying this should be that case, but it might be something that needs to be resolved, before we can remove this thing from the KGS. Removing it when still various tests depend on it, doesn't strike me as the best way to do things. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] issues with building zope2.11.3
Hello, at preparing zope2.11.3 for debian, i came across several byte-compiling errors. three of them are due to the new tests for python2.5 and python2.6, and are just failing because python2.4 is the python version debian uses for zope2.11. but the last one seems to be a real bug: Compiling /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py ... File /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py, line 91 yield row SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause I also found this error in list archive logs of zope-te...@epy.co.at. from 'pydoc2.4 yield': The yield statement is not allowed in the try clause of a try ... finally construct. The difficulty is that there's no guarantee the generator will ever be resumed, hence no guarantee that the finally block will ever get executed. is this a known bug, and does a fix exist? greetings, jonas ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] issues with building zope2.11.3
On 02.07.09 18:32, Jonas Meurer wrote: Hello, at preparing zope2.11.3 for debian, i came across several byte-compiling errors. three of them are due to the new tests for python2.5 and python2.6, and are just failing because python2.4 is the python version debian uses for zope2.11. but the last one seems to be a real bug: Compiling /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py ... File /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py, line 91 yield row SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause I also found this error in list archive logs of zope-te...@epy.co.at. from 'pydoc2.4 yield': The yield statement is not allowed in the try clause of a try ... finally construct. The difficulty is that there's no guarantee the generator will ever be resumed, hence no guarantee that the finally block will ever get executed. is this a known bug, no - please file a bug report and does a fix exist? Unlikely - and I don't think that this issue is of relevance. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.module, zope.app.interface and zodb in KGS?
On Jul 2, 2009, at 12:11 PM, Hanno Schlichting wrote: On Thu, Jul 2, 2009 at 3:41 PM, Jim Fultonj...@zope.com wrote: On Jul 2, 2009, at 7:58 AM, Hanno Schlichting wrote: and zope.app.zcmlfiles still have a hard dependency on zope.app.interface though. I don't think zope.app.zcml files should be in it either. It was intended as a bridge to get us from teh monolith world to the new world. Perhaps zope.app.zcml files should become a sort of meta package for some working set of the things it depends on, at some revision at which it worked, perhaps corresponding to the 3.4.0 release/kgs. I think zcmlfiles is still a testing dependency of quite a bit of stuff. Basically anything that tries to do functional testing sets up some kind of complete test fixture based on this IIRC. And we haven't yet gotten rid of all zope.app.* packages that do this. You're probably right I'm not saying this should be that case, but it might be something that needs to be resolved, before we can remove this thing from the KGS. Removing it when still various tests depend on it, doesn't strike me as the best way to do things. probably not Then the question is whether the dependence of zope.app.zcmlfiles on zope.app.interface is needed. I'll look to see what that's about. I need to resist the urge to clean things up and leave them in if they aren't causing test failures, I'd really like to get to something more flexible that zope.app.testing.functional, to make it simpler for applications to use only as much set up as they need. zope.app.testing.function was great in its time, but I think we can do better. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] issues with building zope2.11.3
Hello again, first, thanks for the fast response. On 02/07/2009 Andreas Jung wrote: Compiling /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py ... File /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py, line 91 yield row SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause I also found this error in list archive logs of zope-te...@epy.co.at. from 'pydoc2.4 yield': The yield statement is not allowed in the try clause of a try ... finally construct. The difficulty is that there's no guarantee the generator will ever be resumed, hence no guarantee that the finally block will ever get executed. is this a known bug, no - please file a bug report done: https://bugs.launchpad.net/zope2/+bug/394809 and does a fix exist? Unlikely - and I don't think that this issue is of relevance. I believe that this bug persists in zope2.12+, so it should be fixed in my eyes. greetings, jonas signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] issues with building zope2.11.3
On 02.07.09 19:23, Jonas Meurer wrote: Hello again, first, thanks for the fast response. On 02/07/2009 Andreas Jung wrote: Compiling /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py ... File /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py, line 91 yield row SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause I also found this error in list archive logs of zope-te...@epy.co.at. from 'pydoc2.4 yield': The yield statement is not allowed in the try clause of a try ... finally construct. The difficulty is that there's no guarantee the generator will ever be resumed, hence no guarantee that the finally block will ever get executed. is this a known bug, no - please file a bug report done: https://bugs.launchpad.net/zope2/+bug/394809 Thanks! and does a fix exist? Unlikely - and I don't think that this issue is of relevance. I believe that this bug persists in zope2.12+, so it should be fixed in my eyes. mechanize is basically a third-party module shipped with Zope. Since Zope 2.12 requires Python 2.5 or 2.6 there is a chance will be resolved automatically :) Andreas this issue begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] issues with building zope2.11.3
On 02/07/2009 Andreas Jung wrote: On 02/07/2009 Andreas Jung wrote: Compiling /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py ... File /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py, line 91 yield row SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause I also found this error in list archive logs of zope-te...@epy.co.at. from 'pydoc2.4 yield': The yield statement is not allowed in the try clause of a try ... finally construct. The difficulty is that there's no guarantee the generator will ever be resumed, hence no guarantee that the finally block will ever get executed. and does a fix exist? Unlikely - and I don't think that this issue is of relevance. I believe that this bug persists in zope2.12+, so it should be fixed in my eyes. mechanize is basically a third-party module shipped with Zope. Since Zope 2.12 requires Python 2.5 or 2.6 there is a chance will be resolved automatically :) yea, sounds reasonable. still, that means that zope2.11 uses features of python2.5+ while it still recommends and supports only python2.4. does this mean, that zope2.11 works and is tested with python2.5? greetings, jonas ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] issues with building zope2.11.3
On 02.07.09 19:41, Jonas Meurer wrote: On 02/07/2009 Andreas Jung wrote: On 02/07/2009 Andreas Jung wrote: Compiling /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py ... File /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py, line 91 yield row SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause I also found this error in list archive logs of zope-te...@epy.co.at. from 'pydoc2.4 yield': The yield statement is not allowed in the try clause of a try ... finally construct. The difficulty is that there's no guarantee the generator will ever be resumed, hence no guarantee that the finally block will ever get executed. and does a fix exist? Unlikely - and I don't think that this issue is of relevance. I believe that this bug persists in zope2.12+, so it should be fixed in my eyes. mechanize is basically a third-party module shipped with Zope. Since Zope 2.12 requires Python 2.5 or 2.6 there is a chance will be resolved automatically :) yea, sounds reasonable. still, that means that zope2.11 uses features of python2.5+ while it still recommends and supports only python2.4. mechanize is only used tests (using Five.testbrowser and zope.testbrowser). So the functionality of Zope does not depend on mechanize and especially not of this one Python file..I doubt that this file is ever used...so possibly pretty dead code from the Zope point of view - that's why I don't care much this issue. does this mean, that zope2.11 works and is tested with python2.5? No. Python 2.4 is required. Andreas begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] A suggestion for changing exception handler when loading 'c' optimisations to make modules more friendly for GAE
Hi all
Can I make a suggestion that would make a couple of modules more gae
friendly ;-)
zope.interface and zope.i18nmessageid have 'c' optimisations which
obviously don't work under app engine.
When these modules are imported you get the following exception.
gae/1.333250465889549129/zope/i18nmessageid/_zope_i18nmessageid_message.py,
line 6, in __bootstrap__
imp.load_dynamic(__name__,__file__)
File /base/python_dist/lib/python2.5/py_imp.py, line 116, in load_dynamic
raise NotImplementedError('This function is not supported on App Engine.')
Unfortunately the code (in this case in zope.i18nmessageid.Message)
does the following which doesn't deal with the Exception
raised by the app engine runtime.
try:
from _zope_i18nmessageid_message import Message
except ImportError:
pass
To make it more gae friendly I think we should change these occurrences to
try:
from _zope_i18nmessageid_message import Message
except ImportError, NotImplementedError:
pass
Regards
Tim
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
