-
Notifications
You must be signed in to change notification settings - Fork 3k
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
pip editable installs doesn't copy data_files defined in setup.py #6592
Comments
The best approach here depends on your purpose, and there are two factors I can see:
If the files live inside the package, then this currently works with setuptools and pip for editable installs, sdists, and wheels, it just requires using example.sh
If the files live outside the package (like some of the jsnapy files) - this is not suggested in general, even for non-editably installed packages. For files meant to be accessed at runtime there is a specific statement in the setuptools docs here suggesting to take a different approach. For files not meant to be accessed at runtime, it may be better to bring the issue up on the setuptools issue tracker along with the specific use case. I could not find any existing issue there that seemed related. |
Hi @shrishinde, I hope the above helped. I'll close this issue now, but please let us know if you have any other problems. |
virtualenv
Description
pip editable installs doesn't copy data_files defined in setup.py
Expected behavior
data_files defined in setup.py should be copied to virtualenv irrespective of editable or non-editable mode installs.
How to Reproduce
Use any python module for this which has setup.py defined with data_files param for setup. Here setup is
from setuptools import setup
I faced this issue with my private code base but for giving example here I am using jsnapy
pip install jsnapy
/opt/
git clone [email protected]:Juniper/jsnapy.git
pip install -e /opt/jsnapy/
etc
orvar/logs
are not copied.The text was updated successfully, but these errors were encountered: