Brandon Craig Rhodes wrote:
[buildout]
...
versions = versions
Should we write something like Grok for buildout, so that it just uses
sections without having to have them doubly declared up at the top? :-)
Heh, nah, this was a fair cop. I *did* actually know about this, was
just a silly
Dieter Maurer wrote:
Then, we could get rid of the {get|query}[Multi]Adapter altogether
and consistently use I() with appropriate optional parameters --
what a simplification and homogenization :-)
Yeah, but since when has simplification or homogenisation been a goal of
Zope 3? ;-)
Chris
Dieter Maurer wrote:
Jim is heavily defending this difference.
I am convinced that the difference should not be there
fork anyone? ;-)
but meanwhile have found a use case for it.
Suppose, you have a class C that implements I.
If queryAdapter would behave like I(...), you
would
Benji York wrote:
On Mon, Aug 25, 2008 at 6:24 AM, Michael Howitz [EMAIL PROTECTED] wrote:
Log message for revision 90184:
made doctest sections from the literal sections
Thanks for removing the unneccesary -- and inappropriate
Why are they unneccesary and inappropriate?
These are what
Martijn Faassen wrote:
What's up? Clearly something went wrong during the releasing of this
package, at least documentation-wise. Should be fixed.
I'd hazard a guess at yet another brown bag release that now no-one
wants to remove for the same stupid reasons that are always parrotted as
soon
Benji York wrote:
It'll have to be an external to
svn+ssh://svn.zope.org/repos/main/zc.buildout/trunk/bootstrap since
Subversion doesn't do externals to individual files.
The zope.introspector project is one example taking this approach:
Trying to get a feeling here on whether we want to require proper XML
namespace definition (current z3c.pt behavior) or implicitly fallback to
the standard mappings (current zope.pagetemplate behavior).
\malthe
___
Zope-Dev maillist -
--On 29. August 2008 12:31:21 +0200 Malthe Borch [EMAIL PROTECTED] wrote:
Trying to get a feeling here on whether we want to require proper XML
namespace definition (current z3c.pt behavior) or implicitly fallback to
the standard mappings (current zope.pagetemplate behavior).
Can you
Am Donnerstag 28 August 2008 23:55:24 schrieb Martin Aspeli:
Hermann Himmelbauer wrote:
Am Donnerstag 28 August 2008 02:35:28 schrieb Marius Gedminas:
On Wed, Aug 27, 2008 at 05:15:48PM -0700, Stephan Richter wrote:
On Wednesday 27 August 2008, Martin Aspeli wrote:
This means that if the
Benji York wrote:
For the forked doctest in zope.testing, the Zope 3 project's bug tracker
in Launchpad would be appropriate.
https://bugs.edge.launchpad.net/zope.testing/+bug/262578
I suspect Python's doctest has the same bug; checking that and reporting
the bug to them would be good too.
Am Donnerstag 28 August 2008 17:45:58 schrieb Marius Gedminas:
On Thu, Aug 28, 2008 at 05:26:20PM +0200, Hermann Himmelbauer wrote:
Am Donnerstag 28 August 2008 10:14:11 schrieb Martin Aspeli:
What about the case when you have a list of options of which you need
to chose one or more? In
Summary of messages to the zope-tests list.
Period Thu Aug 28 11:00:00 2008 UTC to Fri Aug 29 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.
Unknown
---
Subject: UNKNOWN : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Thu Aug 28 20:43:02 EDT 2008
URL:
2008/8/29 Andreas Jung [EMAIL PROTECTED]:
--On 29. August 2008 12:31:21 +0200 Malthe Borch [EMAIL PROTECTED] wrote:
Trying to get a feeling here on whether we want to require proper XML
namespace definition (current z3c.pt behavior) or implicitly fallback to
the standard mappings (current
The Python 2.3 on that box hasn't changed in a while, and the
encodings module works, at least interactively.
$ /usr/local/python2.3/bin/python
Python 2.3.6 (#1, Nov 11 2006, 11:08:56)
[GCC 4.0.2 (Debian 4.0.2-2)] on linux2
Type help, copyright, credits or license for more information.
import
--On 29. August 2008 13:20:38 +0200 Malthe Borch [EMAIL PROTECTED] wrote:
2008/8/29 Andreas Jung [EMAIL PROTECTED]:
--On 29. August 2008 12:31:21 +0200 Malthe Borch [EMAIL PROTECTED]
wrote:
Trying to get a feeling here on whether we want to require proper XML
namespace definition
What I have found out now is that in my Python 2.3.6 encodings/
__init__.py does not contain 'import aliases' at module level,
whereas the Python 2.4 lib has this import. The patch does this:
import encodings
encodings._aliases = encoding.aliases.aliases
which does therefore not work in 2.3.
Hi Hermann
Betreff: Re: [Zope-dev] z3c.form - extraction from sequence widget
[...]
I think you *could* interpret it so that a boolean field that's
required really means you have to tick this box (e.g. an
I agree to
these terms and conditions type scenario).
My idea is to look at
On Fri, Aug 29, 2008 at 5:53 AM, Chris Withers [EMAIL PROTECTED] wrote:
Benji York wrote:
It'll have to be an external to
svn+ssh://svn.zope.org/repos/main/zc.buildout/trunk/bootstrap since
Subversion doesn't do externals to individual files.
The zope.introspector project is one example
On Fri, Aug 29, 2008 at 5:36 AM, Chris Withers [EMAIL PROTECTED] wrote:
Benji York wrote:
On Mon, Aug 25, 2008 at 6:24 AM, Michael Howitz [EMAIL PROTECTED] wrote:
Log message for revision 90184:
made doctest sections from the literal sections
Thanks for removing the unneccesary -- and
On Fri, Aug 29, 2008 at 12:31:21PM +0200, Malthe Borch wrote:
Trying to get a feeling here on whether we want to require proper XML
namespace definition (current z3c.pt behavior) or implicitly fallback to
the standard mappings (current zope.pagetemplate behavior).
Requiring explicit XML
I'll try to make the ISource API smooth and usable
for other components. Right now ISource provides no
simple API for work with terms.
Since a ISource only provides a __contains__ method
and the IterableSource the __iter__ method,
there is some more needed which makes it easy to
work with terms
Martijn Faassen wrote:
I just looked at the PyPI page of 'transaction':
http://pypi.python.org/pypi/transaction
And I see some weirdnesses:
* it's called 'transaction 1.0a1'
* the 'changes' claim however:
1.0 (unreleased)
What's up? Clearly something went wrong during the
On Fri, Aug 29, 2008 at 14:05, Stefan H. Holek [EMAIL PROTECTED] wrote:
What I have found out now is that in my Python 2.3.6 encodings/
__init__.py does not contain 'import aliases' at module level,
whereas the Python 2.4 lib has this import. The patch does this:
import encodings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan H. Holek wrote:
What I have found out now is that in my Python 2.3.6 encodings/
__init__.py does not contain 'import aliases' at module level,
whereas the Python 2.4 lib has this import. The patch does this:
import encodings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Pieters wrote:
On Fri, Aug 29, 2008 at 14:05, Stefan H. Holek [EMAIL PROTECTED] wrote:
What I have found out now is that in my Python 2.3.6 encodings/
__init__.py does not contain 'import aliases' at module level,
whereas the Python 2.4
On Fri, Aug 29, 2008 at 5:13 PM, Malthe Borch [EMAIL PROTECTED] wrote:
Log message for revision 90599:
Move test-dependencies to 'extras'.
This is a controversial change; can we avoid making changes like this
until a policy is agreed upon?
The controversy surrounding this has been discussed
Fred Drake wrote:
This is a controversial change; can we avoid making changes like this
until a policy is agreed upon?
The controversy surrounding this has been discussed on zope-dev
several times; I don't want to rehash it *right now*, since we all
have things we need to get done.
I
On Fri, Aug 29, 2008 at 5:26 PM, Malthe Borch [EMAIL PROTECTED] wrote:
I didn't know there was a controversy, but I do remember that there was
consensus that ``extras_require`` is not the most elegant solution.
Oh, there is!
If you can advise a different way to avoid pulling in
Fred Drake wrote:
There's no good way to avoid dependencies like zope.app.testing;
because that's part of the test environment, the tests won't show
whether there are problems when it's removed. If you want to fly what
you test, test dependencies can't be eliminated.
I understand, but this
Hi Fred
Betreff: Re: [Checkins] SVN: zope.dublincore/trunk/ Move
test-dependenciesto 'extras'.
On Fri, Aug 29, 2008 at 5:13 PM, Malthe Borch
[EMAIL PROTECTED] wrote:
Log message for revision 90599:
Move test-dependencies to 'extras'.
This is a controversial change; can we avoid
On Fri, Aug 29, 2008 at 11:59:24PM +0200, Malthe Borch wrote:
Fred Drake wrote:
There's no good way to avoid dependencies like zope.app.testing;
because that's part of the test environment, the tests won't show
whether there are problems when it's removed. If you want to fly what
you
Hi
Betreff: Re: [Zope-dev] SVN: zope.dublincore/trunk/ Move
test-dependenciesto 'extras'.
Fred Drake wrote:
There's no good way to avoid dependencies like zope.app.testing;
because that's part of the test environment, the tests won't show
whether there are problems when it's
Hi Marius
Betreff: Re: [Zope-dev] SVN: zope.dublincore/trunk/
Movetest-dependencies to 'extras'.
[...]
I understand, but this particular dependency pulls in the
world, all
76 packages.
I'll revert the change; it seems we're about to have a fork
the size
of the emacs/xemacs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fred Drake wrote:
On Fri, Aug 29, 2008 at 5:26 PM, Malthe Borch [EMAIL PROTECTED] wrote:
I didn't know there was a controversy, but I do remember that there was
consensus that ``extras_require`` is not the most elegant solution.
Oh, there is!
Previously Malthe Borch wrote:
Trying to get a feeling here on whether we want to require proper XML
namespace definition (current z3c.pt behavior) or implicitly fallback to
the standard mappings (current zope.pagetemplate behavior).
+1 for requiring proper XML namespace. Tools like xmllint
Chris Withers wrote at 2008-8-29 10:25 +0100:
Dieter Maurer wrote:
Then, we could get rid of the {get|query}[Multi]Adapter altogether
and consistently use I() with appropriate optional parameters --
what a simplification and homogenization :-)
Yeah, but since when has simplification or
36 matches
Mail list logo
