ing git branches before. We have pyc files turned off
> in dev to stop this.
>
> Andrew
> On 11 Feb 2015 21:05, "abhillman" >
> wrote:
>
>> I have gotten bitten by lingering bytecode in migrations on several
>> occasions. Steps to reproduce are a little
have pyc files turned off
in dev to stop this.
Andrew
On 11 Feb 2015 21:05, "abhillman" wrote:
> I have gotten bitten by lingering bytecode in migrations on several
> occasions. Steps to reproduce are a little bit complex, but here is an
> rough example:
>
> Loca
llman > wrote:
>
>> I have gotten bitten by lingering bytecode in migrations on several
>> occasions. Steps to reproduce are a little bit complex, but here is an
>> rough example:
>>
>> Local Box:
>> — have *.pyc rule in .gitignore
>> — create some
;
>> I have gotten bitten by lingering bytecode in migrations on several
>> occasions. Steps to reproduce are a little bit complex, but here is an
>> rough example:
>>
>> Local Box:
>> — have *.pyc rule in .gitignore
>> — create some migrations
>> —
Hah. Check out this ticket :) https://code.djangoproject.com/ticket/23406
On Wed, Feb 11, 2015 at 4:04 PM, abhillman wrote:
> I have gotten bitten by lingering bytecode in migrations on several
> occasions. Steps to reproduce are a little bit complex, but here is an
> rough example:
I have gotten bitten by lingering bytecode in migrations on several
occasions. Steps to reproduce are a little bit complex, but here is an
rough example:
Local Box:
— have *.pyc rule in .gitignore
— create some migrations
— commit them
Server Box:
— pull repository
— execute migrations
Local
