➜

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 Mark Borgerding
Recipients Anders.Hovmöller, Mark Borgerding, ezio.melotti, mrabarnett, mu_mind, serhiy.storchaka
Date 2020-04-16.12:57:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content 
So third-party code was knowingly broken to satisfy an aesthetic notion that substitution should be more like iteration.

Would not a FutureWarning have been a kinder way to stage this implementation?

A foolish consistency, indeed.
History
Date User Action Args
2020-04-16 12:57:37Mark Borgerdingsetrecipients: + Mark Borgerding, ezio.melotti, mrabarnett, mu_mind, serhiy.storchaka, Anders.Hovmöller
2020-04-16 12:57:37Mark Borgerdingsetmessageid: <[email protected]>
2020-04-16 12:57:37Mark Borgerdinglinkissue32308 messages
2020-04-16 12:57:37Mark Borgerdingcreate