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 AdamGold
Recipients AdamGold, eric.araujo, kj, lemburg, orsenthil, serhiy.storchaka, vstinner
Date 2021-01-23.22:22:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I _didn't_ change the default - it will allow both '&' and ';' still. Eric showed a link above that still uses semicolon. So I feel that it's strange to break backwards compatibility in a patch update. Maybe we can make just '&' the default in Python 3.10, while backporting the ability to specify separators to older versions so it's up to users?

I like this implementation. I definitely think we should not break backwards compatibility and only change the default in Python 3.10.
Date User Action Args
2021-01-23 22:22:17AdamGoldsetrecipients: + AdamGold, lemburg, orsenthil, vstinner, eric.araujo, serhiy.storchaka, kj
2021-01-23 22:22:17AdamGoldsetmessageid: <>
2021-01-23 22:22:17AdamGoldlinkissue42967 messages
2021-01-23 22:22:17AdamGoldcreate