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 steve.dower
Recipients Joel Croteau, christian.heimes, docs@python, eric.smith, gc2, lukasz.langa, ncoghlan, ned.deily, pmoody, serhiy.storchaka, steve.dower, vstinner
Date 2021-04-06.14:29:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The important quote from the linked issue seems to be:

> Our new separator= parameter does not allow one to achieve the previous behavior if mixing and matching & And ; was intended to be allowed, as it is a single separator rather than a set of separators.

So arguably, we added _the wrong_ parameter in that case, because it only allowed choosing between behaviours not including the "bad" behaviour. We should've added one that was "give me back the previous behaviour".

In this case, having it off by default goes further to prevent breakage, and I wouldn't be opposed to a process level opt-in (e.g. a module-level flag), so that _applications_ have a way to force their dependencies to use the safer behaviour without needing to patch them. Similarly, a process level opt-out also seems good enough if we were to have it on by default.
Date User Action Args
2021-04-06 14:29:48steve.dowersetrecipients: + steve.dower, ncoghlan, vstinner, eric.smith, christian.heimes, ned.deily, pmoody, docs@python, lukasz.langa, serhiy.storchaka, Joel Croteau, gc2
2021-04-06 14:29:48steve.dowersetmessageid: <>
2021-04-06 14:29:48steve.dowerlinkissue36384 messages
2021-04-06 14:29:47steve.dowercreate