#24579: With argparse on Python 3, the migrate management command fails when no
database provided
-------------------------------+--------------------------------------
Reporter: bkonkle | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by bkonkle):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Hmm, argparse actually shouldn't be resolving this to `None`, because the
--database option has a default set: `default=DEFAULT_DB_ALIAS`, which is
'default'.
--
Ticket URL: <https://code.djangoproject.com/ticket/24579#comment:1>
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/065.63fd3bf08bed85df62b016d30ba656cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
