kdev-python move to extragear -- once more

[Sven Brauch]

Hey,

this is still not resolved. If I'm not hearing any objection soon-ish,
then I'll assume you're okay with moving kdev-python to extragear, and
continue working on the python fork issue from there. Python 3.4 is
scheduled for early 2014, and I think the python people's idea of
merging my patch is "somewhere before the feature freeze for this
release", so it might take a while -- far too long to keep kdev-python
stuck in kdereview.

Cheers,
Sven

2013/2/16 Sven Brauch <svenbrauch at googlemail.com>:
> Hello,
>
> A while ago, I asked for a review of kdev-python, in order for it to
> be moved from playground to extragear. There was some (legitimate)
> objection about the fork of the python parser code the plugin
> contains, which is why the move has not taken place yet, and
> kdev-python is still residing in kdereview.
>
> I'm actively working on solving the issue -- chances that a patch can
> be applied upstream which enables me to drop the fork are good. [1]
> (This would however only apply to future releases of the python 3
> version of the plugin, since the patch introduces binary-incompatible
> changes upstream which cannot be backported to python 2.)
>
> Thus, I would suggest to move kdev-python to extragear, even if the
> issue is not solved yet.
> If you disagree, let me know, in that case I must move kdev-python
> back to playground and propose it for review again once the fork has
> been removed from the master branch. I would however prefer not to do
> this.
>
> Thanks and best regards,
> Sven Brauch
>
> ______
> [1] http://bugs.python.org/issue16795