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 olliewalsh
Recipients Arfrever, eric.araujo, eric.smith, olliewalsh, tarek
Date 2012-07-04.11:05:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341399920.79.0.97360836082.issue15205@psf.upfronthosting.co.za>
In-reply-to
Content
Hi,

> As I said in the other bug, symlinks handling in not fully specified

Yes. I've mostly submitted a bug report in case anybody else encounters the problem.

> At present I am not sure if having symlinks in a distribution makes sense

I agree.
In my case symlinks are being used to restructure a large legacy module into smaller packages. When creating sdists the symlinks are dereferenced on another developer's host (OSX) and all is well but they on my host (Linux) I get packages with broken symlinks.

> BTW the example you link to is not at all monkey-patching

My mistake. When I worked around this issue I did monkey-patch sdist. I also just wrapped the source path is os.path.readlink() before hardlinking. I think the approach in that link is a much better solution so I have referred to it instead.

-Ollie
History
Date User Action Args
2012-07-04 11:05:20olliewalshsetrecipients: + olliewalsh, eric.smith, tarek, eric.araujo, Arfrever
2012-07-04 11:05:20olliewalshsetmessageid: <1341399920.79.0.97360836082.issue15205@psf.upfronthosting.co.za>
2012-07-04 11:05:20olliewalshlinkissue15205 messages
2012-07-04 11:05:19olliewalshcreate