Sidnei appears to be broken :-(
Any idea how to reach him?
cheers,
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk
---BeginMessage---
This message was created automatically by mail delivery software (Exim).
A message that you sent
Hello,
today I downloaded the Zope-3.1.0c2 release candidate and played a little
bit with it.
I noticed that the bin/mkzeoinstance script is broken and returns
Traceback (most recent call last):
File ./mkzeoinstance, line 40, in ?
from ZEO.mkzeoinst import ZEOInstanceBuilder
I found no
On Tue, Sep 06, 2005 at 09:08:02AM +0100, Chris Withers wrote:
| Sidnei appears to be broken :-(
|
| Any idea how to reach him?
Odd. I've been receiving email normally.
| Sidnei da Silva wrote:
|
| That smells to me like we need a mime-type negotiator or something,
| pretty much like we
On Sep 6, 2005, at 3:39 PM, Fred Drake wrote:
On 9/6/05, Tim Peters [EMAIL PROTECTED] wrote:
Not sure when this started to fail -- recently:
The `pytz` was recently updated to use a newer version of the Olson
timezone database. This failure appears to be fallout from that.
Not sure
[Gary Poster]
This is probably what we will need to do, but since the failing tests
were bogus to begin with it may be a case of incremental
improvement. This is definitely a problem, though, that we should
resolve one way or another.
It's also worth noting that the i18n code currently
Hi everyone,
I just learned that we need to have a Zope 3.1 RC 3 release. I know that some
people found bugs, so please check in fixes into the branch in the next
couple of days.
Gary, does the pytz problem affect the branch?
Regards,
Stephan
--
Stephan Richter
CBU Physics Chemistry (B.S.)
On Sep 6, 2005, at 4:29 PM, Stephan Richter wrote:
Hi everyone,
I just learned that we need to have a Zope 3.1 RC 3 release. I know
that some
people found bugs, so please check in fixes into the branch in the
next
couple of days.
Gary, does the pytz problem affect the branch?
Yes.
On Sep 6, 2005, at 1:08 AM, Stuart Bishop wrote:
...
So the only thing I think needs changing here is the documentation
suggesting returning maxint from __len__.
...
While I think there is agreement on this, have we settled in on a
solution? Raising NotImplementedError or some other error
On Sep 1, 2005, at 6:05 AM, Adam Groszer wrote:
Dear Gary,
Maybe not too late, I have here one more thing to look at:
Hi Adam. Unfortunately, we did not get to your bug issues.
If you have not already, please do put your issues in the Zope 3
collector
The Buildbot has detected a failed build of Zope3 trunk 2.4 zc1.
Buildbot URL: http://buildbot.zope.org/
Build Reason: The web-page 'force build' button was pressed by 'Benji': Test
Windows Slave
Build Source Stamp: None
Blamelist:
BUILD FAILED: failed svn
sincerely,
-The Buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 zc1.
Buildbot URL: http://buildbot.zope.org/
Build Reason: The web-page 'force build' button was pressed by 'Benji': Test
buildbot on Windows
Build Source Stamp: None
Blamelist:
BUILD FAILED: failed svn
sincerely,
-The Buildbot
On Sep 6, 2005, at 10:27 PM, Fred Drake wrote:
On 9/6/05, Stuart Bishop [EMAIL PROTECTED] wrote:
Is this something I need to be aware of? Because I'm not ;)
This test in the Zope 3 trunk is failing:
I talked with Stuart on IRC. It appears to be a symptom of using
pytz incorrectly in
On 9/6/05, Gary Poster [EMAIL PROTECTED] wrote:
I talked with Stuart on IRC. It appears to be a symptom of using
pytz incorrectly in i18n (it needs to localize, as per the pytz
README). He said he would look into the i18n package and try to
address.
Excellent! Thanks for the update.
Gary Poster wrote:
On Sep 6, 2005, at 3:39 PM, Fred Drake wrote:
This also brings up a question: How should we deal with timezones for
historic dates? The specific set of rules that apply to a given date
or datetime value have to be determined based on both the date and the
timezone
14 matches
Mail list logo
