#33200: Consider "hiding" datetime/zoneinfo imports in django.utils.timezone
-------------------------------------+-------------------------------------
Reporter: Jaap Roes | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Utilities | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: timezone datetime | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
Comment:
> I'm aware Django (or any Python project) is full of potential incorrect
import opportunities. But this one seems to pop up fairly regularly in my
experience and when combined with incorrect assumptions about what is
being imported can be a root cause of subtle bugs.
Thanks for this suggestion, however `__all__` is already defined in the
`django.utils.timezone` and none of it is documented. IMO there is nothing
we can do anything to stop folks from making false assumptions, adding
underscores won't help.
''"wontfixed"'' generally not only in this case. There are many modules
where we may receive similar requests, e.g. `from django.utils.archive
import tarfile`.
--
Ticket URL: <https://code.djangoproject.com/ticket/33200#comment:1>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.333d478c0a4fae289312e7599b5355e8%40djangoproject.com.
