Issue with Django migrate - fine with 2.7x python, but error with 3.6.4?

I've an established Django application that I'm finishing up a new release for, and I'm working on solving any last python 3 issues.

I'm confused at what's happening here though...

Run manage.py migrations under v2.7x:

nerv:quickbbs Benjamin$ manage.py migrate --run-syncdb

Running on nerv.local

Operations to perform:

  Synchronize unmigrated apps: _humanize, allauth, bootstrap3, django_jinja, grappelli, humanize, messages, staticfiles

  Apply all migrations: account, admin, auth, contenttypes, quickbbs, sessions, sites, socialaccount

Synchronizing apps without migrations:

  Creating tables...

    Running deferred SQL...

Running migrations:

  No migrations to apply.

Run manage.py migrations under v3.65.

(quickbbs) nerv:quickbbs Benjamin$ python3 manage.py migrate

Running on nerv.local

CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0019_auto_20171108_0155, 0044_auto_20180519_1914 in quickbbs).

To fix them run 'python manage.py makemigrations --merge'

(quickbbs) nerv:quickbbs Benjamin$ 

Okay?  

Manage.py makemigrations --merge

(quickbbs) nerv:quickbbs Benjamin$ python3 manage.py makemigrations --merge

Running on nerv.local

Traceback (most recent call last):

  File "manage.py", line 10, in <module>

    execute_from_command_line(sys.argv)

  File "/Users/Benjamin/django-py3/quickbbs/lib/python3.6/site-packages/django/core/management/__init__.py", line 371, in execute_from_command_line

    utility.execute()

  File "/Users/Benjamin/django-py3/quickbbs/lib/python3.6/site-packages/django/core/management/__init__.py", line 365, in execute

    self.fetch_command(subcommand).run_from_argv(self.argv)

  File "/Users/Benjamin/django-py3/quickbbs/lib/python3.6/site-packages/django/core/management/base.py", line 288, in run_from_argv

    self.execute(*args, **cmd_options)

  File "/Users/Benjamin/django-py3/quickbbs/lib/python3.6/site-packages/django/core/management/base.py", line 335, in execute

    output = self.handle(*args, **options)

  File "/Users/Benjamin/django-py3/quickbbs/lib/python3.6/site-packages/django/core/management/commands/makemigrations.py", line 124, in handle

    return self.handle_merge(loader, conflicts)

  File "/Users/Benjamin/django-py3/quickbbs/lib/python3.6/site-packages/django/core/management/commands/makemigrations.py", line 251, in handle_merge

    raise ValueError("Could not find common ancestor of %s" % migration_names)

ValueError: Could not find common ancestor of {'0019_auto_20171108_0155', '0044_auto_20180519_1914'}

I have found several other people reporting similar issues, but I don't see any best practices to prevent this, and no straight forward explanations on how to fix this?

But my big question is why is this happening with Py3, and not Py2?  

            - 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+unsubscribe@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/2fca9e9d-09a2-4d6e-b9ba-578db6bbf404%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.