2009/4/11 Thiago Macieira <thiago@kde.org>:
> Well, if we detect Python 2.6, then we should install to the KDE prefix by
> default.
According to PEP 370[1], we should install it to the local
site-packages dir, usually ~/.local/lib/python2.6/site-packages.

[1] http://www.python.org/dev/peps/pep-0370/

> The problem then is, of course, the surprise factor: if someone
> upgrades, suddenly KDE starts installing to the wrong path.
>
> I recommend, instead, that we default to the KDE prefix and, if Python 2.5
> or earlier is detected, we print a big warning at the end of the cmake
> run, saying that you will not be able to run and that you should set the
> PYTHON_SITE_PACKAGES_DIR variable instead. Even make it a fatal error.
Except for the KDE prefix part, this seems reasonable.

However, I haven't looked at Michael's patch for a while, so I don't
remember if this is actually wrong too.
_______________________________________________
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem