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 r.david.murray
Recipients Arfrever, docs@python, eric.snow, r.david.murray, shai
Date 2013-02-03.14:48:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359902936.5.0.667688975894.issue17108@psf.upfronthosting.co.za>
In-reply-to
Content
Yes.  Imagine you have a deployed application, and there happens to be an xx.py file that is masked by a package in it.  You upgrade from pythonX.Y.Z to X.Y.Z+1, and your application is suddenly throwing an error.  Yes it is easy to fix, but we prefer not to break things that way.

Now, could we throw an error in Python 3.4?  It could be discussed, at least.
History
Date User Action Args
2013-02-03 14:48:56r.david.murraysetrecipients: + r.david.murray, Arfrever, docs@python, eric.snow, shai
2013-02-03 14:48:56r.david.murraysetmessageid: <1359902936.5.0.667688975894.issue17108@psf.upfronthosting.co.za>
2013-02-03 14:48:56r.david.murraylinkissue17108 messages
2013-02-03 14:48:56r.david.murraycreate