Movatterモバイル変換
[0]ホーム
linux & users' python-extensions
Paweł Stołowskipawelstol at poczta.onet.pl
Thu Apr 12 18:04:27 EDT 2001
John J. Lee wrote:> On 11 Apr 2001, [iso-8859-2] Paweł Stołowski wrote:>> Now, when I put spam.py in ~/lib/python2.0, it works. But what should I>> do to make visible an extension module to the system (without cluttering>> global configuration)?. There are some Setup.* files in>> /usr/local/lib/python2.0/config/ (main python files) that list>> dependencies beetwen .py and extension modules; do I have to make a copy> [...]> Don't have a copy here to check, but if those 'Setup.*' files are setup.py> scripts, then no, you don't have to copy them anywhere -- see the> Distutils docs in the standard distribution of Python. If they're> something else, that I know not about, wait for somebody else to answer> the question. :) You don't need to copy them anywhere to make your> modules visible, though.>> For an extension module to be visible, it just has to be in sys.path.Yeah, I managed to achieve the goal! :) The problem was that *I thought*,that putting a compiled extension spam.so is the first step, and thesecond is to inform python not only where the modules lies, but also addsomething like:*share*spam spam.cto a Setup file, that was placed in /usr/local/lib/python2.0/config.And of course Setup file has nothing to do with users' extensions. It isonly used by the makefiles provided with python (and may be used byusers, too, to compile modules easily). The only thing an userhas to do is to set PYTHONPATH to his own built extensions. That's all.Another example how one can make his life harder by himself :)Thanks for help,yogin-- ___________________________________________Linux User #165389 ICQ #47602612 .Bydgoszcz-[http://www.komputery.bydgoszcz.pl/linux]-
More information about the Python-listmailing list
[8]ページ先頭