Please feel free to edit the change proposal. I also fully agree to the proposal you made
at the link you provided. Currently I have in copr the first beta, and also I can build
the second beta as well if I exclude the ensurepip test.
I was actually thinking of adding python 3.6 in rawhide when rc1 was released, but if that
is too late, which pre-release would be ideal to be built in rawhide?
Associate Software Engineer
Python Maintenance Team, Red Hat
----- Original Message -----
From: "Nick Coghlan" <ncoghlan(a)gmail.com>
To: "Fedora Python SIG" <python-devel(a)lists.fedoraproject.org>
Sent: Wednesday, October 12, 2016 8:29:04 AM
Subject: Python 3.6 beta release in F26 Rawhide?
During the discussion of the os.urandom() change in Python 3.6 (the
successor to the accidental change in Python 3.5 that is the subject
of Tomas's emailing about rebasing to 3.5.2 in F24), we came to the
conclusion it would be good to get 3.6 into Rawhide early enough to
impact the upstream beta cycle:
However, there's no reference to that discussion in
- it only refers to
incorporating a release candidate or the actual release, which will be
too late for us to request changes to the upstream default
os.urandom() behaviour if we find unexpected problems with it.
With Python 3.6b2 recently pushed out the door, there's about two
months (including two more beta releases) until the first release
candidate in early December.
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
python-devel mailing list -- python-devel(a)lists.fedoraproject.org
To unsubscribe send an email to python-devel-leave(a)lists.fedoraproject.org