-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 18.09.2012 19:52, Christopher Nelson wrote:
> In 0.11 parse_date() seems to assume ISO format which isn't really an
> option for me.  users can configure their own format to match their
> data.

IIRC, Trac 0.12 does better, but sure, we even have 1.0 now.

If you need to stick to older Trac and if you're prepared to roll your
own code as (part of) a plugin, I recommend mxDateTime by eGenix.com [1]
to you. I happened to test it rather extensively while working on the
initial TracTicketsCustomTimeFields [2] implementation, that finally
made it into Trac after 1.0 in current development.

mxDateTime parser is really powerful and does even guess many typos
right, like semi-colon instead of colon for time stamps etc. But it
would be another external dependency, so it was not included in the
final changes for Trac by now.

Steffen Hoffmann


[1] http://www.egenix.com/products/python/mxBase/mxDateTime/doc/#DateTime
[2]
http://trac.edgewall.org/wiki/TracTicketsCustomTimeFields#Externalrelatedresources
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBYxAcACgkQ31DJeiZFuHfrewCg3qrKa8ljtwq7Ox3PGKX0mKGS
rQgAoKr28Otsfv2SyTA7IybferSoDDR7
=6ooi
-----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en.

Reply via email to