Re: [Python-Dev] Python 2.7 EOL date
I was operating under the optimistic assumption whatever the precise time of 2.7's official demise would only be an amusing piece of trivia for a world of happy Python 3 users. It's still to early to promise exact release dates; that will depend on the day-to-day schedules of the release manager and binary builders circa January 2020. A conservative assumption is that no 2.7 changes that land after December 31 2019 will ever be released. We could make the last release of 2.7 in July 2020. But what does that buy anyone? On Thu, Aug 23, 2018, at 11:53, 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, 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? > > 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. > > Thanks! > Collin > ___ > 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/benjamin%40python.org ___ 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-checkins] bpo-34171: Prevent creating Lib/trace.cover when run the trace module. (GH-8841)
On Sat, Aug 25, 2018 at 1:28 AM Serhiy Storchaka wrote: > > https://github.com/python/cpython/commit/c406d5cd74002964a64c3eb7d9e2445a7fd3a03f > commit: c406d5cd74002964a64c3eb7d9e2445a7fd3a03f > branch: master > author: Serhiy Storchaka > committer: GitHub > date: 2018-08-25T10:27:55+03:00 > summary: > > bpo-34171: Prevent creating Lib/trace.cover when run the trace module. > (GH-8841) > > files: > A Misc/NEWS.d/next/Library/2018-08-21-00-29-01.bpo-34171.6LkWav.rst > M Lib/test/test_trace.py > M Lib/trace.py This change seems to have caused most buildbots to go red. ___ 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] Python REPL doesn't work on Windows over remote powershell session (winrm)
Hello dears Python devs, I'm taking the initiative of writing to you for a question on Python REPL over Windows remote powershell session (winrm). As we’ve all known, Python REPL works well on local Linux, local Windows, and remote SSH session. But for the remote Windows powershell session the REPL doesn’t work, when I type ‘’python” on the remote session, there’s nothing happened. === Steps to reproduce # 1/ pre-install python on server1 (server 1 is a windows os) # 2/ from a powershell console on server0, type below 2 commands: enter-pssession server1 python Expected behavior # The python >>> prompt appears Actual behavior # Nothing, it is still the powershell prompt === The problem impacts all the python versions and all the windows versions. This make me (and other windows guys) unable to use Python remotely, especially for the Windows Server Core version, which is a headless version (no GUI, so no remote desktop connection), the only way to connect to them is by the remote powershell session. You can imagine the panic if Python REPL doesn’t work over SSH for Linux. Could you please kindly have a look, and tell at least why it doesn’t work ? Thanks. FYI, I’ve also opened a issue on Microsoft Powershell GitHub : https://github.com/PowerShell/PowerShell/issues/7581 Regards, Xiang ZHU ___ 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 REPL doesn't work on Windows over remote powershell session (winrm)
On Sun, Aug 26, 2018 at 9:09 AM, ZHU Xiang wrote: > But for the remote Windows powershell session the REPL doesn’t work, when I > type ‘’python” on the remote session, there’s nothing happened. > > # 1/ pre-install python on server1 (server 1 is a windows os) > # 2/ from a powershell console on server0, type below 2 commands: > enter-pssession server1 > python > Quick check: With the exact same servers, after you enter-possession, can you run a Python *script* successfully? And/or can you run: python -c "print(1+2)" ? If so, it's definitely just a REPL problem. > The problem impacts all the python versions and all the windows versions. Which versions were tested? ChrisA ___ 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 REPL doesn't work on Windows over remote powershell session (winrm)
ZHU Xiang writes: > === > Steps to reproduce > > # 1/ pre-install python on server1 (server 1 is a windows os) > # 2/ from a powershell console on server0, type below 2 commands: > enter-pssession server1 > python > > Expected behavior > # The python >>> prompt appears > > Actual behavior > # Nothing, it is still the powershell prompt > === Still the powershell prompt or nothing at all? If the latter, try using "python -i" instead. The "-i" will force interactive mode if stdin isn't otherwise detected as interactive (under the covers, isatty() is false for stdin), which is where I believe the issue is. I've used that under Windows ssh sessions (though with cygwin rather than powershell as well as some of my own remoting tools) for as long as I can remember (certainly back to XP and Python 2.x - maybe 1.x) for an interactive prompt when operating without a local windows console. I'm not sure if there's any better way for Python to detect a remote shell as being interactive under Windows that would cover such cases. Perhaps some of the newer pty changes I read Microsoft is making might help, assuming it flows through to the isatty() test. -- David ___ 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
