Is it possible to save binaries that pip compiles while installing a package?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I'm working on a project for a Raspberry Pi 3.
One of the things my project requires is cython.



Running pip install cython on a Raspberry Pi inside of a virtualenv takes about 40 minutes to complete, as cython apparently needs to be compiled first. During these 40 minutes, top shows cc running, trying to compile stuff, using 100% of one core.



I need to do this several times every day, as I keep needing to reset the SD card to a fresh image of Raspbian. This is obviously very time-consuming, and is slowing down progress.



When pip is done compiling cython, where are the binaries stored? Inside the virtualenv? Somewhere else on the filesystem?



If they are stored in the virtualenv, can I archive the entire virtualenv folder, and restore it to a fresh Linux, and expect it to work? I know virtualenvs aren't supposed to be portable (without using the --relocatable arg, which seems to have its own issues), but in my case, the path of the virtualenv will remain the same when I restore it.




compiling pip virtualenv




share|improve this question



















  • If you are putting the same binaries in the same distribution with the same hardware, you should only compile it once, save and copy as necessary. Pip will store files in the virtualenv and tracks where it places each file, use pip show -f somepackage to see where pip placed all the files resulting from compiling sompackage
    – GracefulRestart
    Jun 26 at 20:55














up vote
1
down vote

favorite












I'm working on a project for a Raspberry Pi 3.
One of the things my project requires is cython.



Running pip install cython on a Raspberry Pi inside of a virtualenv takes about 40 minutes to complete, as cython apparently needs to be compiled first. During these 40 minutes, top shows cc running, trying to compile stuff, using 100% of one core.



I need to do this several times every day, as I keep needing to reset the SD card to a fresh image of Raspbian. This is obviously very time-consuming, and is slowing down progress.



When pip is done compiling cython, where are the binaries stored? Inside the virtualenv? Somewhere else on the filesystem?



If they are stored in the virtualenv, can I archive the entire virtualenv folder, and restore it to a fresh Linux, and expect it to work? I know virtualenvs aren't supposed to be portable (without using the --relocatable arg, which seems to have its own issues), but in my case, the path of the virtualenv will remain the same when I restore it.




compiling pip virtualenv




share|improve this question



















  • If you are putting the same binaries in the same distribution with the same hardware, you should only compile it once, save and copy as necessary. Pip will store files in the virtualenv and tracks where it places each file, use pip show -f somepackage to see where pip placed all the files resulting from compiling sompackage
    – GracefulRestart
    Jun 26 at 20:55












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I'm working on a project for a Raspberry Pi 3.
One of the things my project requires is cython.



Running pip install cython on a Raspberry Pi inside of a virtualenv takes about 40 minutes to complete, as cython apparently needs to be compiled first. During these 40 minutes, top shows cc running, trying to compile stuff, using 100% of one core.



I need to do this several times every day, as I keep needing to reset the SD card to a fresh image of Raspbian. This is obviously very time-consuming, and is slowing down progress.



When pip is done compiling cython, where are the binaries stored? Inside the virtualenv? Somewhere else on the filesystem?



If they are stored in the virtualenv, can I archive the entire virtualenv folder, and restore it to a fresh Linux, and expect it to work? I know virtualenvs aren't supposed to be portable (without using the --relocatable arg, which seems to have its own issues), but in my case, the path of the virtualenv will remain the same when I restore it.




compiling pip virtualenv




share|improve this question











I'm working on a project for a Raspberry Pi 3.
One of the things my project requires is cython.



Running pip install cython on a Raspberry Pi inside of a virtualenv takes about 40 minutes to complete, as cython apparently needs to be compiled first. During these 40 minutes, top shows cc running, trying to compile stuff, using 100% of one core.



I need to do this several times every day, as I keep needing to reset the SD card to a fresh image of Raspbian. This is obviously very time-consuming, and is slowing down progress.



When pip is done compiling cython, where are the binaries stored? Inside the virtualenv? Somewhere else on the filesystem?



If they are stored in the virtualenv, can I archive the entire virtualenv folder, and restore it to a fresh Linux, and expect it to work? I know virtualenvs aren't supposed to be portable (without using the --relocatable arg, which seems to have its own issues), but in my case, the path of the virtualenv will remain the same when I restore it.





compiling pip virtualenv





share|improve this question










share|improve this question




share|improve this question









asked Jun 26 at 18:59









Tal

592721




