#35825: Document None return type for dateparse functions
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: dev
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* resolution: => invalid
* status: assigned => closed
Comment:
I think it does state it at the top, the 3rd bullet point?
{{{
The functions defined in this module share the following properties:
- They accept strings in ISO 8601 date/time formats (or some close
alternatives) and return objects from the corresponding classes in
Python's
:mod:`datetime` module.
- They raise :exc:`ValueError` if their input is well formatted but isn't
a
valid date or time.
- They return ``None`` if it isn't well formatted at all.
- They accept up to picosecond resolution in input, but they truncate it
to
microseconds, since that's what Python supports.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35825#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070192757a20af-4f748768-9b29-4361-b490-ea23fe2fd728-000000%40eu-central-1.amazonses.com.
