Using your requirements.txt, things worked well here: # virtualenv t # source t/bin/activate # pip install -U pip setuptools wheel # pip wheel -w wheels -r requirements.txt # pip wheel -w wheels --global-option=--with-speedups genshi==0.6 # rm -vf wheels/Genshi-0.6-py2-none-any.whl # pip install wheels/*.whl
In theory, one should be able to add global options to the requirements.txt file: ... genshi==0.6 --global-option=--with-speedups ... but in my tests that didn't work - it is honored by "pip install", but ignored by "pip wheel". Also, it has unwanted global effects, see https://github.com/pypa/pip/issues/4118. The more general question is, whether it is really an issue if packages are installed from a wheel or as egg. Using this recipe (and your unmodified requirements.txt) to directly installing packages # virtualenv t # source t/bin/activate # pip install -U pip setuptools wheel # pip install --global-option=--with-speedups genshi==0.6 # pip install -r requirements.txt will not put any zipped eggs in t/lib/python2.7/site-packages, so I guess in that case also no egg cache will be used? - Thomas -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
