FS#57827 : [ogre] Python Bindings Module Path

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#57827 - [ogre] Python Bindings Module Path

Attached to Project: Community Packages
Opened by Steffen Pankratz (kratz00) - Tuesday, 13 March 2018, 20:37 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 16 March 2018, 19:05 GMT

Task Type	Bug Report
Category	Upstream Bugs
Status	Closed
Assigned To	Sven-Hendrik Haase (Svenstaro)
Architecture	All
Severity	Low
Priority	Normal
Reported Version
Due in Version	Undecided
Due Date	Undecided
Percent Complete
Votes	1 Steffen Pankratz (kratz00) (2018-03-13)
Private	No

Details

I wanted to try out the Ogre Python bindings, but the Ogre Python modules can not be imported by default.
They get installed in /usr/lib/python3.6/dist-packages/

But Python3 is only looking in:

/usr/lib/python36.zip
/usr/lib/python3.6
/usr/lib/python3.6/lib-dynload
/usr/lib/python3.6/site-packages
/usr/lib/python3.6/site-packages/gtk-2.0

As a workaround I can start Python3 like 'PYTHONPATH=/usr/lib/python3.6/dist-packages/ python3' so the Ogre Python modules get found.

My proposal is to install the Ogre Python modules instead of in /usr/lib/python3.6/dist-packages/, in /usr/lib/python3.6/site-packages/.
If you would be okay with this solution, I have a patch I can provide.

This task depends upon

Closed by Eli Schwartz (eschwartz)
Friday, 16 March 2018, 19:05 GMT
Reason for closing: Fixed
Additional comments about closing: ogre 1.10.11-4