#24769: Cast optparse verbosity argument to an integer for better backwards
compatibility
-------------------------------------+-------------------------------------
Reporter: blueyed | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Management | Version: 1.8
commands) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"76c526f80e43b0bf5199dfe33b1ce31e813fa2fb" 76c526f8]:
{{{
#!CommitTicketReference repository=""
revision="76c526f80e43b0bf5199dfe33b1ce31e813fa2fb"
[1.8.x] Fixed #24769 -- Cast optparse verbosity argument to an integer for
better backwards compatibility.
Using `BaseCommand.options_list` makes Django use the legacy optparse
parser, which does not set the verbosity attribute correctly. Now the
verbosity argument is always cast to int. Regression in 8568638 (#19973).
Initial report and patch from blueyed.
Backport of a0047c6242fd48068eb444e0a58f7a5d2bc1bcd3 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24769#comment:10>
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.1c4eab1e481787272c23640bfab21c8a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
