This is a problem I have faced as well. I have a number of projects at various levels of modification of GR and various 3rd party python packages being supported. I find having virtualenvs to be very useful in keeping python package versions, GR mods, and my own modules in agreement. I've been tinkering a bunch with getting venvs and pybombs to work together and I think I've made some headway. For example, the elevated privileges for pip is (nominally) hardcoded in packagers/pip.py. I made a modification to condition elevation on the presence of a virtualenv, which is detected in the config_manager. This is one way to perhaps get pybombs and virtualenvs to play nice. I'll hopefully be offering a pull request soon that incorporates a number of changes.
On Wed, Mar 22, 2017 at 12:30 PM, Naceur <[email protected]> wrote: > You are right if they had access to it at first place. Anyhow I fixed it. > > > > -- > View this message in context: http://gnuradio.4.n7.nabble. > com/installing-a-python-package-without-elevated- > privileges-tp63183p63258.html > Sent from the GnuRadio mailing list archive at Nabble.com. > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
