This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jssfr
Recipients bethard, eric.araujo, jssfr, maker, martin.panter, paul.j3, r.david.murray, rhettinger, shihai1991
Date 2019-10-03.16:19:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Since I have been adversely affected by this bug ([1]), I looked at the patches.

I combined issue14364.test.patch (which adds test cases for --foo=--) and dbldash.patch in my local working tree and that seems to resolve the issue (tests pass if and only if I apply dbldash.patch and my reproducer from [1]) passes too).

The patches do not contain any type of metainformation, so I’m not comfortable with submitting this as a PR. I am also not at all familiar with the process of managing the changelog etc.

This should serve as a confirmation that this issue can be resolved with the patches. Someone more familiar than me with the process could take up the task to get this merged.

Note: As you can see in [1], this issue has already caused data loss.

Date User Action Args
2019-10-03 16:19:59jssfrsetrecipients: + jssfr, rhettinger, bethard, eric.araujo, r.david.murray, maker, martin.panter, paul.j3, shihai1991
2019-10-03 16:19:59jssfrsetmessageid: <>
2019-10-03 16:19:59jssfrlinkissue14364 messages
2019-10-03 16:19:59jssfrcreate