Re: [Python-Dev] Is adding support for os.PathLike an enhancement or bugfix?

On 6 May 2017 at 05:36, Chris Barker wrote: > It doesn't actually say "everywhere possible in the stdlib", but if the goal > is to facilitate migration, as stated, then the any but truly obscure > functions should be covered -- and shutil is certainly not obscure. > > So it

Re: [Python-Dev] Outdated GitHub clone of the old svn repository

OK I'll contact GitHub. On Fri, May 5, 2017 at 10:01 AM, Guido van Rossum wrote: > Let's coordinate who contacts GitHub. Victor, Brett or myself? > > On Fri, May 5, 2017 at 9:52 AM, Brett Cannon wrote: > >> >> >> On Fri, 5 May 2017 at 09:50 Victor Stinner

Re: [Python-Dev] Is adding support for os.PathLike an enhancement or bugfix?

On May 5, 2017 10:39 PM, "Chris Barker" wrote: Sorry to come late to the game, It wasn't immediately clear to me what the implications were of the "enhancement or bugfix" distinction... On Thu, May 4, 2017 at 9:46 PM, Nick Coghlan wrote: > That

Re: [Python-Dev] Is adding support for os.PathLike an enhancement or bugfix?

On 5/5/2017 3:36 PM, Chris Barker wrote: Sorry to come late to the game, It wasn't immediately clear to me what the implications were of the "enhancement or bugfix" distinction... An enhancement changes the definition of the Python language, a bugfix does not. Enhancements can only be part

Re: [Python-Dev] Is adding support for os.PathLike an enhancement or bugfix?

On 5/5/2017 3:36 PM, Chris Barker wrote: Sorry to come late to the game, It wasn't immediately clear to me what the implications were of the "enhancement or bugfix" distinction... On Thu, May 4, 2017 at 9:46 PM, Nick Coghlan > wrote: That

Re: [Python-Dev] Is adding support for os.PathLike an enhancement or bugfix?

Sorry to come late to the game, It wasn't immediately clear to me what the implications were of the "enhancement or bugfix" distinction... On Thu, May 4, 2017 at 9:46 PM, Nick Coghlan wrote: > That improved casting mechanism and the implicit support in the low > level APIs

Re: [Python-Dev] Outdated GitHub clone of the old svn repository

Let's coordinate who contacts GitHub. Victor, Brett or myself? On Fri, May 5, 2017 at 9:52 AM, Brett Cannon wrote: > > > On Fri, 5 May 2017 at 09:50 Victor Stinner > wrote: > >> 2017-05-05 18:36 GMT+02:00 Jonathan Goble : >> > It

Re: [Python-Dev] Outdated GitHub clone of the old svn repository

On Fri, May 5, 2017 at 12:52 PM Brett Cannon wrote: > On Fri, 5 May 2017 at 09:50 Victor Stinner > wrote: > >> 2017-05-05 18:36 GMT+02:00 Jonathan Goble : >> > It appears to me to be an individual user rather than an organization.

Re: [Python-Dev] Outdated GitHub clone of the old svn repository

On Fri, 5 May 2017 at 09:50 Victor Stinner wrote: > 2017-05-05 18:36 GMT+02:00 Jonathan Goble : > > It appears to me to be an individual user rather than an organization. > > Oh nice, glad to meet you :-) So what do you think? Are you ok to > remove

Re: [Python-Dev] Outdated GitHub clone of the old svn repository

2017-05-05 18:36 GMT+02:00 Jonathan Goble : > It appears to me to be an individual user rather than an organization. Oh nice, glad to meet you :-) So what do you think? Are you ok to remove this old clone? Or do you have reasons to keep it? Victor

Re: [Python-Dev] Outdated GitHub clone of the old svn repository

On Fri, May 5, 2017 at 7:31 PM, Victor Stinner wrote: > Hi, > > Does someone know who owns the following Git clone of the old > Subversion CPython repository? > https://github.com/python-git/python/ > > I would suggest to remove it to avoid confusion. A friend pointed to

Re: [Python-Dev] Outdated GitHub clone of the old svn repository

I submitted another issue requesting to shut down that repo, but there are already several other such issues and no response. I think the next step is to contact GitHub user support and request that the repo be shut down. They sometimes do such things if it's clear that a username/repo is

Re: [Python-Dev] Outdated GitHub clone of the old svn repository

On Fri, May 5, 2017 at 12:33 PM Victor Stinner wrote: > Is https://github.com/python-git a real user or an organization? > It appears to me to be an individual user rather than an organization. ___ Python-Dev mailing list

[Python-Dev] Outdated GitHub clone of the old svn repository

Hi, Does someone know who owns the following Git clone of the old Subversion CPython repository? https://github.com/python-git/python/ I would suggest to remove it to avoid confusion. A friend pointed to me this repository and was surprised to see outdated code... Is

[Python-Dev] Summary of Python tracker Issues

ACTIVITY SUMMARY (2017-04-28 - 2017-05-05) Python tracker at http://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: open5929 (+21) closed 36109 (+61) total 42038 (+82) Open issues

Re: [Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale

On 5 May 2017 at 23:21, INADA Naoki wrote: > On Fri, May 5, 2017 at 1:25 AM, Antoine Pitrou wrote: >> If we want to adopt PEP 538 before pronouncing on PEP 540, then PEP 538 >> should remove all points conditional on PEP 540 adoption, and PEP 540 >>

Re: [Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale

On Fri, May 5, 2017 at 1:25 AM, Antoine Pitrou wrote: > On Thu, 4 May 2017 11:24:27 +0900 > INADA Naoki wrote: >> Hi, Nick and all core devs who are interested in this PEP. >> >> I'm reviewing PEP 538 and I want to accept it in this month. >> It will

Re: [Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale

On 5 May 2017 at 19:45, Erik Bray wrote: > On Thu, May 4, 2017 at 6:25 PM, Antoine Pitrou wrote: >> If we want to adopt PEP 538 before pronouncing on PEP 540, then PEP 538 >> should remove all points conditional on PEP 540 adoption, and PEP 540 >>

Re: [Python-Dev] PEP 538: Coercing the legacy C locale to a UTF-8 based locale

On Thu, May 4, 2017 at 6:25 PM, Antoine Pitrou wrote: > On Thu, 4 May 2017 11:24:27 +0900 > INADA Naoki wrote: >> Hi, Nick and all core devs who are interested in this PEP. >> >> I'm reviewing PEP 538 and I want to accept it in this month. >> It will

Re: [Python-Dev] "make touch" replaced with "make regen-all"

2017-05-05 6:31 GMT+02:00 Nick Coghlan : > For the benefit of Linux distros attempting to ensure they're doing > full "from source" builds, it would be good to note this in a "Notable > changes in maintenance releases", akin to the existing ones for 3.4 > and 2.7 (perhaps

Re: [Python-Dev] "make touch" replaced with "make regen-all"

On 5 May 2017 at 16:01, Victor Stinner wrote: > Le 5 mai 2017 6:31 AM, "Nick Coghlan" a écrit : > > The note just needs to say that folks that care about doing "complete" > builds need to adjust their command sequence to be "./configure > && make

Re: [Python-Dev] "make touch" replaced with "make regen-all"

Le 5 mai 2017 6:31 AM, "Nick Coghlan" a écrit : The note just needs to say that folks that care about doing "complete" builds need to adjust their command sequence to be "./configure && make regen-all && make install", rather than the previous pattern of "./configure &&