On Sunday, 9 November 2014 14:50:54 UTC+1, Daniel Roseman wrote: > > On Sunday, 9 November 2014 13:40:12 UTC, Dr Ed wrote: >> >> Okay, I'm confused. I found it, in here: >> /Users/XXXX/.virtualenvs/YYYY/lib/python2.7/site- >> packages/django/contrib/auth/migrations >> >> Why are app related migrations being stored in this location? >> >> Cheers, >> >> Ed >> > > What? Migrations related to Django's auth app are, not surprisingly, > stored alongside the code to that app. Why does this puzzle you? >
I guess it's because I thought that we could build migrations on the development machines and then update the project on the production machine and apply the migrations. Obviously this assumption was wrong and we need to distribute the entire .virtualenv too... Fine, if that's the way it is, that's the way it is, but to me this seems odd because everything else in there is just something you 'pip install' and I would not expect to mix 'user data' with 'installed packages' like this. It actually seems like an unfortunate design decision since it forces you - unless you try to be clever - to put django etc into the repository... we did this before and shifting to 1.7 was more painful as a result). Anyway, thanks for the reply! Cheers, Ed -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/62a63805-1677-4979-814c-44388666b870%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
