Being all things to everyone is tough. I recently contributed some code to
support the openSUSE package manager, zypper, in pybombs. So universal
support is kind of an evolving feature. Perhaps it would be a start to
simply limit the initial virtualenv support to python2. I would suggest
that
Please note that there's an open issue on how PyBOMBS and venvs are
effectively broken (https://github.com/gnuradio/pybombs/issues/363).
There are also related issues regarding the fact that we don't know if
we're running Python 2 or 3. So yeah, I know about this, and would love
to see it fixed,
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
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.
Huh, that seems a bit *too* permissive – other users might thus have
modified freely a script that you run as your user!
On 21.03.2017 21:39, Naceur wrote:
> Thanks. I just circumvented it by getting rid of pip requirement and asking
> the recipe to get the deb/rpm requirements instead.
> FYI,
Thanks. I just circumvented it by getting rid of pip requirement and asking
the recipe to get the deb/rpm requirements instead.
FYI, my /home/nae/.local/bin/pip was already allowed 777.
Regards,
Naceur
--
View this message in context:
Personal two cents: On most modern linuxes, you shouldn't be installing
mako via pip, and much less even numpy (because that's a huge compile
including fortran interfaces).
I just go and remove pip from the list of preferred packagers on my
systems¹. Never ran into problems with that. Now, I've
Thank you for your reply. However, I don't want to have anything done
manually.
Maybe I need rephrasing my initial post:
It is not that I want PyBOMBS to to do a pip --user but I am more wondering
why it is saying:
> PyBOMBS.PackageManager - DEBUG - Using packager pip
> PyBOMBS.Packager.pip -
The answer would be virtualenvs, but virtualenvs are not fully supported
in PyBOMBS. You might be able to to this by hand, but I've never tried it:
- Create a prefix using the --virtualenv switch
- Manually pip install the package into the virtualenv
- Maybe you need to manually set the package
Hello GR,
I am creating a recipe for pytun as a dependency for an OOT module.
Is there a way I can tell pybombs to install that while passing --user to
pip because testing the install tells: pip is using elevated privileges
.
.
.
PyBOMBS.PackageManager - DEBUG - Checking if package pytun is
10 matches
Mail list logo
