Remove makemigrations.py, use Django instead

ryancausey · Mar 30, 2019 · 969228b · 969228b
1 parent 0a6c157
commit 969228b
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 103 deletions.
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
@@ -91,7 +91,7 @@ Ready to contribute? Here's how to set up `dj-stripe` for local development.
 
 7. If your changes altered the models you may need to generate Django migrations::
 
-    $ python makemigrations.py
+    $ DJSTRIPE_TEST_DB_VENDOR=sqlite ./manage.py makemigrations
 
 8. Commit your changes and push your branch to GitHub::
 

diff --git a/makemigrations.py b/makemigrations.py
diff --git a/tox.ini b/tox.ini
@@ -32,14 +32,12 @@ commands =
 	isort {toxinidir} -c
 
 [testenv:checkmigrations]
-commands = python makemigrations.py --check
-deps =
-	Django>=2.1,<2.2
+setenv = DJSTRIPE_TEST_DB_VENDOR=sqlite
+commands = ./manage.py makemigrations --check --dry-run
 
 [testenv:makemigrations]
-commands = python makemigrations.py
-deps =
-	Django>=2.1,<2.2
+setenv = DJSTRIPE_TEST_DB_VENDOR=sqlite
+commands = ./manage.py makemigrations
 
 [testenv:makemessages]
 whitelist_externals = mkdir