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

Pip install does not use symlinks for bufrtables if wheels are enabled #2

Open
cpaulik opened this issue May 19, 2016 · 4 comments
Open
Labels

Comments

@cpaulik
Copy link
Contributor

cpaulik commented May 19, 2016

Running

pip install pybufr-ecmwf does not use symlinks for the BUFR tables.

This leads to 1.5 GB of used space for each environment in which it is installed in this way.

@cpaulik
Copy link
Contributor Author

cpaulik commented May 19, 2016

This is not really critical for me since I use my conda package but it might be interesting to know for others.

@jdkloe
Copy link
Owner

jdkloe commented May 19, 2016

that's strange. I just did a test on my own linux machine, and there I do not see this symlink problem. The installed module in $HOME/.local/lib/python2.7/site-packages/pybufr_ecmwf/ is just 18MB in size.
Could you give me some details on your machine and software/OS versions?

@cpaulik
Copy link
Contributor Author

cpaulik commented May 19, 2016

I've investigated a little bit and the reason for it is bdist_wheel which seems to be the default now. I'm using pip 8.1.1 and normal installation without the symlink problem can be achieved by disabling the building of wheels with the --no-binary flag

@cpaulik cpaulik changed the title Pip install does not use symlinks for bufrtables Pip install does not use symlinks for bufrtables if wheels are enabled May 19, 2016
@jdkloe
Copy link
Owner

jdkloe commented May 19, 2016

OK, thanks for your investigations. I am thinking of getting rid of these symlinks completely in a next version, but this will require some recoding. It may take a while before this is implemented.

@jdkloe jdkloe added the bug label Aug 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants