Philipp von Weitershausen wrote:
Thomas Lotze wrote:
I just realized that Zope 2.11.0-a1 contains zope.app.fssync but not
zope.fssync. This doesn't make much sense to me given that the former
depends on the latter. Is there a good reason for it, should both be
included, or none of the two?
On 10/4/07, Andreas Jung [EMAIL PROTECTED] wrote:
I would not care much about dropping the support for weird timezone names
without further notice as long as their is an easy way for people
migrating their code e.g. by specifying a proper tz name.
Lets not break too much, and instead
Summary of messages to the zope-tests list.
Period Wed Oct 3 12:00:00 2007 UTC to Thu Oct 4 12:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Wed Oct 3 20:51:44 EDT 2007
Not sure what Zope 3 is using these days (haven't checked), but Zope 2
had a 'Signals' package that handled signaling events on both Windows
and *nix in a somewhat transparent way. Has anyone thought of
packaging that as an egg?
--
Sidnei da Silva
Enfold Systems
Any objections?
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
Jim
--
Jim Fulton
Zope Corporation
___
Zope-Dev maillist - Zope-Dev@zope.org
There's work going on to create a second version of WSGI. Last time,
we didn't pay much attention until WSGI was a done deal. This time,
I think it would be better if we were involved earlier.
Unfortunately, I don't have time to pay attention. Does anyone else?
Jim
P.S. I'd lobe to
Jim Fulton wrote:
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
+100
--
http://worldcookery.com -- Professional Zope documentation and training
___
Zope-Dev maillist - Zope-Dev@zope.org
Andreas Jung wrote:
I would not care much about dropping the support for weird timezone names
without further notice as long as their is an easy way for people
migrating their code e.g. by specifying a proper tz name.
I should clarify that they are mostly abbreviations.
I also agree with
On Thu, 2007-10-04 at 09:57 -0400, Jim Fulton wrote:
Any objections?
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
+1
Seems reasonable. The archives for the retired list will remain in
place, right?
- Michael R. Bernstein
Hi,
I wanted to let folks know that I've created the amos-datetime-pytz
branch with my changes.
Please let me know when/if you'd like me to merge this to the trunk.
Of course I'm also happy to receive any criticism or comments on the changes.
Thanks!
-Amos
--On 4. Oktober 2007 12:52:24 -0400 Amos Latteier [EMAIL PROTECTED] wrote:
Hi,
I wanted to let folks know that I've created the amos-datetime-pytz
branch with my changes.
Please let me know when/if you'd like me to merge this to the trunk.
Any chance getting rid of the _zlst and _zmap
On Oct 4, 2007, at 5:42 AM, Lennart Regebro wrote:
...
Being on a Grok sprint right now I don't have time to do that this
week. Can I be given a deadline? I like deadlines. :-)
Just to put this in perspective. People in the US will be affected
again by the existing bug starting the last
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amos Latteier wrote:
Andreas Jung wrote:
I would not care much about dropping the support for weird timezone names
without further notice as long as their is an easy way for people
migrating their code e.g. by specifying a proper tz name.
I
On Thursday 04 October 2007 09:57, Jim Fulton wrote:
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
-1. I do not follow zope-dev at all and the traffic is pretty high there.
Regards,
Stephan
--
Stephan Richter
CBU Physics
--On 4. Oktober 2007 15:15:40 -0400 Stephan Richter
[EMAIL PROTECTED] wrote:
On Thursday 04 October 2007 09:57, Jim Fulton wrote:
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
-1. I do not follow zope-dev at all and the
I've been working on this too today (well datetime handling anyway).
Please see my patch at https://bugs.launchpad.net/zope2/+bug/149060
Laurence
Amos Latteier wrote:
Hi,
I wanted to let folks know that I've created the amos-datetime-pytz
branch with my changes.
Please let me know when/if
Stephan Richter wrote:
On Thursday 04 October 2007 09:57, Jim Fulton wrote:
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
-1. I do not follow zope-dev at all and the traffic is pretty high there.
But pretty low there, if you take
Stephan Richter wrote:
On Thursday 04 October 2007 09:57, Jim Fulton wrote:
This would basically involve retiring the zope3-dev list and moving
zope3 developers to the zope-dev list.
-1. I do not follow zope-dev at all and the traffic is pretty high there.
If you do not follow it at all,
18 matches
Mail list logo
