Opened 10 years ago
Closed 10 years ago
#24540 closed Uncategorized (invalid)
Migrations will generate migrations in a virtualenv
| Reported by: | David Sanders | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 1.7 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Recently upgrade from 1.7 to 1.8 and makemigrations generated a couple of migrations for django-allauth in the app's migrations folder inside the virtualenv.
It would be handy to have these new migrations created inside my project's folder so they can be committed to version control and not be lost if I blow my virtualenv away.
I'm not sure how this would work as I've tried manually moving them to my project but am unsure how to set the dependency back to the initial app migration, but this at least should be highlighted as a potential issue.
Change History (2)
comment:1 by , 10 years ago
| Summary: | Migrations will generate migrations a virtualenv → Migrations will generate migrations in a virtualenv |
|---|
comment:2 by , 10 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
You can use the
MIGRATION_MODULESsetting to create migrations inside your project.