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 eric.araujo
Recipients eric.araujo, lemburg, olliewalsh, pitrou, samtygier, tarek
Date 2012-07-02.20:37:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341261444.79.0.524400767305.issue8876@psf.upfronthosting.co.za>
In-reply-to
Content
AFAICT using hard links only serves to save up a little time and disk space; it seems to me that always copying would solve one or two bugs at a small cost (not so small for large projects, I don’t know).  Could this impact setup scripts?  Maybe if os.link were monkey-patched and expected to be called.  I could ask on distutils-sig.

In #15205 Ollie noted this: “distutils2 appears to always copy instead of hardlinking resolving all of these issues”.  That would be because d2 uses shutil.copytree and distutils.util.copy_file (yes, a function from distutils1 because of some Windows issue :().
History
Date User Action Args
2012-07-02 20:37:24eric.araujosetrecipients: + eric.araujo, lemburg, pitrou, tarek, samtygier, olliewalsh
2012-07-02 20:37:24eric.araujosetmessageid: <1341261444.79.0.524400767305.issue8876@psf.upfronthosting.co.za>
2012-07-02 20:37:24eric.araujolinkissue8876 messages
2012-07-02 20:37:23eric.araujocreate