➜

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 Steven.Barker
Recipients Steven.Barker, chris.jerdonek, fdrake, georg.brandl, goatsofmendez, pvrijlandt, rhettinger, sandro.tosi
Date 2014-04-21.08:30:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398069017.38.0.801601615296.issue1234674@psf.upfronthosting.co.za>
In-reply-to
Content 
A recent Stack Overflow question (http://stackoverflow.com/q/23192359/1405065) relates to this bug. The questioner was surprised that filecmp.cmp is much slower than usual for certain large files, despite the "shallow" parameter being True.

It is pretty clear to me that the behavior of filecmp.cmp does not match its docstring with respect to "shallow". Either the docstring should be updated to match the existing behavior, or (more likely?) the behavior should change to match the docs.
History
Date User Action Args
2014-04-21 08:30:17Steven.Barkersetrecipients: + Steven.Barker, fdrake, georg.brandl, rhettinger, pvrijlandt, goatsofmendez, sandro.tosi, chris.jerdonek
2014-04-21 08:30:17Steven.Barkersetmessageid: <1398069017.38.0.801601615296.issue1234674@psf.upfronthosting.co.za>
2014-04-21 08:30:17Steven.Barkerlinkissue1234674 messages
2014-04-21 08:30:16Steven.Barkercreate