[issue15100] Race conditions in shutil.copy, shutil.copy2 and shutil.copyfile
Additionally, shutil.copyfile procedure seems to have a problem with symlinks that could result in the corruption of content of any file on filesystem (in favorable conditions). --- Does the shutil.copyfile corruption issue impact Python 2.6? And, what sort of favorable conditions need to exist for this to happen? I ask because we are seeing some file corruption on a GPFS filesystem where we are using Python 2.6 and shutil.copyfile with symlinks. I'm not on this list, so cc me if you reply to the list and want me to see the response. Thanks, Brad ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1755] Misspelling in future.c in 2.5.1 source (handl should be handle)
New submission from Brad Tilley: /* A subsequent pass will detect future imports that don't appear at the beginning of the file. There's one case, however, that is easier to handl here: A series of imports joined by semi-colons, where the first import is a future statement but some subsequent import has the future form but is preceded by a regular import. */ -- components: None messages: 59445 nosy: brad severity: minor status: open title: Misspelling in future.c in 2.5.1 source (handl should be handle) versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1755 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
