A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-list/2001-April/093301.html below:

linux & users' python-extensions

linux & users' python-extensions linux & users' python-extensionsMichael Hudson mwh21 at cam.ac.uk
Wed Apr 11 18:41:31 EDT 2001
pawelstol at poczta.onet.pl (=?iso-8859-2?Q?Pawe=B3_Sto=B3owski?=) writes:

> I've installed Python into /usr/local/bin and /usr/local/lib/Python2.0.
> Now I'd like to allow an ordinary user to maintain his own python-extensions
> modules (written in C/C++). So, each user's python programs should see
> the global modules hierarchy, but also allow the user to import his own
> modules and link coresponding C/C++ modules, when needed. Is it possible
> without cluttering global Python-configuration each time an user needs
> to play with his new extension-module? 

You could put something like

sys.path.append(os.path.join(os.environ["HOME"],"lib/python2.0")

is site.py.

HTH,
M.

-- 
  For every complex problem, there is a solution that is simple,
  neat, and wrong.                                    -- H. L. Mencken

More information about the Python-list mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4