[Python-Dev] Re: The Python 2 death march
Regardless of the date of the final release, no one's Python2 install will stop working, and people will still be able to download and install that last release. So I like the metaphor -- it's being "sunset" -- there will be a long dusk .. a month or tow makes no difference to anyone's workflow. -CHB On Fri, Sep 13, 2019 at 6:39 PM Sumana Harihareswara wrote: > Hi. I've joined python-dev to participate in this thread (I don't have > email delivery turned on; I'll be checking back via the web). > > Benjamin, I am sorry that I didn't check in with you, and assumed that > January 1, 2020 would be the the date of the final 2.7 point release. > (My understanding was based on Guido's EOL announcement from March last > year https://mail.python.org/pipermail/python-dev/2018-March/152348.html > -- I should have also gotten a review from you and not just the > Steering Council in https://github.com/python/steering-council/issues/14 > .) I'm going to continue this discussion here so I can make sure I > understand the policy decision properly, and then (if necessary) update > the FAQ. > > Based on what I've read here and what I see in > https://www.python.org/dev/peps/pep-0373/#maintenance-releases , it > sounds like the timeline will go something like: > > * 2019-10-19: release of 2.7.17 October > * October, November, and December 2019: developers continue to fix > issues in 2.7 > * 2020-01-01: code freeze for 2.7.18 release candidate > * January and February 2020: flexibility to fix any issues introduced > since the 2.7.17 release, but no other bugs or security issues, and no > 3.x backports > * ~2020-04-02: release candidate for 2.7.18 > * 2020-04-17: final 2.7.18 release > > Is this right? (If so, I can submit an update to PEP 373.) > > This is a little more complicated than I had anticipated when > communicating out about the sunsetting. But I can find a way either to > concisely communicate this, or to point to a user-friendly explanation > elsewhere. > > Thanks. > > -- > Sumana Harihareswara > Changeset Consulting > https://changeset.nyc > ___ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/MXCGMTXDY7BX6JBBU36O5YFRWWBB3NQE/ > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR(206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/QM5B2SH5URWHF4WEWJ33KM4CXZA4QMFB/
[Python-Dev] Re: urllib request HTTPS memory leak?
On 16/09/2019 23.37, V-ron P wrote: > Hello Python Dev, > > One of my HTTPS servers leaked over 8 GB of memory over the past week. > After troubleshooting the issue, I managed to narrow it down to the > minimal test case below: > > https://gist.github.com/hydrogen-mvm/d588521c2138e0f98aa94b18e7dedfdb > > (Note that the 100 threads are not necessary, but they help exaggerate > and accelerate the memory leaking.) > > The memory leak happens if I send a HTTPS request, regardless if it's > GET or POST. The most bizarre part is the destination address does > -not- need to exist and it still leaks! (In the script above it points > to a non-existent HTTPS server on your localhost.) > > This leak does not happen for HTTP (plaintext) requests, which suggests > that the bug might be SSL-related. > > My OS is Windows 7 and my Python version is: > > Python 3.7.4 (tags/v3.7.4:e09359112e, Jul 8 2019, 20:34:20) [MSC v.1916 > 64 bit (AMD64)] on win32 > > A friend of mine tested the script on his Windows 10 machine and also > experienced the same memory leaking effect. > > Please confirm if this is in fact a bug in Python or this is a bug in my > environment. Thanks. Yes, we are aware of a memory leak on Windows. A recent change has caused a memory leak and performance regression in the Windows-only part of the ssl module. The bug is fixed in 3.7 branch but not yet released. See https://bugs.python.org/issue37702 and https://bugs.python.org/issue35941 for more details. As a workaround I suggest that you create a single SSLContext with ssl.create_default_context() and reuse the context in all HTTP queries. You can share the context across threads w/o locking and use it for all HTTPS connections. A single SSLContext is also more efficient. Christian ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/CYKQCXVPJBFGUDMEE7QFQ5EWQF3LUJDG/
[Python-Dev] urllib request HTTPS memory leak?
Hello Python Dev, One of my HTTPS servers leaked over 8 GB of memory over the past week. After troubleshooting the issue, I managed to narrow it down to the minimal test case below: https://gist.github.com/hydrogen-mvm/d588521c2138e0f98aa94b18e7dedfdb (Note that the 100 threads are not necessary, but they help exaggerate and accelerate the memory leaking.) The memory leak happens if I send a HTTPS request, regardless if it's GET or POST. The most bizarre part is the destination address does -not- need to exist and it still leaks! (In the script above it points to a non-existent HTTPS server on your localhost.) This leak does not happen for HTTP (plaintext) requests, which suggests that the bug might be SSL-related. My OS is Windows 7 and my Python version is: Python 3.7.4 (tags/v3.7.4:e09359112e, Jul 8 2019, 20:34:20) [MSC v.1916 64 bit (AMD64)] on win32 A friend of mine tested the script on his Windows 10 machine and also experienced the same memory leaking effect. Please confirm if this is in fact a bug in Python or this is a bug in my environment. Thanks. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/HE4PXCWWDODJ6PHRUOZXSYCHMM53S3PN/
