Message385565
> 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:17 | AdamGold | set | recipients:
+ AdamGold, lemburg, orsenthil, vstinner, eric.araujo, serhiy.storchaka, kj |
2021-01-23 22:22:17 | AdamGold | set | messageid: <1611440537.83.0.195208858638.issue42967@roundup.psfhosted.org> |
2021-01-23 22:22:17 | AdamGold | link | issue42967 messages |
2021-01-23 22:22:17 | AdamGold | create | |
|