Maciej has been helping Ezio, David, and me out with updates to
bugs.python.org for the GitHub migration and he's reached a point where we
are all comfortable with him making updates to the issue tracker's code
without us holding him up. He knows not to commit to Python itself or other
repos.
Just a reminder: I'll be tagging 3.5.3 rc1 and 3.4.6 rc1 tomorrow, Jan 1
2017, sometime between 24 and 36 hours from now. Please work quickly if
there's anything you need to get in to either of those releases. I'm
hoping that, for once, there are literally no code changes between rc1
and final.
Best wishes for a happy new year,
//arry/
On behalf of the Python development community and the Python 3.6 release
team, I am pleased to announce the availability of Python 3.6.0. Python
3.6.0 is the newest major release of the Python language, and it contains
many new features and optimizations. See the "What’s New In Python 3.6"
document for more information:
https://docs.python.org/3.6/whatsnew/3.6.html
You can download Python 3.6.0 here:
https://www.python.org/downloads/release/python-360/
Also, most third-party distributors of Python should be making 3.6.0
packages available soon.
Maintenance releases for the 3.6 series will follow at regular intervals
starting in the first quarter of 2017.
We hope you enjoy Python 3.6.0!
P.S. As a volunteer-staffed open source project, we could not bring
Python releases to you without the enormous contributions of many,
many people. Thank you to all who have contributed and reviewed code
and documentation changes, documented and investigated bugs, tested
Python and third-party packages, and provided and supported the
infrastructure needed to support Python development and testing.
Please consider supporting the work of the Python Software Foundation.
More at:
https://www.python.org/psf-landing/
--
Ned Deily
nad(a)python.org -- []
Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and
3.4.6 to ship about a month after 3.6.0 did, to "let the dust settle"
around the release. I expect a flood of adoption of 3.6, and people
switching will find bugs, and maybe those bugs are in 3.5 or 3.4. So it
just seemed sensible.
3.6 just slipped by two weeks. So now there's less than two weeks
between 3.6.0 final shipping and tagging the release canddiates for
3.5.3 and 3.4.6. This isn't as much time as I'd like.
If I had total freedom to do as I liked, I'd slip my releases by two
weeks to match 3.6. But there might be people planning around 3.5.3 and
3.4.6--like Guido was waiting for 3.5.3 for something iirc.
So, if you have an opinion, please vote for one of these three options:
* Don't slip 3.5.3. and 3.4.6.
* Slip 3.5.3 and 3.4.6 by two weeks to match 3.6.0.
* Slip 3.5.3 and 3.4.6 by a whole month, to give 3.6.0 the ability to
slip again without us having to change the release.
Your faithful servant,
//arry/
Hey all,
I heard some of you wanted MSDN subscription renewals from Santa
Claus, so I can take care of that and put in a good word for you. If
you're an existing subscriber I just need the email and subscriber ID
for your account, which you can get out of some of the emails they
send you, or via
https://msdn.microsoft.com/en-us/subscriptions/manage/.
If you don't have a subscription and would like access to various
Microsoft tools to help you make Python better, e.g., Visual Studio,
Windows images, etc., they give us complimentary access to the
Microsoft Developer Network to enable that. Each subscription gets you
one year of access to download those tools (plus some amount of Azure
credit), and they give us continued renewals as long as we're using
them and making Python better. If you'd like a subscription for the
first time, I need the following info:
First Name:
Last Name:
Email Address:
Project/Company: Python Software Foundation
Complete Mailing Address:
Phone Number:
I'd like to batch these up so it makes things easier on the folks at
Microsoft who help us out with this, so get me your details and I'll
send a batch next week on the 28th, and any batches after that I'll
just gauge by how many are coming in.
Thanks,
Brian
On Mon, 19 Dec 2016 at 06:29 Terry Reedy <tjreedy(a)udel.edu> wrote:
> On 12/19/2016 12:26 AM, Larry Hastings wrote:
> >
> >
> > Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and
> > 3.4.6 to ship about a month after 3.6.0 did, to "let the dust settle"
> > around the release. I expect a flood of adoption of 3.6, and people
> > switching will find bugs, and maybe those bugs are in 3.5 or 3.4. So it
> > just seemed sensible.
> >
> > 3.6 just slipped by two weeks. So now there's less than two weeks
> > between 3.6.0 final shipping and tagging the release canddiates for
> > 3.5.3 and 3.4.6. This isn't as much time as I'd like.
> >
> > If I had total freedom to do as I liked, I'd slip my releases by two
> > weeks to match 3.6. But there might be people planning around 3.5.3 and
> > 3.4.6--like Guido was waiting for 3.5.3 for something iirc.
> >
> > So, if you have an opinion, please vote for one of these three options:
> >
> > * Don't slip 3.5.3. and 3.4.6.
>
> I am mildly in favor of this. There are already known bugs in 3.5 that
> will not get fixed, no matter how long you delay the final maintenance
> release. There are even bugs left in 2.7 after 6 years of fixing. In
> the meanwhile, it is a mild nuisance to have 3 3.x maintenance branches
> open.
>
> I don't know when Brett will move us to GIT and how that might impact
> the timing.
>
Slipping doesn't affect me yet as all the pieces are still not quite in
place. So a shift in release just shifts the blackout period for the week
prior to the 3.5.3 release.
On behalf of the Python development community and the Python 3.6 release
team, I would like to announce the availability of Python 3.6.0rc2. 3.6.0rc2
is the second release candidate for Python 3.6, the next major release of
Python.
Code for 3.6.0 is now frozen. 3.6.0rc2 is the same code base as the first
release candidate, 3.6.0rc1, with the addition of fixes for a couple of
critical problems and with some documentation additions and updates.
Assuming no further release critical problems are found prior to the 3.6.0
final release date, now planned for 2016-12-23, the 3.6.0 final release
will be the same code base as this 3.6.0rc2. Maintenance releases for the
3.6 series will follow at regular intervals starting in the first quarter
of 2017.
Among the new major new features in Python 3.6 are:
* PEP 468 - Preserving the order of **kwargs in a function
* PEP 487 - Simpler customization of class creation
* PEP 495 - Local Time Disambiguation
* PEP 498 - Literal String Formatting
* PEP 506 - Adding A Secrets Module To The Standard Library
* PEP 509 - Add a private version to dict
* PEP 515 - Underscores in Numeric Literals
* PEP 519 - Adding a file system path protocol
* PEP 520 - Preserving Class Attribute Definition Order
* PEP 523 - Adding a frame evaluation API to CPython
* PEP 524 - Make os.urandom() blocking on Linux (during system startup)
* PEP 525 - Asynchronous Generators (provisional)
* PEP 526 - Syntax for Variable Annotations (provisional)
* PEP 528 - Change Windows console encoding to UTF-8
* PEP 529 - Change Windows filesystem encoding to UTF-8
* PEP 530 - Asynchronous Comprehensions
Please see "What’s New In Python 3.6" for more information:
https://docs.python.org/3.6/whatsnew/3.6.html
You can find Python 3.6.0rc2 here:
https://www.python.org/downloads/release/python-360rc2/
Note that 3.6.0rc2 is still a preview release and thus its use is not
recommended for production environments.
More information about the release schedule can be found here:
https://www.python.org/dev/peps/pep-0494/
--
Ned Deily
nad(a)python.org -- []
Hi all!
Today (2016-12-16) has long been our planned release date for 3.6.0 final. So far most of the feedback from users testing the preview versions of 3.6.0 has been very positive. We made it to the next-to-final milestone, the 3.6.0rc1 release candidate, 10 days ago with hopes of going directly to the final release. Alas, in the last few days at least one outstanding issue that we had hoped would not be a real-world problem has proven to be a showstopper during third-party package testing and I have been persuaded that we do need to fix it before 3.6.0 final. I take responsibility and apologize for not ensuring it was resolved earlier in the release cycle; I'll try to do better next time. Therefore, we are going to produce a second release candidate. Besides the showstopper fix (#28147), I've cherrypicked a few requested build fixes and, as promised, some last-minute documentation updates and additions. I'm also expecting to cherrypick at least one more asynchio fix before tagging and manufacturing 3.6.0rc2 sometime later today (i.e. within the next 24 hours). Assuming that is accomplished, we will be looking for quick feedback to ensure that we have addressed the problems and have not introduced any new ones. Then, assuming all goes well and no new showstoppers are found, we plan to release 3.6.0 final on Friday 2016-12-23, a week from now.
Also note that there is no change in the status of the cpython repo branches. Continue to push appropriate changes to the 3.6 branch for the 3.6.1 maintenance release and to the default branch for the next feature release, 3.7.0. Should you run into a potential showstopper problem for 3.6.0, please make sure there is an open issue for it on the bug tracker marked as "release blocker", work to getting a fix pushed to the 3.6 branch for 3.6.1, and contact me ASAP to discuss potential cherrypicking. Please do the same for any necessary important documentation fixes for 3.6.0 final. As before, my goal will be to have no new changes after the release candidate.
Thank you all again for your great efforts and co-operation throughout the 3.6 development cycle! We are oh-so-close to getting your work officially out there.
--Ned
P.S. Happy Beethoven's Birthday
FYI: Here is a list of the post 3.6.0rc1 changesets that have been cherrypicked so far for 3.6.0rc2. There will likely be at least one more. (Note, the description and files list below for some changesets may be truncated.)
user: Yury Selivanov <yury(a)magic.io>
date: Wed Dec 07 16:19:56 2016 -0800
files: Doc/whatsnew/3.6.rst
description:
Issue #28635: Drop the note that whatsnew is incomplete
user: Ned Deily <nad(a)python.org>
date: Wed Dec 07 23:37:12 2016 -0500
files: Doc/tools/templates/indexsidebar.html
description:
Issue #28900: Update documentation sidebar for 3.6.0rc.
user: Benjamin Peterson <benjamin(a)python.org>
date: Wed Dec 07 23:54:28 2016 -0800
files: Include/pyport.h
description:
guard HAVE_LONG_LONG definition to prevent redefinition (#28898)
[prevent gdb build errors with 3.6.0]
user: Steve Dower <steve.dower(a)microsoft.com>
date: Wed Dec 07 13:02:27 2016 -0800
files: Doc/library/importlib.rst Doc/using/windows.rst Doc/whatsnew/3.6.rst Misc/NEW
description:
Issue #28896: Deprecate WindowsRegistryFinder
user: Steve Dower <steve.dower(a)microsoft.com>
date: Sun Dec 11 14:48:32 2016 -0800
files: Tools/msi/distutils.command.__init__.py Tools/msi/distutils.command.bdist_win
description:
Issue #28783: Replaces bdist_wininst in nuget packages with stub
user: Yury Selivanov <yury(a)magic.io>
date: Mon Dec 12 16:44:58 2016 -0500
files: Doc/library/asyncio-protocol.rst Doc/whatsnew/3.6.rst
description:
Issue #28089: Document TCP_NODELAY in asyncio
user: Victor Stinner <victor.stinner(a)gmail.com>
date: Thu Dec 15 16:20:53 2016 +0100
files: Doc/whatsnew/3.6.rst
description:
Issue #28979: Fix What's New in Python 3.6, dict
user: Victor Stinner <victor.stinner(a)gmail.com>
date: Thu Dec 15 17:21:23 2016 +0100
files: Lib/test/test_dict.py Misc/NEWS Modules/_testcapimodule.c Objects/dictobject.
description:
Issue #28147: Fix a memory leak in split-table dictionaries: setattr() must not
convert combined table into split table. Patch written by INADA Naoki.
user: Yury Selivanov <yury(a)magic.io>
date: Thu Dec 15 17:36:05 2016 -0500
files: Doc/glossary.rst Doc/library/asyncio-eventloop.rst Doc/library/inspect.rst [...]
description:
Issue #28091: Document PEP 525 & PEP 530.
user: Yury Selivanov <yury(a)magic.io>
date: Thu Dec 15 17:56:43 2016 -0500
files: Doc/whatsnew/3.6.rst
description:
Issue #28635: asyncio-related fixes and additions. [docs only]
user: Yury Selivanov <yury(a)magic.io>
date: Thu Dec 15 18:58:19 2016 -0500
files: Doc/library/asyncio.rst
description:
docs: asyncio is no longer provisional
user: Ned Deily <nad(a)python.org>
date: Thu Dec 15 23:20:48 2016 -0500
files: Misc/NEWS
description:
Issue #28898: add Misc/NEWS entry
--
Ned Deily
nad(a)python.org -- []
Here's the release schedule for Python versions 3.5.3 and 3.4.6.
Sun Jan 1st, 2017 - tag 3.5.3rc1and 3.4.6rc1
Mon Jan 2nd, 2017 - release 3.5.3rc1and 3.4.6rc1
Sun Jan 15th, 2017 - tag 3.5.3 finaland 3.4.6final
Mon Jan 16th, 2017 - release 3.5.3 finaland 3.4.6final
The 3.5 branch is still in maintenance mode. I don't plan to transition
it to security-fixes-only mode until 3.6 has been out for a while (e.g.
once 3.6.1 comes out). So 3.5.3 will be released both with source code
and binary installers for Windows and OS X.
The 3.4 branch is already in security-fixes-only mode, and 3.4.6 will be
a source-code-only release.
Looking forward to {next_python_version} in {days_until_release},
//arry/
