Hi Michael,

On Apr 04, 2016, at 01:52 AM, Michael Biebl wrote:

>Andreas was suggesting a compromise.  Split out the python2 loader but keep
>the python3 loader within the main libpeas-1.0-0 package. This will reduce
>the churn quite a but.

I think I missed that, thanks for the clarification.

This solution works for me.  I'll note the one difference is that it will keep
a Python dependency even for libpeas clients that don't extend through Python
(crazy talk, I know! :).  But since it will be a Python *3* dependency and
Python 2 can be split off and demoted, that's okay by me.

>This means we can close most of the bugs and and only need to keep the 3
>python2 bugs open. We should follow up there and make it clear that they
>should update to python3. They then can drop the explicit dependency on
>the python2 loader package again.

+1

>I intend to work on the libpeas package the next couple of days.
>One of the modfications I'd like to do, is move the python2 loader
>package to oldlibs/extra and drop the soname specific part from the package.
>
>I hope you can agree with this plan, if not, please shout.

<sotto voce> I agree with the plan.  :)

Thanks!

Attachment: pgpp8atBQIAEo.pgp
Description: OpenPGP digital signature

Reply via email to