Bug#849091: Port to Python 3 and python3-gst-1.0

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#849091: Port to Python 3 and python3-gst-1.0

Sebastian Dröge-6
Package: mopidy
Severity: normal
User: [hidden email]
Usertags: python-gst-1.0-removal

Hi,

your package currently depends on python-gst-1.0. Upstream is planning
to drop Python 2.x support in the near future, leaving only Python 3
support.

Please update your package to Python 3 to make this as painless as
possible later. Thanks!


Sebastian

signature.asc (981 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#849091: Port to Python 3 and python3-gst-1.0

Sebastian Dröge-6
On Thu, 22 Dec 2016 17:52:09 +0200 Sebastian Dröge <[hidden email]> wrote:

> your package currently depends on python-gst-1.0. Upstream is planning
> to drop Python 2.x support in the near future, leaving only Python 3
> support.
>
> Please update your package to Python 3 to make this as painless as
> possible later. Thanks!

Just an update here, this will likely happen in the next 2-3 months
with the next upstream release. Your package will become uninstallable
at that point unless it is ported to Python 3.

signature.asc (981 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#849091: Port to Python 3 and python3-gst-1.0

Thomas Goirand-3
In reply to this post by Sebastian Dröge-6
Hi,

I'm surprised to see no reply from the maintainer(s) when this bug has
been opened in 2016. This isn't reassuring, and likely to cause the
package to drop from Debian, especially as the Python team is actively
doing Python 2 removal.

Is this transition to Python 3 planned? What does upstream say?

Thomas Goirand (zigo)

Reply | Threaded
Open this post in threaded view
|

Bug#849091: Port to Python 3 and python3-gst-1.0

Stein Magnus Jodal
On Wed, Aug 14, 2019 at 10:56:21PM +0200, Thomas Goirand wrote:
> I'm surprised to see no reply from the maintainer(s) when this bug has
> been opened in 2016. This isn't reassuring, and likely to cause the
> package to drop from Debian, especially as the Python team is actively
> doing Python 2 removal.
>
> Is this transition to Python 3 planned? What does upstream say?

Hi!

I'm both the main upstream maintainer and the packager.

This bug is marked as forwarded to the upstream issue at
https://github.com/mopidy/mopidy/issues/779. That issue is also pinned
to the top of the upstream issues list.

tl;dr: Work porting Mopidy to Python 3 is ongoing. It is not blocked by
any dependencies, it is just plain regular work that needs to be
completed.

-jodal

signature.asc (849 bytes) Download Attachment