.py files install to dist-packages not site-packages
Bug #790883 reported by
Bruno Postle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Hugin |
Fix Released
|
High
|
Unassigned |
Bug Description
[Just working on the 2011.1.0 fedora rpm package]
I'm no python expert so correct me if I'm wrong, the Hugin .py, .pyc & .pyo files install to here:
$LIBDIR/
...whereas the fedora documentation suggests they would go into:
$LIBDIR/
In particular they say that python libs should go in whatever location you get when you run this command:
python -c "from distutils.sysconfig import get_python_lib; print(get_
Which here is /usr/lib64/
Changed in hugin: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
I am no expert either, but the logical place where I would put Hugin Python scripts is: share/hugin/ plugins (or /usr/share/ hugin/plugins) for HPI scripts, i.e. those that only make sense when run as plugins from within Hugin. The plugins directory is to be created new.
* /usr/local/bin/ (or /usr/bin) for HSI scripts, i.e. those that are meant to be CLI commands or stand-alone GUI tools that simply use Hugin functionality.
* /usr/local/
The above is for "system-wide" distributed scripts and plugins that will be part of core Hugin.
Beyond that, the user can write their own scripts anywhere they can put executables with 'import hsi'; and we should make provision for a standard location in the user's own folder for his self-written plug-ins.
I am not sure that it makes sense to install .pyc and .pyo - IIRC these are generated automatically the first time the .py is executed.
We will also need equivalent locations for Windows and OSX.