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
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.
-
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
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
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.
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
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
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
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) ·
-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
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:
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
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
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
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
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
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
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
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
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.
20 matches
Mail list logo
