On Tue, May 4, 2010 at 10:54 PM, Charlie Clark
wrote:
> I think some kind of paper trail is definitely a good idea. Not sure if
> docs is the right place but Christian is planning to put the reports into
> the svn repository. And both location and form are less important than
> having an archive*.
Charlie Clark wrote:
> I think some kind of paper trail is definitely a good idea. Not sure if
> docs is the right place but Christian is planning to put the reports into
> the svn repository. And both location and form are less important than
> having an archive*. We'll have something sorted
Am 04.05.2010, 22:43 Uhr, schrieb Martijn Faassen :
> Hi there,
> Wouldn't it be useful to add the reports of the weekly IRC meetings to
> the ZTK docs? This way we have an archive that includes some decisions
> and such that's easier to go through than the mailing list archive. It
> also provides
Hi there,
Wouldn't it be useful to add the reports of the weekly IRC meetings to
the ZTK docs? This way we have an archive that includes some decisions
and such that's easier to go through than the mailing list archive. It
also provides a source of information that could then later be
integrat
Am 04.05.2010, 15:12 Uhr, schrieb Christian Theune :
> Hi,
> thanks, Charlie for doing this. Would you consider being the second
> person to handle the meetings (reminders, presence, and summaries)
> together with me?
I don't mind - not hard for me to play the clueless guy asking the dumb
quest
Hi,
quite a crowd today. Must be have been drawn by my star status! ;-)
Charlie
--
Charlie Clark
Managing Director
Clark Consulting & Research
German Office
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-600-3657
Mobile: +49-178-782-6226=
Weekly Zope developer meet
On May 4, 2010, at 6:07 AM, Martijn Faassen wrote:
> For a while already people have been making changes that at least break
> tests on 2.4. For instance, zope.testing has some facility to pretty print a
> dictionary that sorts the keys, because Python 2.4's built-in pretty print
> module appar
On Tue, May 4, 2010 at 15:31, Tres Seaver wrote:
> The Securactive stuff seems to be offline (503s or non-resolvable
> hostnames).
Hi Tres,
Sorry for that, I've stopped accidentally the builbots this morning.
--
Sebastien Douche
Twitter: http://bit.ly/afkrK (agile, lean, python, open source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Hanno Schlichting wrote:
>> Dropping Python 2.4 supports makes most sense to me at this stage.
>> Zope2/Plone only support Python 2.6 for any modern version.
>>
>> I don't know what BlueBream and Grok want to support, but would
Hi,
thanks, Charlie for doing this. Would you consider being the second
person to handle the meetings (reminders, presence, and summaries)
together with me?
I'd like to adjust your agenda a little bit:
On 05/04/2010 02:24 PM, Charlie Clark wrote:
> Hi,
>
> can't see Theuni anywhere so I though
Hi,
sorry for the lag (and thanks for Charlie to pick up the reminder today).
Here's last weeks summary.
Biggeste note: next bug day is on 2010-05-19 which is a rainy Wednesday
- a perfect day for sitting inside and smashing bugs.
Christian
--
Christian Theune · c...@gocept.com
gocept gmbh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lennart Regebro wrote:
> On Mon, May 3, 2010 at 20:02, Tres Seaver wrote:
>> - - zope.browserpage
>> - - zope.viewlet
>> - - zope.contentprovider
>> - - zope.deferredimport
>
> These tests all fail because as Tres pointed out, Python 2.4 doesn't
> se
Hi,
can't see Theuni anywhere so I thought I'd do the honours - the meeting
will be on #zope in just over two-and-a-half hours.
Not sure about the Agenda but I think there is some KGS to be carried over
from last week and possibly some of the very recent ZTK discussions need
formalising so
Summary of messages to the zope-tests list.
Period Mon May 3 12:00:00 2010 UTC to Tue May 4 12:00:00 2010 UTC.
There were 16 messages: 6 from Zope Tests, 9 from ccomb at free.fr, 1 from ct
at gocept.com.
Test failures
-
Subject: FAILED: Repository policy check found errors in 670
On Tue, May 4, 2010 at 4:25 AM, Tres Seaver wrote:
> Should the triumvirs so decide, attached is the patch for zopetoolkit
> which adopts the versions from Zope2. The "normal" buildout (using eggs
> rather than checkouts) passes all test-ztk and test-zopeapp tests with
> this patch applied.
As f
On Tue, May 4, 2010 at 12:07, Martijn Faassen wrote:
> For a while already people have been making changes that at least break
> tests on 2.4. For instance, zope.testing has some facility to pretty
> print a dictionary that sorts the keys, because Python 2.4's built-in
> pretty print module appare
Hanno Schlichting wrote:
> Dropping Python 2.4 supports makes most sense to me at this stage.
> Zope2/Plone only support Python 2.6 for any modern version.
>
> I don't know what BlueBream and Grok want to support, but would guess
> they aim for Python 2.5 + 2.6 support. 2.4 is really old by now.
Hi there,
Christophe Combelles wrote:
> Unless I missed something, the ZTK was globally compatible with Python2.4
> recently, wasn't it? Do we want the latest changes and Lennart's work to be
> part of the ZTK 1.0?
For a while already people have been making changes that at least break
tests
On Mon, May 3, 2010 at 20:02, Tres Seaver wrote:
> - - zope.browserpage
> - - zope.viewlet
> - - zope.contentprovider
> - - zope.deferredimport
These tests all fail because as Tres pointed out, Python 2.4 doesn't
set __file__ to the doctest filename in the globals. Zope.browserpage
in turn uses t
19 matches
Mail list logo