Re: Bug#755757: transition: wxpython3.0
On Mon, Aug 18, 2014 at 2:58 PM, Olly Betts <olly@survex.com> wrote:
> On Wed, Jul 23, 2014 at 03:33:03PM +0200, Matthias Klose wrote:
>> Asking what will happen with packages depending on wxPython 2.8 and
>> which cannot be converted to 3.0.
>
> There aren't many incompatible changes between wxPython 2.8 and 3.0.
> With the C++ API, the Unicode changes have been quite painful, but
> that's simply not relevant to wxPython.
>
> My hope is that we will get all packages converted, though I know from
> the wxwidgets2.8 transition that there are a few rdeps which are dead
> upstream and effectively unmaintained in Debian. If such a package
> isn't actually working currently and nobody has reported it, removal
> might be the best option.
Hi Olly, and thanks for working on wxpython3.0 transition.
While this is not directly related to the transition, can you please
use the correct package naming for python packages (at least in
future)?
For example, you recently (~ 2 days ago) added a new binary package:
* New binary package python-gtk-media3.0 for wx.media. (Closes: #722687)
Per the Python policy [1], it should have been named python-wx.media,
not python-gtk-media3.0 (we have these naming rules so that it's
easier to guess which package a module is in).
[1] https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-package_names
--
Dmitry Shachnev
Reply to: