USE_L10N and microseconds

[anonymous]

Hello,

I have a problem when I'm using "USE_L10N = True" and "DateTimeField" eg in auth.User model.
I can't save the form, because it contains field "last_login" with the time including microseconds. These are defined in DATETIME_INPUT_FORMATS, but only in global_settings.py, not in the formats directory.

django.conf.global_settings:

DATETIME_INPUT_FORMATS = (
    '%Y-%m-%d %H:%M:%S',
    '%Y-%m-%d %H:%M:%S.%f',  # OKAY
    ...
}

django.conf.locale.en.formats:

DATETIME_INPUT_FORMATS = (
    '%d.%m.%Y %H:%M:%S',
    '%d.%m.%Y %H:%M',       # '25.10.2006 14:30'
    '%d.%m.%Y',             # '25.10.2006'
    '%Y-%m-%d %H:%M:%S',    # '2006-10-25 14:30:59'
    '%Y-%m-%d %H:%M',       # '2006-10-25 14:30'
    '%Y-%m-%d',             # '2006-10-25'
)

Here is ".%f" missing.

Now I have my own formats directory, where I add the ".%f" to the locales ​what needs my application. But I think it's not very elegant solution.

Thank you
Ross

[Aymeric Augustin]

This problem probably affects most of the 33 locales that define their own DATETIME_INPUT_FORMATS.

Note that %f only exists since Python 2.6, but there's a hack in django.forms.fields.BaseTemporalField.to_python to support format strings ending in %f.

[Thomas Güttler]

Django 1.5 will drop support for Python 2.5. This means that the current development version of django can safely use %f to parse microseconds.

[Claude Paroz <claude@…>]

In 21722702c8ca85895d245ce2967e7336a168585d:

Fixed #16888 -- Added microseconds in localized input formats