Nevermind. I later found that I could not call HTTPConnection from my
python script in Zope and ended up going straight to running it in
python 2.3.
Jamie
On 12/28/05, Jamie O'Keefe [EMAIL PROTECTED] wrote:
I am trying to get the latest time in a Python Script.
I declare:
from
Thanks Andreas and Jens for the helpful tip.
Jamie
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
Chris Withers wrote:
Just a note: I don't think mixing in persistance is needed.
Hmm... how so? I've always thought it quite nice that when, for example,
you store the modification time of an object in a DateTime, you can
safely update it without worrying about the whole object having to be
[ Florent Guillaume wrote:]
Jürgen Herrmann wrote:
recently i came up here with the intention to fix DateTime#strftime().
while trying this, i had to dig deeper and deeper into the
implementation
of DateTime and especially the timezone and daylight saving stuff.
to be honest, it's
On 11/22/05, Jürgen Herrmann [EMAIL PROTECTED] wrote:
do we REALLY need dates 1900 / 2036 ?
Yes.
using unix timestamps for
storage and as the base for all conversions would make things a lot
easier!
datetimes are picklable, so if you are going to change how they are
stored (which may not be
[ Lennart Regebro wrote:]
On 11/22/05, Jürgen Herrmann [EMAIL PROTECTED] wrote:
do we REALLY need dates 1900 / 2036 ?
Yes.
using unix timestamps for
storage and as the base for all conversions would make things a lot
easier!
datetimes are picklable, so if you are going to change how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jürgen Herrmann wrote:
[ Florent Guillaume wrote:]
Jürgen Herrmann wrote:
recently i came up here with the intention to fix DateTime#strftime().
while trying this, i had to dig deeper and deeper into the
implementation
of DateTime and especially
On 11/22/05, Jürgen Herrmann [EMAIL PROTECTED] wrote:
i'll surely change the storage format, when rewriting it!
So you plan on having some version marker, or so, which
tells which storage format is used?
//Curious.
--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management
[ Lennart Regebro wrote:]
On 11/22/05, Jürgen Herrmann [EMAIL PROTECTED] wrote:
i'll surely change the storage format, when rewriting it!
So you plan on having some version marker, or so, which
tells which storage format is used?
//Curious.
basicall i thought about having a dateime
At Tuesday 22/11/2005 05:50, Jürgen Herrmann wrote:
one more question (to the public!):
do we REALLY need dates 1900 / 2036 ? using unix timestamps for
storage and as the base for all conversions would make things a lot
easier!
Sure. What about birthdays of aged people? Long running
On Nov 22, 2005, at 11:27 AM, Gabriel Genellina wrote:
At Tuesday 22/11/2005 05:50, Jürgen Herrmann wrote:
one more question (to the public!):
do we REALLY need dates 1900 / 2036 ? using unix timestamps for
storage and as the base for all conversions would make things a lot
easier!
Sure.
Jürgen Herrmann wrote:
recently i came up here with the intention to fix DateTime#strftime().
while trying this, i had to dig deeper and deeper into the implementation
of DateTime and especially the timezone and daylight saving stuff.
to be honest, it's completely hacked together :(
zope 2.7.8's DateTime::strftime() looks like this:
def strftime(self, format):
# Format the date/time using the *local timezone representation*.
return strftime(format, safelocaltime(self.timeTime()))
it seems that my assumption about strftime's behaviour was incorrect.
why do we have time
Jürgen Herrmann wrote at 2005-11-9 13:38 +0100:
zope 2.7.8's DateTime::strftime() looks like this:
def strftime(self, format):
# Format the date/time using the *local timezone representation*.
return strftime(format, safelocaltime(self.timeTime()))
it seems that my assumption about
[ Dieter Maurer wrote:]
Jürgen Herrmann wrote at 2005-11-9 13:38 +0100:
zope 2.7.8's DateTime::strftime() looks like this:
def strftime(self, format):
# Format the date/time using the *local timezone representation*.
return strftime(format, safelocaltime(self.timeTime()))
it seems that my
Thanks Lupa.
I have tracked it down and created a patch which fixes the problem in
general. Seems the ISO 8601 implementation had some warts. We are
testing the patch now. When I am sure it's OK I'll submit it to the
Collector with an URGENT tag. I'll also send you a copy.
I suspect
On Thu, Apr 07, 2005 at 11:22:39AM -0400, Paul Winkler wrote:
Maybe this is relevant:
http://www.zope.org/Collectors/CMF/325
... crap, I never merged the fix.
OK, now this is merged to the trunk and CMF-1_5-branch.
--
Paul Winkler
http://www.slinkp.com
Max M wrote:
I have a product where I convert some external datetimes to zope
DateTime() objects. I save them as UTC as zopes DateTime does by default.
But when these are rendered, the time is offset by two hours.
Ok. I was unclear here.
I convert from datetime objects (python) to DateTime
Max M wrote:
When I convert to DateTime objects, they are saved as 9:00 Universal.
So that is correct too.
Ok. Turned out that I have misunderstood zopes DateTime().
It saves in UTC, but it still needs a timezone.
So converting datetime objects to the local timezone and then converting
to
On Thu, Apr 07, 2005 at 02:44:38PM +0200, Max M wrote:
Max M wrote:
When I convert to DateTime objects, they are saved as 9:00 Universal.
So that is correct too.
Ok. Turned out that I have misunderstood zopes DateTime().
It saves in UTC, but it still needs a timezone.
So converting
Jerome Alet wrote:
On Fri, 10 Nov 2000, Chris Withers wrote:
mxDateTime is _not_ the DateTime in Zope. If only it was
It's voting season, so I vote +10 for this one.
bye,
I'll second that
+10
kapil
___
Zope maillist - [EMAIL
These aren't really hosting related so I'm moving this to the
[EMAIL PROTECTED] list...
Thiebaut CHAMPENIER wrote:
The official home page for this module is
http://starship.python.net/~lemburg/mxDateTime.html (not responding rigth
now)
IIRC, starship is down 'cos the Python team are moving
On Fri, 10 Nov 2000, Chris Withers wrote:
mxDateTime is _not_ the DateTime in Zope. If only it was
It's voting season, so I vote +10 for this one.
bye,
Jerome ALET - [EMAIL PROTECTED] - http://cortex.unice.fr/~jerome
Fac de Medecine de Nicehttp://wwwmed.unice.fr
Tel: (+33) 4 93
23 matches
Mail list logo
