Re: [Python-Dev] [python-committers] PEP 595: Improving bugs.python.org

On Fri, May 24, 2019, 23:14 Gregory P. Smith wrote: > > > On Fri, May 24, 2019 at 1:48 PM Ezio Melotti > wrote: > >> >> On Fri, May 24, 2019, 20:23 Gregory P. Smith wrote: >> >>> -cc: committers to avoid crossposting. >>> >> >> +1 (I wanted to include committers, since the announcement about PE

Re: [Python-Dev] [python-committers] PEP 595: Improving bugs.python.org

On Fri, May 24, 2019 at 1:48 PM Ezio Melotti wrote: > > On Fri, May 24, 2019, 20:23 Gregory P. Smith wrote: > >> -cc: committers to avoid crossposting. >> > > +1 (I wanted to include committers, since the announcement about PEP 581 > was posted there too, but it's better to keep the discussion h

Re: [Python-Dev] [python-committers] PEP 595: Improving bugs.python.org

On Fri, May 24, 2019, 20:23 Gregory P. Smith wrote: > -cc: committers to avoid crossposting. > +1 (I wanted to include committers, since the announcement about PEP 581 was posted there too, but it's better to keep the discussion here) > I have feedback for roundup as experienced on BPO that sh

Re: [Python-Dev] [python-committers] PEP 595: Improving bugs.python.org

-cc: committers to avoid crossposting. I have feedback for roundup as experienced on BPO that should be represented within PEP 595 if we are going to have a summary of "improving roundup for BPO" captured in a PEP (presumably already rejected given 581? But good to have documented regardless so _t

Re: [Python-Dev] Python in next Windows 10 update

On Wed, 22 May 2019 at 03:30, Steve Dower wrote: > Hi all > > Just sharing this here because I think it's important for us to be aware > of it - I'm not trying to promote or sell anything here :) (Those who > were at the language summit have seen this already.) > > In the next Windows 10 update t

Re: [Python-Dev] Python in next Windows 10 update

On 24May2019 0220, Baptiste Carvello wrote: Hello, Le 21/05/2019 à 22:30, Steve Dower a écrit : [...] * the Python 3.7 installed from the store will not auto-update to 3.8, but when 3.8 is released we (Microsoft) will update the redirect to point at it * if you pass arguments to the redirect

Re: [Python-Dev] Python in next Windows 10 update

Hello, Le 21/05/2019 à 22:30, Steve Dower a écrit : > > [...] > > * the Python 3.7 installed from the store will not auto-update to 3.8, > but when 3.8 is released we (Microsoft) will update the redirect to > point at it > * if you pass arguments to the redirect command, it just exits with an > e

Re: [Python-Dev] Python in next Windows 10 update

On Thu, 23 May 2019 00:23:39 +0200 Ray Donnelly wrote: > On Thu, May 23, 2019, 12:17 AM Ivan Pozdeev via Python-Dev < > python-dev@python.org> wrote: > > > On 22.05.2019 23:52, Steve Dower wrote: > > > On 22May2019 1309, Ivan Pozdeev via Python-Dev wrote: > > >> As someone whose job is to dia

Re: [Python-Dev] Python in next Windows 10 update

On Thu, May 23, 2019, 12:17 AM Ivan Pozdeev via Python-Dev < python-dev@python.org> wrote: > On 22.05.2019 23:52, Steve Dower wrote: > > On 22May2019 1309, Ivan Pozdeev via Python-Dev wrote: > >> As someone whose job is to diagnose and fix problems with running > software: > >> Are there patches i

Re: [Python-Dev] Python in next Windows 10 update

On 22.05.2019 23:52, Steve Dower wrote: On 22May2019 1309, Ivan Pozdeev via Python-Dev wrote: As someone whose job is to diagnose and fix problems with running software: Are there patches in your release? Do you provide corresponding sources and debug symbols for it? You can find the sources

Re: [Python-Dev] Python in next Windows 10 update

On 22May2019 1309, Ivan Pozdeev via Python-Dev wrote: As someone whose job is to diagnose and fix problems with running software: Are there patches in your release? Do you provide corresponding sources and debug symbols for it? You can find the sources at https://github.com/python/cpython :)

Re: [Python-Dev] Python in next Windows 10 update

On 22May2019 1237, Oscar Benjamin wrote: On Tue, 21 May 2019 at 21:32, Steve Dower wrote: In the next Windows 10 update that starts rolling out today, we (Microsoft) have added "python.exe" and "python3.exe" commands that are installed on PATH *by default* and will open the Microsoft Store at

Re: [Python-Dev] Python in next Windows 10 update

On 21.05.2019 23:30, Steve Dower wrote: Hi all Just sharing this here because I think it's important for us to be aware of it - I'm not trying to promote or sell anything here :) (Those who were at the language summit have seen this already.) In the next Windows 10 update that starts rollin

Re: [Python-Dev] Python in next Windows 10 update

On Tue, 21 May 2019 at 21:32, Steve Dower wrote: > > In the next Windows 10 update that starts rolling out today, we > (Microsoft) have added "python.exe" and "python3.exe" commands that are > installed on PATH *by default* and will open the Microsoft Store at the > page where we (Python core team

Re: [Python-Dev] Python in next Windows 10 update

On 21May2019 1621, MRAB wrote: Does it behave nicely with py.exe? This is still something of an open issue with the Store package for Python - py.exe doesn't look for the registry keys in a way that will find them (due to some very obscure compatibility quirks). The Store package does not i

Re: [Python-Dev] Python in next Windows 10 update

On 2019-05-21 21:30, Steve Dower wrote: [snip] The associated blog post: https://devblogs.microsoft.com/python/python-in-the-windows-10-may-2019-update/ Here are answers to a few questions that I assume will come up, at least from this audience that understands the issues better than most: * i

Re: [Python-Dev] Python in next Windows 10 update

On 05/21/2019 01:30 PM, Steve Dower wrote: In the next Windows 10 update that starts rolling out today, we (Microsoft) have added "python.exe" and "python3.exe" commands that are installed on PATH *by default* and will open the Microsoft Store at the page where we (Python core team) publish ou

Re: [Python-Dev] Python in next Windows 10 update

On 21/05/2019 22.30, Steve Dower wrote: > Hi all > > Just sharing this here because I think it's important for us to be aware of > it - I'm not trying to promote or sell anything here :) (Those who were at > the language summit have seen this already.) > > In the next Windows 10 update that sta

Re: [Python-Dev] Python in next Windows 10 update

That’s great, Steve. Thanks for all of the work (by you and others) on this. -- Eric V. Smith True Blade Systems, Inc (301) 859-4544 > On May 21, 2019, at 4:30 PM, Steve Dower wrote: > > Hi all > > Just sharing this here because I think it's important for us to be aware of > it - I'm not try

Re: [Python-Dev] [python-committers] PEP 581 (Using GitHub issues for CPython) is accepted

On Wed, May 15, 2019 at 6:44 PM Ezio Melotti wrote: > > I share the same concerns: 1) the PEP contains several factual errors. I pointed this out during > the core-sprints last year and more recently Berker pointed out some > on GitHub: https://github.com/python/peps/pull/1013 ; > 4) Berker is/

Re: [Python-Dev] Python Language Summit 2019 blog posts

On 5/15/2019 6:06 PM, Mariatta wrote: If you have FOMO (fear of missing out) of Python Language Summit 2019, worry no more. We invited A. Jesse Jiryu Davis to cover for the language summit, and the blog posts are starting to appear in The PSF's official blog. Starts here: http://pyfound.blo

Re: [Python-Dev] [python-committers] PEP 581 (Using GitHub issues for CPython) is accepted

Hello, On Wed, May 15, 2019 at 5:18 PM Paul Moore wrote: > > On Wed, 15 May 2019 at 15:56, Victor Stinner wrote: > > > > Hi Paul, > > Le mer. 15 mai 2019 à 11:40, Paul Moore a écrit : > > > Also, is there an archive of the discussions anywhere? The PEP says > > > discussions happened on Zulip,

Re: [Python-Dev] [python-committers] PEP 581 (Using GitHub issues for CPython) is accepted

On Wed, May 15, 2019 at 8:18 AM Paul Moore wrote: > On Wed, 15 May 2019 at 15:56, Victor Stinner wrote: > > > > Hi Paul, > > Le mer. 15 mai 2019 à 11:40, Paul Moore a écrit : > > > Also, is there an archive of the discussions anywhere? The PEP says > > > discussions happened on Zulip, but I don

Re: [Python-Dev] [python-committers] PEP 581 (Using GitHub issues for CPython) is accepted

On Wed, 15 May 2019 at 15:56, Victor Stinner wrote: > > Hi Paul, > Le mer. 15 mai 2019 à 11:40, Paul Moore a écrit : > > Also, is there an archive of the discussions anywhere? The PEP says > > discussions happened on Zulip, but I don't follow that and I don't > > know where I can find an archived

Re: [Python-Dev] [python-committers] PEP 581 (Using GitHub issues for CPython) is accepted

Hi Paul, Le mer. 15 mai 2019 à 11:40, Paul Moore a écrit : > Also, is there an archive of the discussions anywhere? The PEP says > discussions happened on Zulip, but I don't follow that and I don't > know where I can find an archived copy of the discussions. Well, the PEP has been discussed a lot

Re: [Python-Dev] Python Documentation Translation in italian language

On 4/20/2019 4:14 AM, Alessandro Cucci wrote: Hello folks, I want to start a project for translating the Python Documentation in Italian. I'm reading the PEP545, trying to understand how it works. I founded a Python User Group in my city and I can work with them on the translations, plus next

Re: [Python-Dev] [python-committers] Last-minute request: please backport bpo-33329 fix to 3.4 and 3.5

I don't think that a thread about a release is the right place to discuss a bug. Please open an issue at bugs.python.org 😉 Victor Le lundi 11 mars 2019, Joni Orponen a écrit : > On Sun, Mar 10, 2019 at 7:50 AM Larry Hastings wrote: >> >> On 3/4/19 2:29 AM, Joni Orponen wrote: >> >> On Sat, Mar

Re: [Python-Dev] [python-committers] [RELEASED] Python 3.4.10rc1 and Python 3.5.7rc1 are now available

FYI I check and I confirm that all known security vulnerabilities listed in the link below are fixed in these releases: https://python-security.readthedocs.io/vulnerabilities.html Victor Le lun. 4 mars 2019 à 10:24, Larry Hastings a écrit : > > > On behalf of the Python development community, I'

Re: [Python-Dev] [python-committers] Announcing: signups are open for the 2019 Python Language Summit

> On 27 Feb 2019, at 14:22, Łukasz Langa wrote: > > The Python Language Summit is an event for the developers of Python > implementations (CPython, PyPy, Jython, and so on) to share information, > discuss our shared problems, and — hopefully — solve them. Oh, you'd also like to know *when* and

Re: [Python-Dev] python subprocess module to submit a list of slurm sbatch jobs, each job use multiprocessing.Pool to run simulation on single compute node in cluster

This mailing list is for the development of the Python interpreter, not for asking questions about your own code. Did you sign up using the Python-Dev mailing list website? At the top of the page, it says Do not post general Python questions to this list. For help with Python please se

Re: [Python-Dev] Python Language Governance Proposals

On 2018-10-26 19:17, Brett Cannon wrote: But since you're asking about wanting to "review PEPs", you can review them now. Unfortunately not everybody agrees on that... See https://mail.python.org/pipermail/python-dev/2018-October/155441.html in particular I really hope that I won't have to

Re: [Python-Dev] Python Language Governance Proposals

As a piece of pure experiential data based on some years trying to herd the PSF cats, if python-dev can find a way of running its activities without votes needing to be taken I would really emphasise the benefits of the lack of such administration. If voting is required, please consider using the

Re: [Python-Dev] Python Language Governance Proposals

On Tue, 23 Oct 2018 at 13:20, Jeroen Demeyer wrote: > What is the timeframe for the installation of the new governance? In > other words, when will it be possible to review PEPs? > PEP 8001 outlines the voting for the governance models which includes a planned schedule for that vote. After that

Re: [Python-Dev] Python Language Governance Proposals

What is the timeframe for the installation of the new governance? In other words, when will it be possible to review PEPs? ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.p

Re: [Python-Dev] Python Language Governance Proposals

+1 (for what it's worth) to any proposal which includes one (or more) GUIDOs :) S. On Tue, Oct 23, 2018 at 11:57 AM Victor Stinner wrote: > Hi, > > Last July, Guido van Rossum decided to resign from his role of BDFL. > Python core developers decided to design a new governance/organization > f

Re: [Python-Dev] [Python-checkins] bpo-34203: FAQ now recommends python 3.x over 2.x (GH-9796)

> On Oct 12, 2018, at 7:03 PM, Martin Panter wrote: > >> On 12/10/2018, Eric V. Smith wrote: >>> On 10/12/2018 5:17 AM, Tal Einat wrote: >>> >>> The latest stable releases can always be found on the `Python download page >>> -`_. There are two recommended

Re: [Python-Dev] [Python-checkins] bpo-34203: FAQ now recommends python 3.x over 2.x (GH-9796)

On 12/10/2018, Eric V. Smith wrote: > On 10/12/2018 5:17 AM, Tal Einat wrote: > >> The latest stable releases can always be found on the `Python download page >> -`_. There are two recommended >> production-ready >> -versions at this point in time, because at

Re: [Python-Dev] [Python-checkins] bpo-34203: FAQ now recommends python 3.x over 2.x (GH-9796)

On 10/12/2018 5:17 AM, Tal Einat wrote: The latest stable releases can always be found on the `Python download page -`_. There are two recommended production-ready -versions at this point in time, because at the moment there are two branches of -stable rele

Re: [Python-Dev] Python startup time

> On 9 Oct 2018, at 23:02, Gregory Szorc wrote: > > > > While we're here, CPython might want to look into getdirentriesattr() as > a replacement for readdir(). We switched to it in Mercurial several > years ago to make `hg status` operations significantly faster [2]. I'm > not sure if it will

Re: [Python-Dev] Python startup time

Hi, On Tue, 9 Oct 2018 14:02:02 -0700 Gregory Szorc wrote: > > Python 3.7 doesn't exhibit as much of a problem. But it is still there. > A brief audit of the importer code and call stacks confirms it is the > same problem - just less prevalent. Wall time execution of the test > harness from Py

Re: [Python-Dev] Python startup time

On 5/1/2018 8:26 PM, Gregory Szorc wrote: > On 7/19/2017 12:15 PM, Larry Hastings wrote: >> >> >> On 07/19/2017 05:59 AM, Victor Stinner wrote: >>> Mercurial startup time is already 45.8x slower than Git whereas tested >>> Mercurial runs on Python 2.7.12. Now try to sell Python 3 to Mercurial >>> d

Re: [Python-Dev] Python REPL doesn't work on Windows over remote powershell session (winrm)

On Sun, 26 Aug 2018 at 12:16, David Bolen wrote: > 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

Re: [Python-Dev] Python 2.7 EOL date

Thanks all for clarifying! -Collin On Sat, Aug 25, 2018 at 2:50 PM Benjamin Peterson wrote: > 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 ear

Re: [Python-Dev] [Python-checkins] bpo-34171: Prevent creating Lib/trace.cover when run the trace module. (GH-8841)

On Mon, Aug 27, 2018 at 7:26 AM Victor Stinner wrote: > > Jemery: would you mind to revert this commit since nobody fixed the > buildbot since 2 days? > https://pythondev.readthedocs.io/ci.html#revert-on-fail I think you meant Serhiy :) Anyway, a commit has finally landed that addresses the buil

Re: [Python-Dev] [Python-checkins] bpo-34171: Prevent creating Lib/trace.cover when run the trace module. (GH-8841)

Jemery: would you mind to revert this commit since nobody fixed the buildbot since 2 days? https://pythondev.readthedocs.io/ci.html#revert-on-fail Victor Le sam. 25 août 2018 à 22:50, Jeremy Kloth a écrit : > > On Sat, Aug 25, 2018 at 1:28 AM Serhiy Storchaka > wrote: > > > > https://github.com/

Re: [Python-Dev] Python REPL doesn't work on Windows over remote powershell session (winrm)

On Sat, Aug 25, 2018 at 11:09:10PM +, 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. [...] > FYI, I’ve also opened a issue on Microsoft Powershell GitHub : > https://github.com/Po

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 app

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 se

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 > sum

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 manage

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

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

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

Re: [Python-Dev] Python 2.7 EOL date

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

Re: [Python-Dev] Python 2.7 EOL date

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 t

Re: [Python-Dev] Python 2.7 EOL date

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 Victor 2018-08-23 20:53 GMT+02:00 Collin Anderson : > Hi All, > > Sorry if this has been mentioned before, but I noticed the Python 2.7 EOL > date was recent

Re: [Python-Dev] Python 2.7 EOL date

No more security fixes after Jan 1, 2020. It is the end of Python 2.7. On Thu, Aug 23, 2018, 12:47 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 release

Re: [Python-Dev] [python-committers] Winding down 3.4

If they're really all wontfix, maybe we should mark them as wontfix, thus giving 3.4 a sendoff worthy of its heroic stature. Godspeed, and may a flight of angels sing thee to thy rest, //arry/ On 08/20/2018 05:52 AM, Victor Stinner wrote: > "shutil copy* unsafe on POSIX - they preserve set

Re: [Python-Dev] [python-committers] Winding down 3.4

On 20/08/2018 14:52, Victor Stinner wrote: >> "shutil copy* unsafe on POSIX - they preserve setuid/setgit bits" >> https://bugs.python.org/issue17180 > There is no fix. A fix may break the backward compatibility. Is it really > worth it for the last 3.4 release? > My idea would be to focus on a "fi

Re: [Python-Dev] [python-committers] Winding down 3.4

> "shutil copy* unsafe on POSIX - they preserve setuid/setgit bits" > https://bugs.python.org/issue17180 There is no fix. A fix may break the backward compatibility. Is it really worth it for the last 3.4 release? > "XML vulnerabilities in Python" > https://bugs.python.org/issue17239 Bug inactiv

Re: [Python-Dev] [python-committers] Winding down 3.4

“So that 3.4 dies in good health?” More like getting all its evil deeds off its chest on the death bed, I think :) Top-posted from my Windows 10 phone From: Antoine Pitrou Sent: Monday, 13 August 2018 2:59 To: Larry Hastings; python-committers; Python-Dev Subject: Re: [python-committers] Winding

Re: [Python-Dev] [python-committers] Winding down 3.4

Le 13/08/2018 à 11:49, Larry Hastings a écrit : > > > We of the core dev community commit to supporting Python releases for > five years.  Releases get eighteen months of active bug fixes, followed > by three and a half years of security fixes.  Python 3.4 turns 5 next > March--at which point we

Re: [Python-Dev] [python-committers] [RELEASED] Python 3.4.9 and Python 3.5.6 are now available

On 8/6/2018 11:38 AM, Charalampos Stratakis wrote: > A side note on your side note. Different distro's have different > standards, use/customer cases to address etc. In enterprise > distributions the usual scheme is that the version that you see is the > minimum one and many fixes coming from ups

Re: [Python-Dev] [python-committers] [RELEASED] Python 3.4.9 and Python 3.5.6 are now available

- Original Message - > From: "Michael" > To: "Larry Hastings" , python-dev@python.org > Sent: Sunday, August 5, 2018 8:57:40 PM > Subject: Re: [Python-Dev] [python-committers] [RELEASED] Python 3.4.9 and > Python 3.5.6 are now available > On

Re: [Python-Dev] [python-committers] [RELEASED] Python 3.4.9 and Python 3.5.6 are now available

On 2018-08-05 19:57, Michael wrote: On 03/08/2018 03:22, Larry Hastings wrote: On 08/02/2018 07:17 AM, Victor Stinner wrote: 3.4.9 and 3.5.6 have no more known security vulnerabilities :-) Well, not to be a complete pill, but... https://bugs.python.org/issue17180 https://bugs.python.org/is