592721











  • If you are putting the same binaries in the same distribution with the same hardware, you should only compile it once, save and copy as necessary. Pip will store files in the virtualenv and tracks where it places each file, use pip show -f somepackage to see where pip placed all the files resulting from compiling sompackage
    – GracefulRestart
    Jun 26 at 20:55
















  • If you are putting the same binaries in the same distribution with the same hardware, you should only compile it once, save and copy as necessary. Pip will store files in the virtualenv and tracks where it places each file, use pip show -f somepackage to see where pip placed all the files resulting from compiling sompackage
    – GracefulRestart
    Jun 26 at 20:55















If you are putting the same binaries in the same distribution with the same hardware, you should only compile it once, save and copy as necessary. Pip will store files in the virtualenv and tracks where it places each file, use pip show -f somepackage to see where pip placed all the files resulting from compiling sompackage
– GracefulRestart
Jun 26 at 20:55




If you are putting the same binaries in the same distribution with the same hardware, you should only compile it once, save and copy as necessary. Pip will store files in the virtualenv and tracks where it places each file, use pip show -f somepackage to see where pip placed all the files resulting from compiling sompackage
– GracefulRestart
Jun 26 at 20:55










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










Just copy the wheel file from the cache dir. When pip install pkgname is issued and pip doesn't find a compatible wheel to install from, it builds one from the source dist and stores it in cache to reuse for future reinstalls. To find the wheel file, issue



$ find $HOME/.cache/pip -type f -name Cython*.whl


Backup the file; to install from the local file, just issue



$ pip install path/to/file.whl


Where to go from here: local repository



When you have a lot of prebuilt wheels collected, the next step would be setting up a local PyPI repository to install from. The simplest way is to organize the wheels into package-named dirs and run a simple HTTP server:



└── repodir
 ├── Cython
 │ └── Cython-0.28.0-cp36-cp36m-linux_aarch64.whl
 ...


Start the server with e.g.



$ python3 -m http.server -p 9000


Now you can pass the repo to pip:



$ pip install Cython --extra-index-url=http://127.0.0.1:9000


or even persist the repo URL in the pip.conf to not to enter it each time:



# pip.conf
[global]
extra-index-url=http://127.0.0.1:9000


Should you look for more, there are lots of fancy PyPI repo servers out there like devpi which offer versatile package management, web UI etc.






share|improve this answer























  • It looks like when using virtualenvs, the wheel files are stored inside the virtual env. Archiving the virtualenv with tar, and later restoring it to a clean Linux worked with no issues, and sped up the process of setting up a fresh Linux considerably. Thanks for the idea of a local repo - I might do that.
    – Tal
    Jun 28 at 14:40










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f452082%2fis-it-possible-to-save-binaries-that-pip-compiles-while-installing-a-package%23new-answer', 'question_page');

);

Post as a guest

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










Just copy the wheel file from the cache dir. When pip install pkgname is issued and pip doesn't find a compatible wheel to install from, it builds one from the source dist and stores it in cache to reuse for future reinstalls. To find the wheel file, issue



$ find $HOME/.cache/pip -type f -name Cython*.whl


Backup the file; to install from the local file, just issue



$ pip install path/to/file.whl


Where to go from here: local repository



When you have a lot of prebuilt wheels collected, the next step would be setting up a local PyPI repository to install from. The simplest way is to organize the wheels into package-named dirs and run a simple HTTP server:



└── repodir
 ├── Cython
 │ └── Cython-0.28.0-cp36-cp36m-linux_aarch64.whl
 ...


Start the server with e.g.



$ python3 -m http.server -p 9000


Now you can pass the repo to pip:



$ pip install Cython --extra-index-url=http://127.0.0.1:9000


or even persist the repo URL in the pip.conf to not to enter it each time:



# pip.conf
[global]
extra-index-url=http://127.0.0.1:9000


Should you look for more, there are lots of fancy PyPI repo servers out there like devpi which offer versatile package management, web UI etc.






share|improve this answer























  • It looks like when using virtualenvs, the wheel files are stored inside the virtual env. Archiving the virtualenv with tar, and later restoring it to a clean Linux worked with no issues, and sped up the process of setting up a fresh Linux considerably. Thanks for the idea of a local repo - I might do that.
    – Tal
    Jun 28 at 14:40














up vote
1
down vote



accepted










Just copy the wheel file from the cache dir. When pip install pkgname is issued and pip doesn't find a compatible wheel to install from, it builds one from the source dist and stores it in cache to reuse for future reinstalls. To find the wheel file, issue



$ find $HOME/.cache/pip -type f -name Cython*.whl


Backup the file; to install from the local file, just issue



$ pip install path/to/file.whl


Where to go from here: local repository



When you have a lot of prebuilt wheels collected, the next step would be setting up a local PyPI repository to install from. The simplest way is to organize the wheels into package-named dirs and run a simple HTTP server:



└── repodir
 ├── Cython
 │ └── Cython-0.28.0-cp36-cp36m-linux_aarch64.whl
 ...


