Log message for revision 106668:
Note status of zope.app.pagetemplate
Changed:
U Zope/trunk/ZOPE_APP_DEPENDENCIES.rst
-=-
Modified: Zope/trunk/ZOPE_APP_DEPENDENCIES.rst
===
--- Zope/trunk/ZOPE_APP_DEPENDENCIES.rst
Log message for revision 106675:
Note that basicskin isn't quite as evil anymore
Changed:
U Zope/trunk/ZOPE_APP_DEPENDENCIES.rst
-=-
Modified: Zope/trunk/ZOPE_APP_DEPENDENCIES.rst
===
---
Log message for revision 106677:
Let's not bother with the transitive dependencies of zope.app.testing,
there's actually many more horrors... the real deal is to remove
zope.app.testing from the zope.* packages
Changed:
U Zope/trunk/ZOPE_APP_DEPENDENCIES.rst
-=-
Modified:
Log message for revision 106684:
We are almost there - formlib and functional testbrowser tests are the two
last items
Changed:
U Zope/trunk/ZOPE_APP_DEPENDENCIES.rst
-=-
Modified: Zope/trunk/ZOPE_APP_DEPENDENCIES.rst
===
On 12/15/09 11:49 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
Log message for revision 106536:
Include distribute, so we can use it in presence of the
allow-picked-versions=false
Changed:
U zopetoolkit/trunk/ztk.cfg
-=-
Summary of messages to the zope-tests list.
Period Tue Dec 15 12:00:00 2009 UTC to Wed Dec 16 12:00:00 2009 UTC.
There were 6 messages: 6 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Tue Dec 15 20:38:47 EST 2009
URL:
Thomas Lotze wrote:
Martijn Faassen wrote:
* have dummy implementations in zope.interface that raise
NotImplementedError
That would still introduce too many zope.component concepts into
zope.interface IMO: obviously that of utilities as one of the dummy
methods would bear that name, and
Hi there,
Baiju M wrote:
Most of the source distribution packages of ZTK are
in .tar.gz format. But there are few exceptions.
For consistency, can we use .tar.gz format for all releases ?
Which are the exceptions?
Regards,
Martijn
___
On Wed, Dec 16, 2009 at 08:35, Baiju M mba...@zeomega.com wrote:
Hi,
Most of the source distribution packages of ZTK are
in .tar.gz format. But there are few exceptions.
For consistency, can we use .tar.gz format for all releases ?
Why do we need consistency? I mostly use tgz, but that's
Hello Martijn,
I guess which were created by windowze people. It does zips by default.
Wednesday, December 16, 2009, 3:39:00 PM, you wrote:
MF Hi there,
MF Baiju M wrote:
Most of the source distribution packages of ZTK are
in .tar.gz format. But there are few exceptions.
For
On Wed, Dec 16, 2009 at 4:40 PM, Adam GROSZER agros...@gmail.com wrote:
I guess which were created by windowze people. It does zips by default.
Nope. I only create zips being on Mac OS.
With the tarfile module in Python 2.4 being utterly broken, I ran into
too much trouble with broken tar.gzips
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
schrieb Hanno Schlichting:
On Wed, Dec 16, 2009 at 4:40 PM, Adam GROSZER agros...@gmail.com
wrote:
I guess which were created by windowze people. It does zips by
default.
Nope. I only create zips being on Mac OS.
With the tarfile module in
On Wed, Dec 16, 2009 at 8:09 PM, Martijn Faassen faas...@startifact.com wrote:
Hi there,
Baiju M wrote:
Most of the source distribution packages of ZTK are
in .tar.gz format. But there are few exceptions.
For consistency, can we use .tar.gz format for all releases ?
Which are the
Martijn Faassen wrote:
Thomas Lotze wrote:
Martijn Faassen wrote:
* have dummy implementations in zope.interface that raise
NotImplementedError
That would still introduce too many zope.component concepts into
zope.interface IMO: obviously that of utilities as one of the dummy
methods
Thomas Lotze wrote:
I'm
not sure whether we should make the name of that parameter consistent
between zope.component and zope.interface,
Sorry, nevermind. Of course we'll want to rename that parameter as our
secret plan is to access the ZCA through Interface.__call__ one day.
--
Thomas
On Wed, Dec 16, 2009 at 17:31, Baiju M mba...@zeomega.com wrote:
Others has already raised their concern against .tar.gz
as it is not working in Python 2.4
And bz2 module might be missing for many Python installations.
(BTW, We don't have any bz2 source packages released)
Right. So for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Tres Seaver wrote:
Martin Aspeli wrote:
zope.component raises TypeError if you can't adapt. It raises
ComponentLookupError it can't find a utility.
Not so: see $ZSVN/zope.component/trunk/src/zope/component/registry.py:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
Thomas Lotze wrote:
Martijn Faassen wrote:
* have dummy implementations in zope.interface that raise
NotImplementedError
That would still introduce too many zope.component concepts into
zope.interface IMO: obviously that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
On 2009-12-16 08:35, Baiju M wrote:
Hi,
Most of the source distribution packages of ZTK are
in .tar.gz format. But there are few exceptions.
For consistency, can we use .tar.gz format for all releases ?
Once there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
On Wed, Dec 16, 2009 at 9:23 PM, Chris Withers ch...@simplistix.co.uk wrote:
Baiju M wrote:
Most of the source distribution packages of ZTK are
in .tar.gz format. But there are few exceptions.
For consistency, can we use
Tres Seaver wrote:
In either case, I think TypeError (or maybe LookupError) is the *right*
choice: we don't want to hide zope.component's API functions and then
turn around and require folks to import zope.component just to catch its
local exception types.
Yeah, that's a compelling reason.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Tres Seaver wrote:
In either case, I think TypeError (or maybe LookupError) is the *right*
choice: we don't want to hide zope.component's API functions and then
turn around and require folks to import zope.component just to
Hi,
Any plan for releasing 64 bit Windows binaries for ZODB, ZTK Zope 2 ?
Anyone used MinGW for 64 bit Windows to compile Zope packages ?
Regards,
Baiju M
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
Hi!
I've a Zope BTree called answers. It contains PersistentMapping objects:
self.answers[userid] = PersistentMapping(value=value,
comments=comments)
value can be a string, a list or a dictionary
what happen exactly if I do:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yuri wrote:
Hi!
I've a Zope BTree called answers. It contains PersistentMapping objects:
self.answers[userid] = PersistentMapping(value=value,
comments=comments)
value can be a string, a list
25 matches
Mail list logo
