Mailman 3 June 2016 - python-committers

[RELEASED] Python 3.4.5 and Python 3.5.2 are now available
by Larry Hastings 28 Jun '16

28 Jun '16

On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm thrilled to announce the availability of Python 3.4.5 and Python 3.5.2. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. All changes made to Python 3.4 since Python 3.4.4 should be security fixes only; conventional bug fixes are not accepted. Also, Python 3.4.5 and all future releases of Python 3.4 will only be released as source code--no official binary installers will be produced. Python 3.5 is still in active "bug fix" mode. Python 3.5.2 contains many incremental improvements and bug fixes over Python 3.5.1. You can find Python 3.4.5 here: https://www.python.org/downloads/release/python-345/ And you can find Python 3.5.2 here: https://www.python.org/downloads/release/python-352/ Releasing software from 30,000 feet, //arry /p.s. There appears to be a small oops with the Windows installers for 3.5.2--uploaded to the wrong directory or something. They'll be available soon, honest!

3 5

Re: [python-committers] [Python-Dev] [RELEASED] Python 3.4.5 andPython 3.5.2 are now available
by R. David Murray 28 Jun '16

28 Jun '16

On Mon, 27 Jun 2016 12:51:07 -0700, Steve Dower <steve.dower(a)python.org> wrote: > I hoped by informing the lists we'll be able to address concerns as > they come up, but I'd rather not have a semi-permanent instruction to > ignore a virus scanner :) Good point. I actually thought about that a few hours after I sent the email :) --David

1 0

Here's what's going into 3.5.2 final and 3.4.5 final
by Larry Hastings 24 Jun '16

24 Jun '16

Heads up! This is a courtesy reminder from your friendly 3.4 and 3.5 release manager. Here's a list of all the changes since 3.5.2rc1 that are currently going into 3.5.2 final: * 155e665428c6 - Zachary: OpenSSL 1.0.2h build changes for Windows * cae0b7ffeb9f - Benjamin: fix % in Doc/whatsnew/3.5.rst that confuses latex * 783dfd77e4c1 - Terry Reed: allow non-ascii in idlelib/NEWS.txt * <new revision> - Matthias: fix for test_ssl test_options on Ubuntu 3.4.5 final only has one change from 3.4.5rc1: the test_ssl test_options fix from Matthias. If there's something else that needs to go into one of these releases, and it's not on the list above, speak up now. I may actually tag these late Friday as I'm traveling Saturday. So you have approximately, let's say 20 hours from when I post this. Thanks, //arry/

4 4

The peps repo is now on GitHub!
by Brett Cannon 16 Jun '16

16 Jun '16

I don't think anything has fallen over, so I'm calling this a successful migration! The peps repo is now https://github.com/python/peps . I have given the Python core team on GitHub write access to the repository so people can add/update their own PEPs. There is also an issue tracker there, seeded with some enhancements we could make to have the PEPs be nicer to work with. I should also mention that the CLA bot is turned on for this repo as per our lawyer's advice, so people will need to have signed the CLA and have their GitHub username associated with their bugs.python.org account to have their pull request cleared for acceptance. And can someone delete hg.python.org/peps?

6 9

Please do not commit to the peps repo
by Brett Cannon 15 Jun '16

15 Jun '16

We will begin the migration process in about an hour. Once it's over and everything is set I'll email again and give the all clear to start using https://github.com/python/peps instead of hg.python.org/peps.

1 0

Python 3.6.0a2 is now available
by Ned Deily 13 Jun '16

13 Jun '16

On behalf of the Python development community and the Python 3.6 release team, I'm happy to announce the availability of Python 3.6.0a2. 3.6.0a2 is the first of four planned alpha releases of Python 3.6, the next major release of Python. During the alpha phase, Python 3.6 remains under heavy development: additional features will be added and existing features may be modified or deleted. Please keep in mind that this is a preview release and its use is not recommended for production environments. You can find Python 3.6.0a2 here: https://www.python.org/downloads/release/python-360a2/ The next release of Python 3.6 will be 3.6.0a3, currently scheduled for 2016-07-11. Enjoy! --Ned -- Ned Deily nad(a)python.org -- []

