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

find_packages no longer follows symbolic links #195

Closed
bb-migration opened this Issue May 2, 2014 · 3 comments

Comments

Projects
None yet
1 participant
@bb-migration

bb-migration commented May 2, 2014

Originally reported by: jaraco (Bitbucket: jaraco, GitHub: jaraco)


In #184, it was reported that find_packages no longer follows symlinks, though it did in earlier versions. This should be corrected promptly.


@bb-migration

This comment has been minimized.

bb-migration commented May 3, 2014

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):


Restore traversal of symbolic links in find_packages. Fixes #195.

@bb-migration

This comment has been minimized.

bb-migration commented May 3, 2014

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):


Add test capturing failure when find_packages no longer follows symlinks. Ref #195

@bb-migration

This comment has been minimized.

bb-migration commented Mar 23, 2016

Original comment by mgunther (Bitbucket: mgunther, GitHub: mgunther):


Sorry to comment to such an old bug, but my issue is completely related. I would like to have a (boolean) option for find_packages, whether to follow symbolic links, or not.
I can understand that people want to create links and include them in their packages. However, usually -- in order to make my life easier -- I create soft links to my data and output directories inside the package directory. Now, when the linked directories are large (and usually mounted from other machines), buildout seems to "freeze" while using the find_packages function.

So, do you think that there is a possibility to have a boolean parameter for find_packages which allows to disable searching in these linked directories, possibly with a default value that replicated current behavior?

Manuel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment