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 797138 - Meson build does not support Python 2
Meson build does not support Python 2
Status: RESOLVED DUPLICATE of bug 796092
Product: GStreamer
Classification: Platform
Component: gst-python
1.14.x
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-09-13 13:19 UTC by Jan Tojnar
Modified: 2018-09-26 13:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
meson: Allow building with Python 2 (4.83 KB, patch)
2018-09-13 13:19 UTC, Jan Tojnar 		none Details | Review

Description Jan Tojnar 2018-09-13 13:19:02 UTC 
Various projects like farstream still only support Python 2 so we need to support it too
Comment 1 Jan Tojnar 2018-09-13 13:19:36 UTC 
Created attachment 373641 [details] [review]
meson: Allow building with Python 2

Various projects like farstream still only support Python 2 so
we need to support it too
Comment 2 Philippe Normand 2018-09-13 13:36:21 UTC 
(In reply to Jan Tojnar from comment #0)
> Various projects like farstream still only support Python 2 so we need to
> support it too

Shouldn't these projects be ported to Python3 rather than dragging us back in time? Python2 is soon reaching end-of-life.
Comment 3 Sebastian Dröge (slomo) 2018-09-13 14:13:43 UTC 
I'd also prefer to not add Python 2 support back. People who are stuck at Python 2 can always continue using older versions of gst-python if needed.
Comment 4 Jan Tojnar 2018-09-13 14:14:50 UTC 
I agree that we should get rid of Python 3 as soon as possible but unfortunately the porting takes time. If we ignore Farstream (which apparently builds without gst-python), morituri (which can be replaced by whipper) and xpra (which supports Python 3 with some fiddling), at least one major dependent project has not been ported yet:

https://github.com/mopidy/mopidy/issues/779

Since Autotools build still support Python 2, the change is minimal and Python 2 EOL not until 2020, it would be nice to support it just a little longer.
Comment 5 Nicolas Dufresne (ndufresne) 2018-09-13 16:23:30 UTC 
Farstream have no hand written bindings. The generated binding works fine in Python3. We should port the small set of examples, and drop the left over .m4 and configure checks. But this is to be filed to Farstream project.

For the reference, the initial setup is the following (tested locally):
$ python3
>> import gi
>> gi.require_version('Gst', '1.0')
>> gi.require_version('Farstream', '0.2')
>> from gi.repository import Gst
>> from gi.repository import Farstream
>> Gst.init(None)
 ....
Comment 6 Jan Tojnar 2018-09-17 21:30:17 UTC 
Additionally, the also switches to the python module instead of the python3 one that is getting deprecated (https://github.com/mesonbuild/meson/pull/4169).
Comment 7 Zeeshan Ali 2018-09-25 23:18:01 UTC 
Should this be closed based on comment#5?
Comment 8 Tim-Philipp Müller 2018-09-26 08:19:51 UTC 
Is this a duplicate of bug Bug #796092 ? (or other way round)
Comment 9 Jan Tojnar 2018-09-26 13:20:59 UTC 
Yes, this is a duplicate. Not sure how I did not find it.Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 796092 ***