Hi all,
I feel a bit embarrassed even asking this question, because it must have an
obvious answer... but when I do "./manage.py migrate -l" I see:
*admin*
[X] 0001_initial
*auth*
[X] 0001_initial
[X] 0002_customer_payingcustomer_projectmanager_staff
[X] 0003_auto_20141107_0803
*conte
Okay, I'm confused. I found it, in here:
/Users//.virtualenvs//lib/python2.7/site-
packages/django/contrib/auth/migrations
Why are app related migrations being stored in this location?
Cheers,
Ed
On Friday, 7 November 2014 09:50:47 UTC+1, Dr Ed wrote:
>
> Hi all,
>
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//.virtualenvs//lib/python2.7/site-
>> packages/django/contrib/auth/m
n app with existing
> migration data.
>
> Personally I'd say get rid of the migration data for that specific model
> and re-initialize, it's just not worth trying to figure out why the magic
> is broken (imho).
>
> Cal
>
> On Fri, Nov 7, 2014 at 8:50 AM, Dr Ed
se_meta.swapped))
TypeError: PayingCustomer cannot proxy the swapped model
'emailcustomuser.User'.
On Monday, 10 November 2014 09:35:29 UTC+1, Markus Holtermann wrote:
>
> Hey Ed,
>
> you certainly don't have to copy the virtualenv over to production!
>
> Can you share
5 matches
Mail list logo