Re: Bug#755757: transition: wxpython3.0
Am 23.07.2014 15:07, schrieb Olly Betts:
> On Wed, Jul 23, 2014 at 02:10:19PM +0200, Matthias Klose wrote:
>> Am 23.07.2014 03:38, schrieb Olly Betts:
>>> The intention is to eliminate wxwidgets2.8 (and hence wxpython 2.8) before
>>> releasing jessie - the last upstream release (2.8.12) was over 3 years ago,
>>> and there's very little upstream interest in bugs in it now.
>>
>> are you saying that around 80 packages will be removed for jessie just
>> because wxpython isn't yet ported to 3.0?
>
> I don't really understand the question - wxPython 3.0.0.0 was released
> in late 2013, and packages for it are in the NEW queue.
>
> I'm not suggesting we remove around 80 packages, but that we move them
> from using wxPython 2.8 to wxPython 3.0. As with any large transition,
> it's possible that we'll find a few candidates for removal in the
> process, but that's not the aim of the transition.
>
>>> This should be a "smooth transition", as the packages for wxpython 2.8 and
>>> 3.0 are co-installable.
>>
>> Maybe I misunderstand something but I wouldn't call this "smooth".
>
> Are you perhaps mixing up wxPython 3.0 and Python 3.x? It is the case
> that neither wxPython 2.8 nor wxPython 3.0 support Python 3.x, but
> that's irrelevant to this transition.
>
> In this context, "smooth transition" just means that packages can be
> switched one by one, rather than having to try to coordinate uploads
> of ~80 different packages.
no, I'm not mixing wxPython 3.0 and Python 3.x. Asking what will happen with
packages depending on wxPython 2.8 and which cannot be converted to 3.0.
the lack of Python3 support in wxpython 3.0 is disappointing, but such is life.
Matthias
Reply to: