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 lemburg
Recipients
Date 2001-11-30.09:36:20
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=38388

I disagree: any change which could potentially blow up existing programs should at least be mentioned somewhere 
in the docs, be it the NEWS file, the release page on python.org or (thanks to the great work of Andrew Kuchling) 
the "What's new in Python x.x" docs.

This is simply needed due to the very dynamic way Python works: there's no way to test all paths through a 
program if you want to port it from one Python version to the next, so we'll have to be very careful about these 
changes even if they are clearly bug fixes.

In the mentioned case, I'd say that the programmer was at fault, though: it's so much easier to test a path for being 
a directory than to rely on some obscure method return value and also much safer !
History
Date User Action Args
2007-08-23 13:57:44adminlinkissue487277 messages
2007-08-23 13:57:44admincreate