Bug 522322 – dev-lang/python-3.4.1 stabilization

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Mike Gilbert 2014-09-07 18:03:02 UTC]

I would like to start the process of stabilizing python:3.4.

For local testing, please unmask the python_targets_python3_4 use flag and set PYTHON_TARGETS="python2_7 python3_4" in make.conf.

Please report your testing results here, but do not commit the keywords yet.

Ideally, I would like to commit most if not all stable keywords at the same time, as well as change PYTHON_TARGETS in the base profile.

Releng: If you would like to do some catalyst testing, please do so.

[Comment 1 Mike Gilbert 2014-09-07 18:04:16 UTC]

Adding archs.

[Comment 2 Jeroen Roovers (RETIRED) 2014-09-13 05:44:25 UTC]

HPPA is OK.

Shouldn't it be fine to just stabilise now and do the profile changes later?

[Comment 3 Mike Gilbert 2014-09-21 22:40:34 UTC]

(In reply to Jeroen Roovers from comment #2)
> Shouldn't it be fine to just stabilise now and do the profile changes later?

Then people will end up with both python3.4 and python3.3 installed, but none of their third party python libs will be installed for python3.4.

It's doable, but a little confusing.

[Comment 4 Jeroen Roovers (RETIRED) 2014-09-26 10:08:38 UTC]

Stable for HPPA.

[Comment 5 Markus Meier 2014-09-30 19:38:52 UTC]

dev-lang/python-3.4.1 builds fine on arm. To really test python packages, newer versions of dev-python/pytest (2.6.1) and thus dev-python/py (1.4.23) are required. Current stable pytest doesn't support python-3.4...

[Comment 6 Agostino Sarubbo 2014-10-10 15:31:12 UTC]

amd64 stable

[Comment 7 Agostino Sarubbo 2014-10-12 09:00:29 UTC]

x86 stable

[Comment 8 Leif Biberg Kristensen 2014-10-13 17:25:49 UTC]

I'm running (mostly) stable amd64, and fail to see why I should have to unmask packages in order to upgrade to python 1.4:

The following keyword changes are necessary to proceed:
 (see "package.accept_keywords" in the portage(5) man page for more details)
# required by dev-python/pygobject-2.28.6-r55
# required by dev-python/pygtksourceview-2.10.1-r1
# required by dev-vcs/git-2.0.4[python,gtk]
# required by app-portage/layman-2.0.0-r3[git]
# required by @selected
# required by @world (argument)
=dev-lang/python-exec-2.9999 **
# required by dev-python/pygments-1.6_p20140324-r1
# required by dev-python/docutils-0.12
# required by media-video/mplayer2-2.0_p20130428-r1
# required by @selected
# required by @world (argument)
=dev-python/setuptools-6.1 ~amd64

[Comment 9 Mike Gilbert 2014-10-13 18:10:13 UTC]

(In reply to Leif Biberg Kristensen from comment #8)
> I'm running (mostly) stable amd64, and fail to see why I should have to
> unmask packages in order to upgrade to python 1.4:

The python_targets_python3_4 use flag is stable masked, which means it is forcibly disabled for any package which you do not have in package.keywords.

You can either add the necessary dependencies to package.keywords, or unmask the use flag.

At some point (hopefully soon) we will remove the stable mask and this will not be a problem any longer.

[Comment 10 Leif Biberg Kristensen 2014-10-13 18:49:21 UTC]

In other words, for now I can simply ignore the suggestion to update my PYTHON_TARGETS?

That sounds rather confusing, and I guess it could need some clarification eg. in the form of a portage news item.

[Comment 11 Mike Gilbert 2014-10-13 18:55:30 UTC]

(In reply to Leif Biberg Kristensen from comment #10)
> In other words, for now I can simply ignore the suggestion to update my
> PYTHON_TARGETS?
> 
> That sounds rather confusing, and I guess it could need some clarification
> eg. in the form of a portage news item.

I noted this problem in comment 3. The arch teams chose to mark it stable, despite my warning.

I'm not cleaning up after them.

[Comment 12 Steve L 2014-10-13 21:47:55 UTC]

(In reply to Mike Gilbert from comment #11)
> I'm not cleaning up after them.

That's perfectly fair.

> The python_targets_python3_4 use flag is stable masked, which means it is
> forcibly disabled for any package which you do not have in package.keywords.
> 
> You can either add the necessary dependencies to package.keywords, or unmask
> the use flag.

Just for clarification: to unmask the USE flag, we use:
mkdir -p /etc/portage/profile
echo '-python_targets_python3_4' >> /etc/portage/profile/use.stable.mask

Is that correct?

(I don't actually want to do it myself; I just think we should give users clear instructions on how to do it, should they need to, so they don't have to deal with a clusterfsck of package unmasking. And I've never had to tweak that file.)

[Comment 13 Mike Gilbert 2014-10-13 22:31:02 UTC]

(In reply to Steve L from comment #12)
> Just for clarification: to unmask the USE flag, we use:
> mkdir -p /etc/portage/profile
> echo '-python_targets_python3_4' >> /etc/portage/profile/use.stable.mask
> 
> Is that correct?

Yup, with one additional item:

echo 5 > /etc/portage/profile/eapi

[Comment 14 Dirkjan Ochtman (RETIRED) 2014-10-15 09:53:47 UTC]

Mike, I'm happy to work on some user-facing explanation of what going on provided you can give the promised braindump. Can you also provide data on what exactly is making the current stabilization process broken? Maybe we can come up with some ideas to improve on it.

[Comment 15 Agostino Sarubbo 2014-10-18 14:56:19 UTC]

ppc stable

[Comment 16 Agostino Sarubbo 2014-10-27 16:07:32 UTC]

ppc64 stable

[Comment 17 Agostino Sarubbo 2014-10-28 10:59:01 UTC]

ia64 stable

[Comment 18 Agostino Sarubbo 2014-10-29 09:33:42 UTC]

sparc stable

[Comment 19 Agostino Sarubbo 2014-11-02 09:04:29 UTC]

alpha stable

[Comment 20 Michał Górny 2014-11-09 15:09:59 UTC]

Removing unstable arches. This leaves us with just arm@ slacking :).

[Comment 21 Markus Meier 2014-11-11 21:01:24 UTC]

(In reply to Michał Górny from comment #20)
> Removing unstable arches. This leaves us with just arm@ slacking :).

arm stable... pretty useless stabilization w/o profile/target updates :)
closing.