Start the server with e.g.



$ python3 -m http.server -p 9000


Now you can pass the repo to pip:



$ pip install Cython --extra-index-url=http://127.0.0.1:9000


or even persist the repo URL in the pip.conf to not to enter it each time:



# pip.conf
[global]
extra-index-url=http://127.0.0.1:9000


Should you look for more, there are lots of fancy PyPI repo servers out there like devpi which offer versatile package management, web UI etc.






share|improve this answer























  • It looks like when using virtualenvs, the wheel files are stored inside the virtual env. Archiving the virtualenv with tar, and later restoring it to a clean Linux worked with no issues, and sped up the process of setting up a fresh Linux considerably. Thanks for the idea of a local repo - I might do that.
    – Tal
    Jun 28 at 14:40












up vote
1
down vote



accepted







up vote
1
down vote



accepted






Just copy the wheel file from the cache dir. When pip install pkgname is issued and pip doesn't find a compatible wheel to install from, it builds one from the source dist and stores it in cache to reuse for future reinstalls. To find the wheel file, issue



$ find $HOME/.cache/pip -type f -name Cython*.whl


Backup the file; to install from the local file, just issue



$ pip install path/to/file.whl


Where to go from here: local repository



When you have a lot of prebuilt wheels collected, the next step would be setting up a local PyPI repository to install from. The simplest way is to organize the wheels into package-named dirs and run a simple HTTP server:



└── repodir
 ├── Cython
 │ └── Cython-0.28.0-cp36-cp36m-linux_aarch64.whl
 ...


Start the server with e.g.



$ python3 -m http.server -p 9000


Now you can pass the repo to pip:



$ pip install Cython --extra-index-url=http://127.0.0.1:9000


or even persist the repo URL in the pip.conf to not to enter it each time:



# pip.conf
[global]
extra-index-url=http://127.0.0.1:9000


Should you look for more, there are lots of fancy PyPI repo servers out there like devpi which offer versatile package management, web UI etc.






share|improve this answer















Just copy the wheel file from the cache dir. When pip install pkgname is issued and pip doesn't find a compatible wheel to install from, it builds one from the source dist and stores it in cache to reuse for future reinstalls. To find the wheel file, issue



$ find $HOME/.cache/pip -type f -name Cython*.whl


Backup the file; to install from the local file, just issue



$ pip install path/to/file.whl


Where to go from here: local repository



When you have a lot of prebuilt wheels collected, the next step would be setting up a local PyPI repository to install from. The simplest way is to organize the wheels into package-named dirs and run a simple HTTP server:



└── repodir
 ├── Cython
 │ └── Cython-0.28.0-cp36-cp36m-linux_aarch64.whl
 ...


Start the server with e.g.



$ python3 -m http.server -p 9000


Now you can pass the repo to pip:



$ pip install Cython --extra-index-url=http://127.0.0.1:9000


or even persist the repo URL in the pip.conf to not to enter it each time:



# pip.conf
[global]
extra-index-url=http://127.0.0.1:9000


Should you look for more, there are lots of fancy PyPI repo servers out there like devpi which offer versatile package management, web UI etc.







share|improve this answer















share|improve this answer



share|improve this answer








edited Jul 1 at 23:26


























answered Jun 28 at 8:26









hoefling

398310




398310











  • It looks like when using virtualenvs, the wheel files are stored inside the virtual env. Archiving the virtualenv with tar, and later restoring it to a clean Linux worked with no issues, and sped up the process of setting up a fresh Linux considerably. Thanks for the idea of a local repo - I might do that.
    – Tal
    Jun 28 at 14:40
















  • It looks like when using virtualenvs, the wheel files are stored inside the virtual env. Archiving the virtualenv with tar, and later restoring it to a clean Linux worked with no issues, and sped up the process of setting up a fresh Linux considerably. Thanks for the idea of a local repo - I might do that.
    – Tal
    Jun 28 at 14:40















It looks like when using virtualenvs, the wheel files are stored inside the virtual env. Archiving the virtualenv with tar, and later restoring it to a clean Linux worked with no issues, and sped up the process of setting up a fresh Linux considerably. Thanks for the idea of a local repo - I might do that.
– Tal
Jun 28 at 14:40




It looks like when using virtualenvs, the wheel files are stored inside the virtual env. Archiving the virtualenv with tar, and later restoring it to a clean Linux worked with no issues, and sped up the process of setting up a fresh Linux considerably. Thanks for the idea of a local repo - I might do that.
– Tal
Jun 28 at 14:40












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f452082%2fis-it-possible-to-save-binaries-that-pip-compiles-while-installing-a-package%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more