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 serhiy.storchaka
Recipients Arfrever, georg.brandl, hynek, larry, r.david.murray, serhiy.storchaka
Date 2012-06-28.08:25:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340871903.2462.85.camel@raxxla>
In-reply-to <1340810611.7.0.212703457825.issue15202@psf.upfronthosting.co.za>
Content
Here is updated patches. The type of exception thrown when specifying
mutually exclusive arguments changed from ValueError to TypeError (in
accordance with the raised in similar conflicts exceptions). Slightly
modified documentation. Taken into account some of Larry's comments.

Only os.walk had followlinks and shutil.copytree had symlinks before
3.3. So these are the only functions preserved the old arguments.
os.fwalk and another five public functions from shutil got a new
argument only in 3.3, for them it just renamed (may be to make them
keyword-only?). Larry worrying, isn't it too late? But it would be
strange to have in 3.3 new and immediately obsolete arguments. Moreover
the support for the two arguments complicate and slow down the code. If
you postpone it to 3.4, there will not be another solution, but now we
can do less mess.
Files
File name Uploaded
followlinks-to-follow_symlinks-2.patch serhiy.storchaka, 2012-06-28.08:24:59
symlinks-to-follow_symlinks-2.patch serhiy.storchaka, 2012-06-28.08:25:05
History
Date User Action Args
2012-06-28 08:25:12serhiy.storchakasetrecipients: + serhiy.storchaka, georg.brandl, larry, Arfrever, r.david.murray, hynek
2012-06-28 08:25:11serhiy.storchakalinkissue15202 messages
2012-06-28 08:25:09serhiy.storchakacreate