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 vajrasky
Recipients georg.brandl, larry, richard, serhiy.storchaka, vajrasky
Date 2014-02-05.09:48:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391593691.28.0.731726492435.issue20517@psf.upfronthosting.co.za>
In-reply-to
Content
"But there are some errors that really need two filenames, like copy(), symlink(), and rename()."

I think *need* is too strong word in this case. I agree that two filenames is better than none. But I don't see anything wrong from omitting filenames in error messages for copy(), etc. If PHP and Perl are taking "omitting filenames" way, surely there is some merit in that way.

I am in if we are taking "two filenames" way just like Ruby does. It's just isn't it too rush for Python 3.4?
History
Date User Action Args
2014-02-05 09:48:11vajraskysetrecipients: + vajrasky, richard, georg.brandl, larry, serhiy.storchaka
2014-02-05 09:48:11vajraskysetmessageid: <1391593691.28.0.731726492435.issue20517@psf.upfronthosting.co.za>
2014-02-05 09:48:11vajraskylinkissue20517 messages
2014-02-05 09:48:11vajraskycreate