Re: [Python-Dev] [python-committers] [RELEASED] Python 3.4.9 and Python 3.5.6 are now available

On 03/08/2018 03:22, Larry Hastings wrote: On 08/02/2018 07:17 AM, Victor Stinner wrote: 3.4.9 and 3.5.6 have no more known security vulnerabilities :-) Well, not to be a complete pill, but...    https://bugs.python.org/issue17180    https://bugs.python.org/issue17239    https://bugs.python

Re: [Python-Dev] [python-committers] [RELEASED] Python 3.4.9 and Python 3.5.6 are now available

On 08/02/2018 07:17 AM, Victor Stinner wrote: 3.4.9 and 3.5.6 have no more known security vulnerabilities :-) Well, not to be a complete pill, but... https://bugs.python.org/issue17180 https://bugs.python.org/issue17239 https://bugs.python.org/issue19050 Sadly, just because they're

Re: [Python-Dev] [python-committers] [RELEASED] Python 3.4.9 and Python 3.5.6 are now available

Hi, 2018-08-02 16:00 GMT+02:00 Larry Hastings : > On behalf of the Python development community, I'm happy to announce the > availability of Python 3.4.9 and Python 3.5.6. Great! FYI these versions fix two security vulnerabilities: (*) CVE-2018-1000117: Buffer overflow vulnerability in os.symlin

