kdev-python move to extragear -- once more

[Aleix Pol]

On Wed, Mar 20, 2013 at 8:20 PM, Albert Astals Cid <aacid at kde.org> wrote:

> El Dimecres, 20 de març de 2013, a les 10:27:55, Sven Brauch va escriure:
> > Hi,
> >
> > my patch to python [1] was merged recently, so I could start working
> > on porting kdev-python away from the python fork. [2] is a branch
> > which is up-to-date with master and works without the fork, it just
> > links against the system's python 3.4. It's not perfect yet, but
> > neither was the old python 3 support branch. As soon as Python 3.4 is
> > released, this brach will be the default.
> >
> > Since the patch contains (binary and source) incompatible changes, it
> > cannot be backported to python 2. Thus, the python 2 version of the
> > plugin will have to stay with the fork for the remainder of its
> > lifetime.
> >
> > It's not going to get much better than this. If we can't move this to
> > extragear now, then I don't see why we could do it anywhere in the
> > near future. Also there's really nothing more I can do about it now.
> >
> > Please let me know what you think.
>
> I know Pino has voiced a negative opinion about the python 2 fork being in
> there, and he obviously should be heard, but i'd like to listen more
> opinions
> in particular the ones of the extragear-kdevelop "module" (Aleix? Milian?).
>
> I mean what can't be fixed, can't be fixed. At the end if Pino thinks the
> python 2 fork is insecure he's always free to not package it in Debian.
>
> Opinions?
>
> Cheers,
>   Albert
>
> >
> > Greetings,
> > Sven
> >
> > ______
> > [1] http://hg.python.org/cpython/rev/7c5c678e4164
> > [2]
> >
> https://projects.kde.org/projects/kdereview/kdev-python/repository/show?rev
> > =python3-nofork
>

Python source code inclusion has been discussed in different occasions,
even sprints. My opinion is that it's a too bad that his attempts to get
the changes in Python to upstream failed, but I don't want this to be the
reason for Sven's work not being available to our users. It would be a
shame.

I think kdev-python should go forward, and if there are practical problems,
we'll have to deal with them.

Aleix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20130320/09cb7c94/attachment.htm>