Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1161894[details]
reproducer
Description of problem:
There was probably a change in behaviour of python argparse in upstream. RHEL versions currently do not behave the same way, which is possibly causing problems during inclusion of upstreams into RHEL.
In RHEL versions, parser.set_defaults takes precedence to subparser.set_defaults. This priority is reversed in newer versions.
Version-Release number of selected component (if applicable):
python-2.7.5
How reproducible:
reliably
Steps to Reproduce:
1. python argparse_defaults.py a
2. see output
Actual results:
In RHEL, outputs "parser"
Expected results:
In newer versions of python, for example 2.7.10, or 3.4.3, outputs "subparser_a"
Comment 3Petr Viktorin (pviktori)
2016-06-21 12:16:09 UTC
This would change behavior of existing software that uses argparse, and there are reports of such brokennes in the upstream issue. How can we ensure there will be no regressions?
Unfortunately, I fear this will need to be handled in new software that is getting into RHEL.
Created attachment 1161894 [details] reproducer Description of problem: There was probably a change in behaviour of python argparse in upstream. RHEL versions currently do not behave the same way, which is possibly causing problems during inclusion of upstreams into RHEL. In RHEL versions, parser.set_defaults takes precedence to subparser.set_defaults. This priority is reversed in newer versions. Version-Release number of selected component (if applicable): python-2.7.5 How reproducible: reliably Steps to Reproduce: 1. python argparse_defaults.py a 2. see output Actual results: In RHEL, outputs "parser" Expected results: In newer versions of python, for example 2.7.10, or 3.4.3, outputs "subparser_a"