graphite-dev team mailing list archive
-
graphite-dev team
-
Mailing list archive
-
Message #06686
Re: [Question #662391]: Target WSGI script '/opt/graphite/conf/graphite.wsgi' cannot be loaded as Python module
Question #662391 on Graphite changed:
https://answers.launchpad.net/graphite/+question/662391
Piotr Popieluch posted a new comment:
I really can't recommend installing with pip (without virtualenv). The
issue is that pip installs libraries in the same paths as yum/dnf. There
is no support for installing multiple versions of a library at the same
time (neither in yum or pip), which means pip can update installed
system libraries. Obviously this can make a mess of your system Python
and mess up your rpmdb (other versions are installed than yum thinks).
Many system tools on Fedora/RHEL are Python based, for example yum/dnf
itself. Using pip to install libraries can potentially break your
system. Also when you run a "yum update/install someotherpythonapp"
later, this can break you Graphite installation as yum might downgrade
your Python libraries.
There have been some attempts to split into a system python and a user
python in separate directories, a bit comparable to how Perl does this
with system_perl, site_pers, user_perl. But afaik these attempts have
all failed (don't know the specifics).
I'm a Fedora/RHEL guy, no clue how other distros handle this but I guess
they also use the Ostrich algorithm :)
Anyway, if you want to run latest Graphite on RHEL based systems I would
recommend to install it in virtualenv or Docker. This installs it
completely isolated so it cannot mess up your system.
--
You received this question notification because your team graphite-dev
is an answer contact for Graphite.