Okay, squashing seems to have resolved this issue...
Seems a bit voodoo-ish, but it worked. Any suggestions for preventing this
in the future would be nice!
- Benjamin
On Wednesday, May 23, 2018 at 6:04:47 PM UTC-4, Benjamin Schollnick wrote:
>
>
> Not convinced yet this is a py2 versus py3 problem. First, you're running
>> different command flags (though, not sure it matters in this case).
>> Second, the
>> Django version for py3 can be different from the py2 version.
>>
>> From the backtrace it isn't clear though which app is causing this. If it
>> really is a py2 versus py3 issue, then I suspect that some migrations are
>> done
>> only for py3, though that is really bad practice.
>>
>
> Well, all migrations were made using makemigrations, so if there are any
> specific PY2 vs PY3 differences, I'm unaware of any...
>
> I've looked, and I don't have any clue on how to manually merge these
> because there are two 0018's, with different timestamps, and I don't want
> to break anything further.
>
> Would it be simpler to reset the migrations using the current database
> state as the base? Is there a way to do this? After all, it's working
> fine... with both versions of django.
> This seems to be more of a false positive then anything else?
>
> Or maybe squash the migrations? Is there a good guide to squashing?
>
> - Benjamin
>
>
>
--
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/c834f175-22a0-42c2-b8f2-69d00e2351d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
