Max Battcher ha scritto:
I just completed transferring the logic to marshall from ``darcs changes
--xml-output -s`` into my Patch model class. In Darcsweb this is the
BuildPatchList class that creates Darcsweb Patches, which are very
simple python object. (In my case the class is named ChangeLogHandler
and it marshals Patch objects, which are derived from
django.db.models.Model, which gives me out of the box relational
database serialization (ORM).)
This sounds very interesting! I'll jump to google :)
In testing this class I'm having a problem in trying to parse the
local_date field of a patch tag. If I run darcs from my command line in
the field I get the time zone "Eastern Standard Zone", but for some
reason when darcs is called via the python script I appear to be getting
the time zone "Ame", which of course isn't parsing as a time zone on the
Python side.
Any ideas on what might be causing this?
Most probably, the environment under which the two executions run is not
the same, in particular regarding the LANG and TZ variables. In
trac-darcs (and tailor) I usually force them, simply by "TZ=UTC LANG=C
darcs ..."
hth, ciao,
lele.
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
