#21523: Models DateField to_python method no longer supports mock dates.
-------------------------------------+-------------------------------------
Reporter: hugo@… | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.6
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: 0 => 1
Comment:
The latest [https://github.com/django/django/pull/2027 PR] uses the mock
library which I don't think we want. Not sure of the merits of the patch
and this idea is probably outside the scope of this ticket, but I wonder
if it might be worth vendoring `unittest.mock` from Python 3.3+ so we can
use it in our tests and have 2.7/3.2 support.
--
Ticket URL: <https://code.djangoproject.com/ticket/21523#comment:22>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/079.55e605f001aae1015676db84d07fd527%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
