Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect if symlinks are supported on target file system #903

Closed
wants to merge 3 commits into from

Conversation

techtonik
Copy link

This detects symlink suppot on destination filesystem and not only in Python interpreter or OS. If symlinks are not supported, falls back to copy behavior.

This fixes some case reported in #92 and #409, without specifying --always-copy explicitly.

Ideal case would be to invert virtualenv symlinking behavior - symlink only when explicitly requested.


This was migrated from #663 to reparent it to the master branch. Please see original pull request for any previous discussion.

This detects symlink suppot on destination filesystem
and not only in Python interpreter or OS. If symlinks
are not supported, falls back to copy behavior.
@techtonik
Copy link
Author

@Ivoz @dstufft ready for review. People are patching utilities like tox with workarounds against this bug, and this PR should make it unnecessary - https://bitbucket.org/hpk42/tox/pull-requests/205/fix-issue-218/diff

@techtonik
Copy link
Author

Ping?

Copy link
Contributor

@gaborbernat gaborbernat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please rebase on master? And add some tests, thanks!

@gaborbernat
Copy link
Contributor

Closing this due to inactivity.

@techtonik
Copy link
Author

techtonik commented Dec 28, 2018

I couldn't wait 2 years. Sorry. 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants