Éric Araujo <mer...@netwok.org> added the comment: > The remaining test > (test_command_install_data.InstallDataTestCase.test_simple_run) was > broken in r1152. This looks like a local revision number, which has no meaning outside of one specific repository. What is the changeset identifier? (see http://hgbook.red-bean.com/read/a-tour-of-mercurial-the-basics.html#id345536)
Thanks for the diagnosis! Code calling functions from the backported shutil should obviously catch exceptions from the backported shutil. I’ll review all modules using the backport. FYI, some distutils2 modules use shutil from the stdlib, for functions that are already here in 2.4; not sure if that is good or bad. > Ideally, I think distutils2/_backport/shutil.py should do "from shutil import > Error" > instead of defining its own Error class Oh, no, our backported module is strictly independent from the stdlib one. > importing shutil from the stdlib is broken in that file besides. I don’t understand this. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13170> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
