On 19/07/18 03:36, Nathaniel Smith wrote:
[tl;dr: We need some ground rules, because uncertainty makes it hard
to think straight. But if we get sucked into a complicated meta-debate
about the ground rules then that defeats the purpose. My proposal for
a Minimum Viable Ground Rule: let's all
On 12/07/18 15:57, Guido van Rossum wrote:
Now that PEP 572 is done, I don't ever want to have to fight so hard for
a PEP and find that so many people despise my decisions.
I would like to remove myself entirely from the decision process. I'll
still be there for a while as an ordinary core
Mark Shannon has an academic background in
language design.
Language *implementation* not design. It is much less controversial :)
Thanks for your vote of confidence, but I think there are plenty of
others better qualified.
Cheers,
Mark.
___
python
Hi,
On 25/09/18 20:30, Yury Selivanov wrote:
What's the current plan for what version of Python we release after 3.9?
[snip]
For the record, we account for the following version tests when
analysing code (on lgtm.com):
sys.version == "3"
sys.version_info > (3,)
sys.version_info[0] == 3
Hi,
Does this mean that https://github.com/python/cpython/pull/6641 isn't
going to get in 3.8?
Cheers,
Mark.
On 03/06/2019 18:56, Łukasz Langa wrote:
tl;dr - We're on it but Beta 1 is special and the buildbots need more
cowbell^H^H more green.
---
Today Victor's been very active helping
https://docs.google.com/presentation/d/1I5ELOo8VTWpgNmr76Edd--W7jnPSWjhg-c2Z-SxyOHM/
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
Hi Victor,
I say no. Why the sudden urgency?
I think that you are making too many assumptions about how
inter-interpreter communication is going to work, and about sharing of
objects.
On 06/05/2020 6:49 pm, Victor Stinner wrote:
Hi,
tl; dr I'm asking for your permission to merge the
Hi,
My PR tests are failing seemingly due to some bug in enum.rst
Which might be caused by https://github.com/python/cpython/pull/22392
(that's the superficial cause, it might not be the root cause).
Example failure:
https://github.com/python/cpython/pull/25069
Hi all,
There is one day left to vote for Ken Jin.
https://discuss.python.org/t/vote-to-promote-ken-jin-fidget-spinner/10146
Ken Jin already has my vote.
He has repeatedly shown himself able to produce good work on many parts
on the code base.
Hi Pablo,
Issue 43683 should not have been marked as a release blocker, as it is a
performance issue, not a bug.
The related bug (which was a release blocker) is
https://bugs.python.org/issue46009, and was fixed a while ago.
Cheers,
Mark.
On 04/01/2022 11:12 pm, Pablo Galindo Salgado wrote:
Hi Pablo,
On 03/02/2022 11:27 pm, Pablo Galindo Salgado wrote:
We needed to tame some angry buildbots, but after a small fight, we won with
just some scratches! Here you have a shiny new alpha release: Python 3.11.0a5.
https://www.python.org/downloads/release/python-3110a5/
Hi,
We don't have a PR check for refleaks. I would like one.
The buildbots are far too slow and unreliable to provide a sensible way to
check for refleaks.
It is nigh impossible to pick out errors in a PR from flaky tests, flaky
machines and pre-existing errors.
Stopping refleaks at source
12 matches
Mail list logo
