[gentoo-dev-announce] Re: [gentoo-dev] Python 3.5 is in, Python 3.3 deprecation

[gentoo-dev-announce] Re: [gentoo-dev] Python 3.5 is in, Python 3.3 deprecation

[Michał Górny]

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

(putting this on announcement board since it seems to be a major
misunderstanding that causes a lot of extra work)

Dnia 2015-10-04, o godz. 10:11:48
Mike Gilbert <floppym@gentoo.org> napisał(a):

> Python 3.5 has been added to ~arch this morning. Please feel free to
> test and add python3_5 to PYTHON_COMPAT as appropriate.

Please do not revbump packages unnecessarily, and do not drop keywords
when adding python3.5 support unless it is absolutely necessary.
The relevant USE flags are stable-masked, so it's completely correct to
add it to PYTHON_COMPAT on stable packages.

The only reason to drop stable keywords and revbump is if you have to
patch the package in order to fix python3.5 support. However, this
still does not require dropping of ~arch keywords, so please do not do
that.

If a dependency of your package has lost keywords due to a version
bump, please try adding python3.5 support to the older version
of the dependency rather than removing keywords from reverse
dependencies.

Also please note that we've just fixed keywords on a lot of Python
packages. So in case you see some keyword mis-sync, please update your
checkout first.

> Also, to keep the number of supported implementations manageable, I
> would like to deprecate Python 3.3. This means that it should not be
> added to PYTHON_COMPAT in new packages. Does anyone object to this, or
> have some reason we should keep it as "supported"?

A minor clarification here too: please avoid adding it to new packages
(unless really required -- e.g. python3.4 completely unsupported) but
please *do not* remove it from existing packages yet.

Implementation removal always carries huge reverse dependency problems.
This is why we keep the implementation deprecated until it's ready to
go, and then package.use.mask the relevant flag and afterwards remove
it via eclass. This way, the removal is atomic and developers don't
have to work hard on keeping dependency tree sane.

> See the wiki for the current status of python implementations.
> 
> https://wiki.gentoo.org/wiki/Project:Python/Implementations

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]