Feature #579
Consider compiling Python bytecode to a path with Python version in it
| Status: | In Progress | Start date: | ||
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | packaging | Spent time: | - | |
| Target version: | 1.6 | |||
| Resolution: | Version: | 0.5.11 | ||
| Trac ticket ID: | 579 |
Description
In morituri's bin/rip.in:
if not "@PYTHONLIBDIR@" in sys.path:
sys.path.append("@PYTHONLIBDIR@")
In morituri's configure.ac:
dnl check for python
AS_PATH_PYTHON(2.3)
dnl check for where to install our python stuff
PYVER=[@$PYTHON -c "import sys ; print sys.version[:3]"@]
dnl This is the best way of installing in an arch-independent location for now
AS_AC_EXPAND(PYTHONLIBDIR, "\${exec_prefix}/lib/python$PYVER/site-packages")
AC_MSG_NOTICE(Installing python code in $PYTHONLIBDIR)
AC_SUBST(PYTHONLIBDIR)
History
Updated by Alexandre Quessy almost 3 years ago
- Status changed from New to In Progress
Our package does not provide public Python packages. Therefore, we could detect the python version at compile time and harcode it in the executables, as a #! string.
Updated by Alexandre Quessy 10 months ago
- Target version changed from 0.6.3 to 1.6