#24540: Migrations will generate migrations a virtualenv
-------------------------------+--------------------
Reporter: rapilabs | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/24540>
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/051.ea428af2ed78d86dbd462ef9e6f29841%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
