#23970: Migrations test failure under Python 3
--------------------------------------+------------------------
               Reporter:  aaugustin   |          Owner:  nobody
                   Type:  Bug         |         Status:  new
              Component:  Migrations  |        Version:  master
               Severity:  Normal      |       Keywords:
           Triage Stage:  Unreviewed  |      Has patch:  0
    Needs documentation:  0           |    Needs tests:  0
Patch needs improvement:  0           |  Easy pickings:  0
                  UI/UX:  0           |
--------------------------------------+------------------------
 {{{
 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`.

--
Ticket URL: <https://code.djangoproject.com/ticket/23970>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.84e79aa4ee8a18a65526cb8be9e45b4b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to