Migrations test failure under Python 3

[Aymeric Augustin]

tests % ./runtests.py migrations
Testing against Django installed in '/Users/myk/Documents/dev/django/django'
Creating test database for alias 'default'...
Creating test database for alias 'other'...
.......................................................................................................................................s.........................F.......................s................................s..s...
======================================================================
FAIL: test_makemigrations_with_custom_name (migrations.test_commands.MakeMigrationsTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/myk/Documents/dev/django/tests/migrations/test_commands.py", line 542, in test_makemigrations_with_custom_name
    content = cmd("0002", migration_name_0002, "--empty")
  File "/Users/myk/Documents/dev/django/tests/migrations/test_commands.py", line 528, in cmd
    self.assertTrue(os.path.exists(migration_file))
AssertionError: False is not true

----------------------------------------------------------------------
Ran 225 tests in 2.072s

FAILED (failures=1, skipped=4)
Destroying test database for alias 'default'...
Destroying test database for alias 'other'...

This happens with Python 3.4.2 from MacPorts on OS X, with the current versions of everything.

A quick investigation shows that the test creates a migration called 0001_my_custom_migration.py instead of 0002_my_custom_migration.py.

[Aymeric Augustin]

The error occurs since 1435cfbe8dbd85c17c9a25af99f910c407dfa9bd where this test was added.

[Tim Graham]

Duplicate of #23850 (OS X seems to be the common thread to the two people that have run into this).