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 aioryi
Recipients aioryi
Date 2008-05-29.15:32:24
SpamBayes Score 0.0296947
Marked as misclassified No
Message-id <>
shutil.copytree() uses shutil.copyfile() to copy files recursively.
shutil.copyfile() opens the source file for reading, and the destination
file for writing, followed by a call to shutil.copyfileobj().

If the file happens to be a named pipe rather than a normal file,
opening for read blocks the copying function, since the Unix OS needs a
writer process to attach to the same named pipe before the open-for-read

Rather than opening the file for reading, the correct action would
probably be to simply create a new named pipe with the same name at the
Looking at the Python2.3 code, the same type of problem seem to exist
for other non-normal file-types other than symlinks (eg device files,
sockets, and possibly a few others).
Date User Action Args
2008-05-29 15:32:31aioryisetspambayes_score: 0.0296947 -> 0.0296947
recipients: + aioryi
2008-05-29 15:32:30aioryisetspambayes_score: 0.0296947 -> 0.0296947
messageid: <>
2008-05-29 15:32:28aioryilinkissue3002 messages
2008-05-29 15:32:25aioryicreate