After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 726831 - Allow installing to a different path than pygobject3 main overrides path
Allow installing to a different path than pygobject3 main overrides path
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-python
unspecified
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-03-21 16:26 UTC by 宋文武
Modified: 2018-11-03 15:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description 宋文武 2014-03-21 16:26:21 UTC
Currently, it not work.

See:
http://git.gnome.org/browse/pygobject/commit?id=b1a9848a7a7255e6b1ccd98712dd62b1514078b9
Comment 1 宋文武 2014-03-22 14:16:33 UTC
Well, __init__.py does exist in git repo, but not in tarball and final install.
Comment 2 Thibault Saunier 2014-06-09 09:21:56 UTC
If you set PYTHON=python3 when compiling it will be installed in the python3 prefix, then if you set it to python2 it will be installed in the python3 prefix.
Comment 3 Tim-Philipp Müller 2014-06-09 09:46:47 UTC
Out of curiosity: why do we default to python2 instead of python3?
Comment 4 Thibault Saunier 2014-06-09 09:52:22 UTC
Just because, I will make sure to change that before releasin 1.4 :)
Comment 5 宋文武 2014-06-16 12:48:11 UTC
(In reply to comment #2)
> If you set PYTHON=python3 when compiling it will be installed in the python3
> prefix, then if you set it to python2 it will be installed in the python3
> prefix.

Sorry, I wrote a misleading bug title, and gave a unclearly description.
It can be installed but will not work correctly when installed into a different prefix than pygobject3.

For example, what I have:
gst-python at /x/lib/python2.7/site-packages/gi
pygobject3 at /y/lib/python2.7/site-packages/gi
The GI overrides installed into different directories. 

Actually, I run into this bug when package pitivi for nixpkgs[1].
For nix[2] package manager, each packages must installed in its own unique subdirectory.

We should modify some autotools stuff to make gi/overrides/__init__.py install.

[1] https://github.com/NixOS/nixpkgs/pull/2001
[2] http://nixos.org/nix/about.html
Comment 6 Thibault Saunier 2014-06-16 12:54:53 UTC
It is how pygobject people told me it was supposed to work, overrides should all land in the same directory.

I am not against installing __init__.py in case we are installing in another directory as it should work (given that we are *guaranteed* that /y/lib/python2.7/site-packages/gi will be scanned by python before /x/lib/python2.7/site-packages/gi (setting PYTHONPATH in the right order for example)).But that should be done *only* if we are not installing in the same directory as PyGobject as we clearly do not want to override the __init__.py installed by pygobject.
Comment 7 宋文武 2014-06-19 10:59:37 UTC
Thanks for explaining.
Comment 8 Thibault Saunier 2014-06-19 21:45:09 UTC
Actually we should look for a proper solution, reopening the bug.
Comment 9 GStreamer system administrator 2018-11-03 15:36:41 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-python/issues/3.