Re: [Opensync-devel] python site-packages, debian, and opensync

[Chris F. <cd...@fo...>]

On Mon, Jul 11, 2011 at 09:32:31AM +0200, Bjoern Ricks wrote:
> Imho only debian changed the default installation. I couldn't find a PEP
> for site-package usage but e.g.
> http://docs.python.org/install/index.htmlexplicit mentions
> site-packages. Of course it is easy in python to change
> the include path via sys.path. For windows a PEP exists
> http://www.python.org/dev/peps/pep-0250/

Thanks.

As far as I could find, Debian actually patches site.py to rename
site-packages to dist-packages.  This changes any python program
that relies on site.py, automatically.  It still seems rather silly
to me to force site-packages when python itself is telling me
dist-packages.  Any normal system will tell me site-packages, as
normal.

Debian also adds the idea that the Filesystem Standard says that non-Debian
packages should install into /usr/local, and so Debian adds
/usr/local/.../dist-packages to the path as well, which takes
preceidence over the system paths.  This makes a lot of sense to
me, but not every system does this.

I think, in the end, your idea of adding a cmake override is best.
Even the ability to override which version of python to use would be
a good thing, I think.  That way it won't matter what default we use,
the compiling user can override it.  (as well as the packager.)

Do you have any comments or warnings that I should be careful about
if letting the user select which version of python to use?

- Chris