#30300: Allow migrations directories without __init__.py files
-------------------------------------+-------------------------------------
Reporter: Benjy Weinberger | Owner: Benjy
| Weinberger
Type: New feature | Status: assigned
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Benjy Weinberger):
Re the use case:
It seems unnecessary to insist on an empty `__init__.py` just to preserve
a (stale) check for `__file__`, when they are otherwise not required in
Python 3.
And https://code.djangoproject.com/ticket/29091 implies that this should
be allowed.
Context is: We've just finished migrating our codebase to all-python 3,
and nuked all our `__init__py` files. We are now upgrading to Django 2.1,
and noticing the various places where they're still de-facto required by
Django. This particular case seemed unnecessary and easy to fix.
--
Ticket URL: <https://code.djangoproject.com/ticket/30300#comment:7>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.af22320a1aec36d2e08825e9883a307a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
