Relocatable python install
in [Python]
|
Prev: Updated License Term Agreement for VC Redistributable in VS 2008 SP1
Next: win32wnet.WNetAddConnection2 to specific network interface?
From: Michel on 14 Apr 2010 16:50 Hi, I would like to create a binary package of python that we will ship with our product. I need to be able to install the package anywhere in the file system. The interpreter seems to be ok with that, but a few other tools that are installed in the PREFIX/bin directory (pydoc, py2to3, python- config,...) contain hardcoded path to the interpreter. Is there a way around that? Or an configure option to prevent these files to be installed? Regards, Michel.
From: Mike Kent on 14 Apr 2010 17:00 On Apr 14, 4:50 pm, Michel <michel.metz...(a)gmail.com> wrote: > Hi, > > I would like to create a binary package of python that we will ship > with our product. I need to be able to install the package anywhere in > the file system. > > The interpreter seems to be ok with that, but a few other tools that > are installed in the PREFIX/bin directory (pydoc, py2to3, python- > config,...) contain hardcoded path to the interpreter. > > Is there a way around that? Or an configure option to prevent these > files to be installed? > > Regards, > > Michel. The standard way to handle this seems to be to write a post-install script that edits the interpreter path in those scripts to point it to the actual install path. I had to handle the same thing, and others have done it as well.
From: Gabriel Genellina on 14 Apr 2010 18:01
En Wed, 14 Apr 2010 18:00:24 -0300, Mike Kent <mrmakent(a)cox.net> escribi�: > On Apr 14, 4:50 pm, Michel <michel.metz...(a)gmail.com> wrote: >> Hi, >> >> I would like to create a binary package of python that we will ship >> with our product. I need to be able to install the package anywhere in >> the file system. >> >> The interpreter seems to be ok with that, but a few other tools that >> are installed in the PREFIX/bin directory (pydoc, py2to3, python- >> config,...) contain hardcoded path to the interpreter. >> >> Is there a way around that? Or an configure option to prevent these >> files to be installed? > > The standard way to handle this seems to be to write a post-install > script that edits the interpreter path in those scripts to point it to > the actual install path. I had to handle the same thing, and others > have done it as well. Note that scripts installed using distutils.core.setup(scripts=[...], ...) get the fix automatically. -- Gabriel Genellina |