Multiple python-3 packages

Multiple python-3 packages

[Leo Famulari]

Currently we have Python 3.4 and 3.5. Python 3.6 was released recently.

When we added 3.5, I thought it was a good idea to keep 3.4 around in
case some packages need it. It turns out that nothing is using it in our
tree.

Do we want to keep 3.4 and 3.5 around? There is a maintenance cost
incurred at each new release, because their shared patches tend to
diverge each time.

If we should keep them, how should the package inheritance go? Now, it's
like this:

2.7 < 3.5 < 3.4

If we kept them all, should 3.5 and 3.4 both inherit 3.6?

Re: Multiple python-3 packages

[Benz Schenk]

On Fri, 27 Jan 2017 05:12:25 -0500
Leo Famulari <leo@famulari.name> wrote:

> Currently we have Python 3.4 and 3.5. Python 3.6 was released recently.
> 
> When we added 3.5, I thought it was a good idea to keep 3.4 around in
> case some packages need it. It turns out that nothing is using it in our
> tree.
> 
> Do we want to keep 3.4 and 3.5 around? There is a maintenance cost
> incurred at each new release, because their shared patches tend to
> diverge each time.

As far as my grep-fu tells me, there's no packages that rely on a
specific Python 3 release in their definition as of now, so I'd be in
favour of dropping the old versions. 

If packages start to fail because of compatibility issues, I'd say
that's
a) an upstream issue, which admittedly has to be worked around until
they hopefuly fix it, but still 
b) until the definitions of the affected packages are patched it would
happen anyway

worst case scenario, the old versions have to be are added again and
people just rollback and keep using whatever they have installed atm
until the needed version is available again and the package definitions
are fixed

> 
> If we should keep them, how should the package inheritance go? Now, it's
> like this:
> 
> 2.7 < 3.5 < 3.4
> 
> If we kept them all, should 3.5 and 3.4 both inherit 3.6?

That would make sense

Re: Multiple python-3 packages

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 980 bytes --]

Leo Famulari <leo@famulari.name> writes:

> Currently we have Python 3.4 and 3.5. Python 3.6 was released recently.
>
> When we added 3.5, I thought it was a good idea to keep 3.4 around in
> case some packages need it. It turns out that nothing is using it in our
> tree.
>
> Do we want to keep 3.4 and 3.5 around? There is a maintenance cost
> incurred at each new release, because their shared patches tend to
> diverge each time.
>
> If we should keep them, how should the package inheritance go? Now, it's
> like this:
>
> 2.7 < 3.5 < 3.4
>
> If we kept them all, should 3.5 and 3.4 both inherit 3.6?

Hi Leo!

I think python 3.x releases should inherit from the latest indeed. That
way changes to lower 3.x releases are guaranteed not to affect the
newest one.

No preference for keeping older releases around either. Unless any
python folks wants to maintain them, I think they can be dropped.

Perhaps we can use python-3.6 as the basis for a new "python-updates"
branch?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]