Opened 2 years ago

Last modified 2 years ago

#24901 new Cleanup/optimization

makemigrations should create empty migrations dir for any installed app without it

Reported by: Andriy Sokolovskiy Owned by: nobody
Component: Migrations Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Someday/Maybe
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Since django is not supporting apps without migrations in master, makemigrations should create empty migrations dir for any installed app without it, because it is ignoring applications if one use manage.py makemigrations without explicit providing of application name.

Change History (5)

comment:1 Changed 2 years ago by Tim Graham

Triage Stage: UnreviewedAccepted

But don't create a migrations directory unless the app has models.

comment:2 Changed 2 years ago by Markus Holtermann

We haven't really deprecated apps without migrations (no deprecation warning in either 1.7 or 1.8). Although we have documented it I'm not sure we can make the change for 1.9.

We also need to figure out a way of how to run the tests without explicit migrations. Once we're there I think we're ready for apps without migrations.

comment:3 Changed 2 years ago by Markus Holtermann

After a talk with Andrew at DjangoCon Europe:

Given #24481 and how that plays in with our test apps, we might reconsider dropping support for apps without migrations.

At some point (2.0 would be a good candidate to justify increasing the major version number ;) ) we should automatically create the migrations package.

comment:4 Changed 2 years ago by Andriy Sokolovskiy

After discussion with Markus, we should postpone this until the result of #24481

comment:5 Changed 2 years ago by Claude Paroz

Triage Stage: AcceptedSomeday/Maybe
Note: See TracTickets for help on using tickets.
Back to Top