1 0

Hold off on 3.5 pushes for the moment
by Ned Deily 13 Jun '16

13 Jun '16

It looks like there's a little bit of merging cleanup that needs to be done following the 3.4.0rc1 and 3.5.0rc1 tagging and releasing. Until Larry has a chance to take care of it, it would be best to hold off pushing things to the 3.5 (or 3.4 security) branches. Thanks! --Ned -- Ned Deily nad(a)python.org -- []

1 1

[RELEASED] Python 3.4.5rc1 and Python 3.5.2rc1 are now available
by Larry Hastings 12 Jun '16

12 Jun '16

On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm pleased to announce the availability of Python 3.4.5rc1 and Python 3.5.2rc1. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. All changes made to Python 3.4 since Python 3.4.4 should be security fixes only; conventional bug fixes are not accepted. Also, Python 3.4.5rc1 and all future releases of Python 3.4 will only be released as source code--no official binary installers will be produced. Python 3.5 is still in active "bug fix" mode. Python 3.5.2rc1 contains many incremental improvements over Python 3.5.1. Both these releases are "release candidates". They should not be considered the final releases, although the final releases should contain only minor differences. Python users are encouraged to test with these releases and report any problems they encounter. You can find Python 3.4.5rc1 here: https://www.python.org/downloads/release/python-345rc1/ And you can find Python 3.5.2rc1 here: https://www.python.org/downloads/release/python-352rc1/ Python 3.4.5 final and Python 3.5.2 final are both scheduled for release on June 26th, 2016. Happy Pythoneering, //arry/

1 0

bugs.python.org, job status, and contributors (aka not core devs)
by Ethan Furman 12 Jun '16

12 Jun '16

Question: I noticed a couple issues on b.p.o that were being closed by contributors (not core-devs, not their own issues). Should non-core-devs be closing issues that do not belong to them? -- ~Ethan~

7 9

Reminder: 3.6.0a2 snapshot 2016-06-13 12:00 UTC
by Ned Deily 10 Jun '16

10 Jun '16

Just a quick reminder that the next alpha snapshot for the 3.6 release cycle is coming up in a couple of days. This is the second of four alphas we have planned. Alpha 2 follows the development sprints at the PyCon US 2016 in Portland. Thanks to all of you who were able to be there and contribute! And to all of you who continue to contribue from afar. While there are still plenty of proposed patches awaiting review, nearly 300 commits have been pushed to the default branch (for 3.6.0) in the four weeks since alpha 1. As a reminder, alpha releases are intended to make it easier for the wider community to test the current state of new features and bug fixes for an upcoming Python release as a whole and for us to test the release process. During the alpha phase, features may be added, modified, or deleted up until the start of the beta phase. Alpha users beware! Also note that Larry has announced plans to do a 3.5.2 release candidate sometime this weekend and Benjamin plans to do a 2.7.12 release candidate. So get important maintenance release fixes in ASAP. Looking ahead, the next alpha release, 3.6.0a3, will follow in about a month on 2016-07-11. 2016-06-13 ~12:00 UTC: code snapshot for 3.6.0 alpha 1 now to 2016-09-07: Alpha phase (unrestricted feature development) 2016-09-07: 3.6.0 feature code freeze, 3.7.0 feature development begins 2016-09-07 to 2016-12-04: 3.6.0 beta phase (bug and regression fixes, no new features) 2016-12-04 3.6.0 release candidate 1 (3.6.0 code freeze) 2016-12-16 3.6.0 release (3.6.0rc1 plus, if necessary, any dire emergency fixes) --Ned P.S. Just to be clear, this upcoming alpha snapshot will *not* contain a resolution for 3.6.0 of the current on-going discussions about the behavior of os.urandom(), the secrets module, and friends (Issue26839, Issue27288, et al). I think the focus should be on getting 3.5.2 settled and then we can decide on and implement any changes for 3.6.0 in an upcoming alpha prior to beta 1. https://www.python.org/dev/peps/pep-0494/ -- Ned Deily nad(a)python.org -- []

1 0