#24769: "TypeError: unorderable types: str() > int()" with options['verbosity']
and
optparse
-------------------------------------+-------------------------------------
Reporter: blueyed | Owner: nobody
Type: Bug | Status: new
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by blueyed):
The problem in my case is not with django-configurations, but django-pdb.
It just got fixed there for Django 1.8, too:
https://github.com/tomchristie/django-
pdb/commit/90e6bec2d463ba215d75f196d398dc0d4c36dc00.
I can see that casting `verbosity` to `int` would be a behaviour change
(for the old parser). But when a command isn't using `option_list` that
would happen anyway (because it uses the new parser).
Therefore I still think that it's better for consistency to use `int` in
both cases.
--
Ticket URL: <https://code.djangoproject.com/ticket/24769#comment:4>
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.1610691dc3ca32e461dfb14463491f48%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
