Re: [Python-Dev] Python 2.7 EOL date
On 8/23/2018 8:14 PM, Barry Warsaw wrote: On Aug 23, 2018, at 15:23, Eric V. Smith wrote: On 8/23/2018 4:30 PM, Victor Stinner wrote: Hi, The reference is the PEP 373 "Python 2.7 Release Schedule". See the "Update" section: https://www.python.org/dev/peps/pep-0373/#update We could probably make it more clear in this section and/or in https://www.python.org/dev/peps/pep-0373/#id4 that there will be no 2.7 releases of any kind after 2020-01-01: no bugfix, no security, and no source releases after that date. I'll whip something up if there's general agreement. +1 from me, but IIRC, Benjamin has said that the final 2.7 release may not happen *exactly* on January 1st (due to holidays and such), but that we should still consider that the “hammer date” when all support stops. We should get some confirmation from Benjamin (the 2.7 release manager) on the (tentative) exact final release date, and then codify that in the PEP. I’d be very happy if that, or say December 31 2019 were the actual last release date. Current: "Being the last of the 2.x series, 2.7 will have an extended period of maintenance. Specifically, 2.7 will receive bugfix support until January 1, 2020. All 2.7 development work will cease in 2020." Proposed, based on what Benjamin said last discussion: "Being the last of the 2.x series, 2.7 will have an extended period of bugfix and security maintenance until January 1, 2020. The final 2.7 release will be on or soon after that date." Anything more specific is up to Benjamin. -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python 2.7 EOL date
On 8/23/2018 2:53 PM, Collin Anderson wrote: Hi All, Sorry if this has been mentioned before, but I noticed the Python 2.7 EOL date was recently set to Jan 1st, 2020. My understanding was Python releases get 5 years of support from their initial release, '5' is a rounded, rather than exact, figure. and Python 2.7 was extended an additional 5 years. Python 2.7 was originally released on 2010-07-03, and with an original EOL of 2015-07-03. Extended 5 years, shouldn't the EOL be 2020-07-03? Think of it this way. In April 2015, after almost 5 years, support was extended for about 5 years, (primarily for build and security issues) to sometime in 2020, left intentionally vague. Based on more information, we recently specified the first day in 2020. Backporting of normal bugfixes is already very selective, and the selectivity may increase. Also, this statement is a little unclear to me: > Specifically, 2.7 will receive bugfix support until January 1, 2020. All 2.7 development work will cease in 2020. This statement makes it sound like bugfixes end on Jan 1st, but seems to leave open the possibility that security fixes could continue through the year. I agree that it is not clear that we actually meant 'final release on or soon after 2020 Jan 1". In other words, no substantive patches of any kind after that date. -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] make patchcheck and git path
I am trying to be a 'good scout' and run "make patchcheck" more regularly. However, I generally am not successful because I build and test in separate directories. There is access to git! just no ready reference in the build area. So, not calling it a bug - but if someone else also experiences this, and feels capable of makeing it more flexible - you will get thanks from me, in any case! Michael signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2018-08-17 - 2018-08-24)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open6807 (+31)
closed 39431 (+36)
total 46238 (+67)
Open issues with patches: 2707
Issues opened (48)
==
#34421: Cannot install package with unicode module names on Windows
https://bugs.python.org/issue34421 opened by julien.malard
#34422: __name__ not available for classes in typing module
https://bugs.python.org/issue34422 opened by Gabriel Tremblay
#34423: Overflow when casting from double to time_t, and_PyTime_t.
https://bugs.python.org/issue34423 opened by enedil
#34424: Unicode names break email header
https://bugs.python.org/issue34424 opened by _savage
#34426: "__lltrace__" seems to be wrong , "__ltrace__" is correct in
https://bugs.python.org/issue34426 opened by Nojima Takahide
#34427: calling MutableSequence.extend on self produces infinite loop
https://bugs.python.org/issue34427 opened by Naris R
#34428: tokenize
https://bugs.python.org/issue34428 opened by lkcl
#34429: On Windows tempfile.TemporaryFile behaves like NamedTemporaryF
https://bugs.python.org/issue34429 opened by dwich
#34430: Symmetrical chaining futures in asyncio.future.wrap_future
https://bugs.python.org/issue34430 opened by huji
#34431: Docs does not eval allows code object as argument
https://bugs.python.org/issue34431 opened by jfine2358
#34433: cancel all other pending child futures
https://bugs.python.org/issue34433 opened by tzongw
#34434: Removal of kwargs for built-in types not covered with "changed
https://bugs.python.org/issue34434 opened by andymaier
#34439: Expose venv --prompt value to an environment value
https://bugs.python.org/issue34439 opened by Tomer
#34442: zlib module not built on windows
https://bugs.python.org/issue34442 opened by steveire
#34443: enum repr should use __qualname__
https://bugs.python.org/issue34443 opened by doerwalter
#3: Module's __file__ should be absolute always ("." in sys.path)
https://bugs.python.org/issue3 opened by blueyed
#34445: asyncio support in doctests
https://bugs.python.org/issue34445 opened by Stefan Tjarks
#34446: ambiguous _max_size parameter in SpooledTemporaryFile
https://bugs.python.org/issue34446 opened by jcc2220
#34447: ttk.TreeView (and maybe other functions) is overzealous in con
https://bugs.python.org/issue34447 opened by abarnert
#34448: incomplete/missing message from configure.ac for usable wchar_
https://bugs.python.org/issue34448 opened by michael-o
#34449: HP aCC complains about invalid -fPIC on HP-UX
https://bugs.python.org/issue34449 opened by michael-o
#34450: improve shutil.make_archive
https://bugs.python.org/issue34450 opened by redstone-cold
#34451: docs: tutorial/introduction doesn't mention toggle of prompts
https://bugs.python.org/issue34451 opened by jfine2358
#34453: ipaddress module accepts some strange IPv6 addresses that it s
https://bugs.python.org/issue34453 opened by lkcl
#34455: Tkinter crashing when pressing Command + ^ (OSX)
https://bugs.python.org/issue34455 opened by iPodClassic
#34458: No way to alternate options
https://bugs.python.org/issue34458 opened by porton
#34459: email.contentmanager should use IANA encoding
https://bugs.python.org/issue34459 opened by era
#34460: email.charset: common IANA labels missing
https://bugs.python.org/issue34460 opened by era
#34461: Availability of parsers in etree initializer
https://bugs.python.org/issue34461 opened by nilanjan roy
#34463: Discrepancy between traceback.print_exception and sys.__except
https://bugs.python.org/issue34463 opened by Timothy McCurrach
#34464: There are inconsitencies in the treatment of True, False, None
https://bugs.python.org/issue34464 opened by jfine2358
#34465: ipaddress should accept bytearray in addition to bytes
https://bugs.python.org/issue34465 opened by joernheissler
#34466: socket.settimeout working incorrectly for connect() method of
https://bugs.python.org/issue34466 opened by Slon
#34467: No mechanism to abort created coroutine or suppress not-awaite
https://bugs.python.org/issue34467 opened by Sheng Zhong
#34470: windows msi in headless mode fails to install Script directory
https://bugs.python.org/issue34470 opened by cdknorow
#34472: zipfile: does not include optional descriptor signature
https://bugs.python.org/issue34472 opened by silas
#34475: functools.partial objects have no __qualname__ attribute
https://bugs.python.org/issue34475 opened by chris.jerdonek
#34476: asyncio.sleep(0) not documented
https://bugs.python.org/issue34476 opened by hniksic
#34478: Possibly misleading/wrong documentation about PyModuleDef.m_fr
https://bugs.python.org/issue34478 opened by Segev Finer
#34479: ArgumentParser subparser error display at the wrong level
https://bugs.python.org/issue34479 opened by siming85
#34480: _
Re: [Python-Dev] make patchcheck and git path
I don't quite understand the problem you're facing with git and make patchcheck? Also, perhaps this is more for core-workflow instead of python-dev. Mariatta ᐧ On Fri, Aug 24, 2018 at 3:20 AM Michael wrote: > I am trying to be a 'good scout' and run "make patchcheck" more > regularly. However, I generally am not successful because I build and > test in separate directories. > > There is access to git! just no ready reference in the build area. > > So, not calling it a bug - but if someone else also experiences this, > and feels capable of makeing it more flexible - you will get thanks from > me, in any case! > > Michael > > > ___ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/mariatta.wijaya%40gmail.com > ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] make patchcheck and git path
On Fri, Aug 24, 2018 at 1:22 PM Michael wrote: > > I am trying to be a 'good scout' and run "make patchcheck" more > regularly. However, I generally am not successful because I build and > test in separate directories. There is an open issue about supporting out-of-tree builds: https://bugs.python.org/issue32256 --Berker ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
