Perhaps (un)related, is the release schedule for 3.5.3 set yet? (I'm holding off putting a new version of typing.py on typeshed until that's out.) On Mon, Nov 28, 2016 at 10:36 AM, Serhiy Storchaka <storchaka at gmail.com> wrote: > On 28.11.16 09:06, Benjamin Peterson wrote: > >> I've have just updated PEP 373 to say that Python 2.7.13 release >> candidate 1 will be released on December 3. The final will follow two >> weeks later on December 17. If there are delays in the process, the >> final will likely to pushed into January. >> > > Could it be delayed until 3.6.0 released? I paused fixing non-critical and > non-documentation bugs while 3.6 in pre-release stage and this could > include bugs that affect 2.7. > > In additional, we always receive increased number of bug reports in the > first one or two weeks after releasing new Python version. Some of these > reports are about regressions introduced by bugfixes. If delay bugfix > releases after new version release, we could fix regressions caused by > backported bugfixes and make bugfix releases more reliable. > > > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido% > 40python.org > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20161128/7372f8b0/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4