I agree with you, Ned.
Mariatta, I'm happy to work on an initial pass at the devguide in my fork.
On Fri, Jun 28, 2019 at 10:52 AM Ned Deily wrote:
>
> On Jun 28, 2019, at 12:56, Mariatta wrote:
> > Some of the items brought up during the language summit:
> > [...]
> > - we should be updating
ACTIVITY SUMMARY (2019-06-21 - 2019-06-28)
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:
open7054 (+16)
closed 42139 (+61)
total 49193 (+77)
Open issues
On Jun 28, 2019, at 12:56, Mariatta wrote:
> Some of the items brought up during the language summit:
> [...]
> - we should be updating devguide ahead of the actual migration, so core
> developers and release managers have time to review and learn the new
> workflow. (suggested by Ned Deily)
Glenn Linderman wrote:
> On 6/27/2019 3:09 PM, Brett Cannon wrote:
> > My guess is that without Guido to just ask this will
> > have to go to a PEP as it changes a built-in.
> > How does adding two new methods change a built-in?
> > Now if an extra parameter were added to modify lstrip, rstrip,
On 6/28/2019 10:10 AM, MRAB wrote:
On 2019-06-28 03:40, Glenn Linderman wrote:
On 6/27/2019 3:09 PM, Brett Cannon wrote:
My guess is that without Guido to just ask this will have to go to a
PEP as it changes a built-in.
How does adding two new methods change a built-in?
Now if an extra
On Jun 28, 2019, at 09:56, Mariatta wrote:
>
> I've updated PEP 581 yesterday, adding the "Downsides of GitHub" section.
>
> https://www.python.org/dev/peps/pep-0581/#downsides-of-github
Thanks Mariatta!
> I plan to update PEP 588 sometime this weekend or next, to incorporate the
>
On 2019-06-28 03:40, Glenn Linderman wrote:
On 6/27/2019 3:09 PM, Brett Cannon wrote:
My guess is that without Guido to just ask this will have to go to a PEP as it
changes a built-in.
How does adding two new methods change a built-in?
Now if an extra parameter were added to modify lstrip,
Hi,
I've updated PEP 581 yesterday, adding the "Downsides of GitHub" section.
https://www.python.org/dev/peps/pep-0581/#downsides-of-github
Other parts of the PEP has also been updated to reflect recent changes to
roundup/bpo that happened after PEP 581's acceptance, for example:
- ability to
On Wed., 26 Jun. 2019, 4:14 pm Elias Zamaria, wrote:
> Nick Coghlan, I'm thinking about what you said, over a year ago, about
> finding a new champion for PEP 467. I think it would be a privilege to work
> on something like that, which may be used by millions of people over a
> period of years
