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 mjs0
Recipients Trundle, daniel.urban, docs@python, eric.araujo, jonathan.hartley, mjs0, rhettinger, terry.reedy
Date 2011-04-09.09:04:49
SpamBayes Score 6.4414853e-06
Marked as misclassified No
Message-id <>
Thanks to everyone for the explanations.

I was hoping for behaviour along the lines of Python 2 (certainly not artificially blocking more cases in the name of consistency) but it doesn't look like that's going to happen. I think this is one slight and rare area where Python 3 has taken a step backwards when compared to Python 2 but I can live with it. As noted there's other ways to achieve the same thing.

The new Python 3 behaviour seems odd to me but perhaps that's just a bias due to many years of development with Python 2. A documentation improvement would help. 

Date User Action Args
2011-04-09 09:04:50mjs0setrecipients: + mjs0, rhettinger, terry.reedy, eric.araujo, Trundle, jonathan.hartley, daniel.urban, docs@python
2011-04-09 09:04:50mjs0setmessageid: <>
2011-04-09 09:04:49mjs0linkissue11796 messages
2011-04-09 09:04:49mjs0create