Re: [Python-Dev] [Python-checkins] bpo-34239: Convert test_bz2 to use tempfile (#8485)

On 28/07/2018 23:54, Chris Jerdonek wrote: On Thu, Jul 26, 2018 at 2:05 PM, Tim Golden wrote: https://github.com/python/cpython/commit/6a62e1d365934de82ff7c634981b3fbf218b4d5f commit: 6a62e1d365934de82ff7c634981b3fbf218b4d5f branch: master author: Tim Golden committer: GitHub date: 2018-07-26

Re: [Python-Dev] [Python-checkins] bpo-34239: Convert test_bz2 to use tempfile (#8485)

On Thu, Jul 26, 2018 at 2:05 PM, Tim Golden wrote: > https://github.com/python/cpython/commit/6a62e1d365934de82ff7c634981b3fbf218b4d5f > commit: 6a62e1d365934de82ff7c634981b3fbf218b4d5f > branch: master > author: Tim Golden > committer: GitHub > date: 2018-07-26T22:05:00+01:00 > summary: > > bpo

Re: [Python-Dev] [python-committers] Time for 3.4.9 and 3.5.6

On 07/08/2018 11:50 AM, Ned Deily wrote: On Jul 8, 2018, at 14:23, Julien Palard via Python-Dev wrote: [Larry] 3.5 also got some doc-only changes related to the online "version switcher" dropdown. About this I have a question: the switchers for english version of 3.4 and 3.5 are disabled (

Re: [Python-Dev] [python-committers] Time for 3.4.9 and 3.5.6

On Jul 8, 2018, at 14:23, Julien Palard via Python-Dev wrote: > [Larry] >> 3.5 also got some doc-only changes related to the online "version switcher" >> dropdown. > > About this I have a question: the switchers for english version of 3.4 and > 3.5 are disabled (https://docs.python.org/3.5/) b

Re: [Python-Dev] [python-committers] Time for 3.4.9 and 3.5.6

Hi, [Larry] > 3.5 also got some doc-only changes related to the online "version switcher" > dropdown. About this I have a question: the switchers for english version of 3.4 and 3.5 are disabled (https://docs.python.org/3.5/) but not disabled for translations (https://docs.python.org/fr/3.5/).

Re: [Python-Dev] Python 3.7.0 is now available! (and so is 3.6.6)

On Wed, Jun 27, 2018 at 7:05 PM Ned Deily wrote: > On behalf of the Python development community and the Python 3.7 release > team, we are pleased to announce the availability of Python 3.7.0. Thanks, Ned (and everyone), for a great job on this release! And thanks to all for yet another great Py

Re: [Python-Dev] Python 3.7.0 is now available! (and so is 3.6.6)

Hi, I updated my list of Python known vulnerabilities and the good news is that Python 3.6.6 and 3.7.0 have no known vulnerability :-) Python 3.7.0 comes with fixes for: * CVE-2018-1000117: Buffer overflow vulnerability in os.symlink on Windows * CVE-2018-1060: difflib and poplib catastrophic ba

Re: [Python-Dev] Python and Linux Standard Base

On 27 June 2018 at 23:57, Charalampos Stratakis wrote: > From: "Antoine Pitrou" >> One question: who maintains the LSB? >> >> The fact that the Python portion was never updated may hint that nobody >> uses it... > > That could definitely be the case here. I stumbled upon that when checking > she

Re: [Python-Dev] Python and Linux Standard Base

- Original Message - > From: "Antoine Pitrou" > To: python-dev@python.org > Sent: Wednesday, June 27, 2018 3:42:53 PM > Subject: Re: [Python-Dev] Python and Linux Standard Base > > On Wed, 27 Jun 2018 09:18:24 -0400 (EDT) > Charalampos Stratakis wro

Re: [Python-Dev] Python and Linux Standard Base

The main wiki page was last touched at all in 2016. The mailing list in Jan 2018 had about 8 comments, none of them actually related to LSB. They stopped archiving the ML altogether in Feb 2018. I think it's safe to say the parrot is dead. On Wed, Jun 27, 2018, 9:50 AM Antoine Pitrou wrote: > On

Re: [Python-Dev] Python and Linux Standard Base

On Wed, 27 Jun 2018 09:18:24 -0400 (EDT) Charalampos Stratakis wrote: > > My question is, if there is any incentive to try and ask for > modernization/amendment of the standards? > I really doubt that any linux distro at that point can be considered lsb > compliant at least from the > python s

Re: [Python-Dev] [python-committers] 3.7.0 / 3.6.6 Update: all systems go for final releases!

Congrats, Ned. Thank you for all of your hard work! -- Eric > On Jun 26, 2018, at 2:39 AM, Ned Deily wrote: > > A quick update: after many months we are at the finish line. We are on > track (mixing metaphors) to release 3.7.0 (and 3.6.6) this week on > 2018-06-27. Since 3.7.0rc1 shipped 2 week

Re: [Python-Dev] Python-Dev Digest, Vol 179, Issue 21

The Jseries acknowlegement by using Jetty containers can get you a best resolution To python wheel asynchronism bugs Envoyé à partir d’un Smarpthone Android avec GMX Mail. Le 14/06/2018, 4:00 PM python-dev-requ...@python.org a écrit: On 13 Jun 2018, at 15:42, Nick Coghlan mailto:ncogh...@gmail

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

On May 24, 2018, at 12:26, Serhiy Storchaka wrote: > 24.05.18 19:02, Ned Deily пише: >> On May 24, 2018, at 11:35, Serhiy Storchaka wrote: >>> I have doubts about two issues. I feel the responsibility for them because >>> I had the opportunity to solve them before, but I lost it. >> [...] >> >>

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

> But cases not supported before 3.7 (like List[int]) now produce fragile pickles. List[int] pickled in 3.7 can't be un-pickled in 3.6, but I wouldn't worry too much about this because it never worked in 3.6. I remember you proposed using __getitem__ in __reduce__, but I am not sure it is a better

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

24.05.18 19:02, Ned Deily пише: On May 24, 2018, at 11:35, Serhiy Storchaka wrote: I have doubts about two issues. I feel the responsibility for them because I had the opportunity to solve them before, but I lost it. [...] Serhiy, what are the bugs.python.org issue numbers for these? Are th

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

> 2. Pickle support in typing is not perfect. I was going to fix it (I had almost ready code), but lost a chance of doing this before. It can be changed in 3.7.1, but this means that pickles of some derived typing types created in 3.7.0 will be not compatible with future versions (may be 3.7.1 will

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

On May 24, 2018, at 11:35, Serhiy Storchaka wrote: > I have doubts about two issues. I feel the responsibility for them because I > had the opportunity to solve them before, but I lost it. [...] Serhiy, what are the bugs.python.org issue numbers for these? Are they marked as "release blocker"?

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

24.05.18 10:23, Ned Deily пише: So this *is* really your last chance: if you know of any true releasing blocking issues for 3.7.0, you have about 12 more hours to log it in the bug tracker as a "release blocker". I'll send out an email once we start the release manufacturing. Any merges to the 3.

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

On May 24, 2018, at 07:26, Victor Stinner wrote: > 2018-05-24 9:23 GMT+02:00 Ned Deily : >> Any merges to the 3.7 branch after >> that will be released in 3.7.1 which we tentatively are planning to >> ship sometime before the end of July (< 2018-07-31). > I recall that Python 3.6.0 was full of bug

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-24 9:23 GMT+02:00 Ned Deily : > Any merges to the 3.7 branch after > that will be released in 3.7.1 which we tentatively are planning to > ship sometime before the end of July (< 2018-07-31). I recall that Python 3.6.0 was full of bugs, some functions like os.waitpid() on Windows (if I rec

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

On May 23, 2018, at 09:13, Ned Deily wrote: > On May 23, 2018, at 07:45, Serhiy Storchaka wrote: >> Is it possible to add yet one beta instead? >> CI was broken for few latest days, tests are not passed on my computer still >> (and fail on some buildbots), updating What's New exposed new feature

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

On May 23, 2018, at 07:45, Serhiy Storchaka wrote: > 15.05.18 14:51, Ned Deily пише: >> This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your >> feature fixes, bug fixes, and documentation updates in before >> 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days >> f

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

2018-05-23 13:45 GMT+02:00 Serhiy Storchaka : > CI was broken for few latest days, tests are not passed on my computer still > (and fail on some buildbots), (...) I looked at buildbots and I confirm that many of the 3.x buildbots are red: AMD64 FreeBSD 10.x Shared 3.x AMD64 Windows8.1 Non-Debug 3

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

Ah, Python doesn't compile on Windows anymore :-) https://bugs.python.org/issue33614 Victor 2018-05-23 14:16 GMT+02:00 Victor Stinner : > 2018-05-23 13:45 GMT+02:00 Serhiy Storchaka : >> CI was broken for few latest days, tests are not passed on my computer still >> (and fail on some buildbots),

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

15.05.18 14:51, Ned Deily пише: This is it! We are down to THE FINAL WEEK for 3.7.0! Please get your feature fixes, bug fixes, and documentation updates in before 2018-05-21 ~23:59 Anywhere on Earth (UTC-12:00). That's about 7 days from now. We will then tag and produce the 3.7.0 release candidat

Re: [Python-Dev] [Python-checkins] bpo-33522: Enable CI builds on Visual Studio Team Services (GH-6865) (GH-6925)

On Thu, May 17, 2018 at 11:32 PM Gregory P. Smith wrote: > Why did this commit modify .py files, unittests, and test.support? > That is inappropriate for something claiming to merely enable a CI platform. I think there is probably an argument to be made that some of the changes will be improvem

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

On 5/18/18 9:20 AM, Ivan Pozdeev via Python-Dev wrote: > Since Python uses semantic versioning (https://semver.org), the > criterion for "what's new-worthy" changes is simple: they are _public > interface changes_ (which include visible changes to documented behavior). > (I maintain that changes to

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

On 18.05.2018 10:55, Serhiy Storchaka wrote: 17.05.18 21:39, Brett Cannon пише: Maybe we should start thinking about flagging PRs or issues as needing a What's New entry to help track when they need one, or always expect it in a PR and ignore that requirement when a 'skip whats new' label is a

Re: [Python-Dev] [python-committers] FINAL WEEK FOR 3.7.0 CHANGES!

17.05.18 21:39, Brett Cannon пише: Maybe we should start thinking about flagging PRs or issues as needing a What's New entry to help track when they need one, or always expect it in a PR and ignore that requirement when a 'skip whats new' label is applied. That would at least make it easier to

Re: [Python-Dev] [Python-checkins] bpo-33522: Enable CI builds onVisual Studio Team Services (GH-6865) (GH-6925)

: Gregory P. Smith Sent: Thursday, May 17, 2018 21:32 To: python-dev@python.org Cc: python-check...@python.org Subject: Re: [Python-Dev] [Python-checkins] bpo-33522: Enable CI builds onVisual Studio Team Services (GH-6865) (GH-6925) Why did this commit modify .py files, unittests, and test.support

Re: [Python-Dev] [Python-checkins] bpo-33522: Enable CI builds on Visual Studio Team Services (GH-6865) (GH-6925)

Why did this commit modify .py files, unittests, and test.support? That is inappropriate for something claiming to merely enable a CI platform. -gps On Thu, May 17, 2018 at 6:50 AM Steve Dower wrote: > > https://github.com/python/cpython/commit/0d8f83f59c8f4cc7fe125434ca4ecdcac111810f > commit

  1   2   3   4   5   6   7   8   9   10   >