Based on the replies here and discussing things with the steering council,
we decided we should archive the list.
On Sat, Jul 8, 2023 at 2:57 AM Marc-Andre Lemburg wrote:
> On 07.07.2023 12:11, Marc-Andre Lemburg wrote:
>
> On 07.07.2023 01:44, Brett Cannon wrote:
>
>
installation)
>>
>> Thanks.
>>
>> On 04.07.2023 06:57, C.A.M. Gerlach wrote:
>> > FWIW, +1 to archiving to reduce duplication. If decided, I can help out
>> > making the appropriate devguide, PEP, etc. changes, as I've done for
>&
The question has come up as to whether people still find this mailing list
useful enough to keep around. Looking at the archive (
https://mail.python.org/archives/list/python-committers@python.org/latest),
this list seems to be used for two things:
1. Announcing new releases
2. Announcing
https://discuss.python.org/t/poll-feedback-to-the-sc-on-making-cpython-free-threaded-and-pep-703/28540/
P.S. I personally would advise people keep an eye on
https://discuss.python.org/c/committers/ for stuff as not everyone
remembers this mailing list even exists (I'm personally posting here just
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
is covered by
https://github.com/python/cpython/actions/workflows/build.yml?query=branch%3Amain+is%3Acompleted
.)
On Thu, Mar 10, 2022 at 3:35 PM Brett Cannon wrote:
> I brought this up on python-dev at
> https://mail.python.org/archives/list/python-...@python.org/
EOM
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
On Mon, May 2, 2022 at 4:12 PM Ethan Furman wrote:
> On 5/2/22 16:00, Jelle Zijlstra wrote:
>
> > We have added several new triagers today:
>
> Do triagers have access to this list?
>
Nope, core devs only.
-Brett
>
> Regardless, congratulations!!
>
> --
> ~Ethan~
>
at 1:31 PM Brett Cannon wrote:
>
>
> On Sat, Apr 9, 2022 at 5:04 AM M.-A. Lemburg wrote:
>
>> On 09.04.2022 02:13, Brett Cannon wrote:
>> >
>> >
>> > On Fri, Apr 8, 2022 at 5:03 AM Marc-Andre Lemburg > > <mailto:m...@egenix.com>>
On Sat, Apr 9, 2022 at 5:04 AM M.-A. Lemburg wrote:
> On 09.04.2022 02:13, Brett Cannon wrote:
> >
> >
> > On Fri, Apr 8, 2022 at 5:03 AM Marc-Andre Lemburg > <mailto:m...@egenix.com>> wrote:
> >
> > On 06.04.2022 20:48, Brett Cannon wrote
On Fri, Apr 8, 2022 at 5:03 AM Marc-Andre Lemburg wrote:
> On 06.04.2022 20:48, Brett Cannon wrote:
> > Last chance on whether my tier 3 proposal make sense! I will take
> silence as
> > acceptance and plan to convert any current tier 2 platform with a single
> c
Last chance on whether my tier 3 proposal make sense! I will take silence
as acceptance and plan to convert any current tier 2 platform with a single
core dev to tier 3 and then ask the SC to approve/reject the list of
platforms. I will also update the PEP about expectations of when things
must be
On Thu, Mar 31, 2022 at 4:40 PM Victor Stinner wrote:
> Hi,
>
> I don't think that the current PEP 11 draft (*) describes correctly
> the current status of a bunch of platforms which are not "actively"
> supported. I like to call these plaforms as "best effort support"
> platforms. I propose
at 12:32 PM Brett Cannon wrote:
> Thanks to Petr, and Victor, the platforms that are still looking for a
> total of two maintainers over at
> https://github.com/python/peps/pull/2442/files are:
>
>1. arch64-apple-darwin clang
>2. aarch64-linux-gnu glibc, clang (Victor
worse than e.g. the devguide.
-Brett
>
> On Fri, 11 Mar 2022, 10:36 am Brett Cannon, wrote:
>
>> I brought this up on python-dev at
>> https://mail.python.org/archives/list/python-...@python.org/thread/ZPBSHENP3V7KHNPYWE6BEQD5ASES2NLV/
>> , and the feedback seemed supportive.
On Mon, Mar 28, 2022 at 7:09 AM Petr Viktorin wrote:
> On Fri, Mar 25, 2022 at 8:32 PM Brett Cannon wrote:
> >
> > Thanks to Petr, and Victor, the platforms that are still looking for a
> total of two maintainers over at
> https://github.com/python/peps/pull/2442/files are:
On Sat, Mar 26, 2022 at 10:11 AM Victor Stinner wrote:
> On Fri, Mar 25, 2022 at 7:04 PM Brett Cannon wrote:
> >
> > On Fri, Mar 25, 2022 at 4:23 AM Victor Stinner
> wrote:
> >>
> >> I dislike the Tier 1 rule "All core developers are responsible to k
On Fri, Mar 25, 2022 at 1:18 PM Ned Deily wrote:
> On Mar 25, 2022, at 15:32, Brett Cannon wrote:
> > Thanks to Petr, and Victor, the platforms that are still looking for a
> total of two maintainers over at
> https://github.com/python/peps/pull/2442/files are:
> >
-linux-gnu glibc, clang
5. s390x-linux-gnu glibc, gcc
6. s390x-linux-gnu glibc, clang
7. x86_64-linux-gnu glibc, clang (Victor is already listed)
8. x86_64-unknown-freebsd BSD libc, cc (Victor is already listed)
On Thu, Mar 24, 2022 at 12:37 PM Brett Cannon wrote:
> Ba
On Fri, Mar 25, 2022 at 4:23 AM Victor Stinner wrote:
> I dislike the Tier 1 rule "All core developers are responsible to keep
> these platforms, and thus ``main``, working."
>
> In my experience, "Everyone is reponsible" means in practice "nobody
> is responsible".
I don't think that applies
nux-gnu glibc, clang
10. x86_64-unknown-freebsd BSD libc, cc
Tier 1 is taken care of:
1. i686-windows-msvc
2. x86_64-windows-msvc
3. x86_64-apple-darwin BSD libc, clang
4. x86_64-linux-gnu glibc, gcc
On Thu, Mar 17, 2022 at 5:56 PM Brett Cannon wrote:
> After considering ev
On Wed, Mar 23, 2022 at 2:23 AM Paul Moore wrote:
> On Tue, 22 Mar 2022 at 23:27, Brett Cannon wrote:
>
> > Update PEP 2 to say a PEP is necessary to add a module to the stdlib
> > Update PEP 4 to say that a PEP is necessary to deprecate/remove a module
> > Mark PEP
I had kicked off a discussion a while back at
https://discuss.python.org/t/how-do-we-want-to-manage-additions-removals-to-the-stdlib/10681
about how to manage the stdlib (this has nothing to with *what* the stdlib
is and thus what belongs in it). It finally bubbled up in the SC agenda and
after
e list as that buildbot has not successfully built in quite some time
(powerpcle seems fine).
On Mon, Mar 14, 2022 at 5:35 PM Gregory P. Smith wrote:
>
>
> On Mon, Mar 14, 2022 at 11:43 AM Marc-Andre Lemburg
> wrote:
>
>> On 14.03.2022 19:34, Brett Cannon wrote:
>> >
On Mon, Mar 14, 2022 at 12:59 PM Christian Heimes
wrote:
> On 14/03/2022 19.37, Brett Cannon wrote:
> >
> >
> > On Fri, Mar 11, 2022 at 5:04 PM Victor Stinner > <mailto:vstin...@python.org>> wrote:
> >
> > Hi Brett,
> >
> > You ca
On Fri, Mar 11, 2022 at 5:04 PM Victor Stinner wrote:
> Hi Brett,
>
> You can put my name as Contact of all Fedora and RHEL platforms.
>
> Note: Fedora "Rawhide" is the rolling release and it's common that
> these buildbots are broken by kernel, compiler or glibc updates,
> rather than actual
On Sat, Mar 12, 2022 at 5:29 AM Marc-Andre Lemburg wrote:
> On 11.03.2022 19:26, Brett Cannon wrote:
>
>
>
> On Fri, Mar 11, 2022 at 1:18 AM Marc-Andre Lemburg wrote:
>
>> I think the list is missing some important platforms which we do
>> support (looking at confi
On Fri, Mar 11, 2022 at 12:37 PM Gregory P. Smith wrote:
>
> On Fri, Mar 11, 2022 at 10:45 AM Brett Cannon wrote:
>
>>
>> On Fri, Mar 11, 2022 at 9:16 AM Paul Moore wrote:
>>
>>> On Fri, 11 Mar 2022 at 17:09, Marc-Andre Lemburg wrote:
>>> &g
On Fri, Mar 11, 2022 at 9:16 AM Paul Moore wrote:
> On Fri, 11 Mar 2022 at 17:09, Marc-Andre Lemburg wrote:
> >
> > On 11.03.2022 17:42, Zachary Ware wrote:
> > >
> > > - Only code which either supports a higher-tier platform or is a
> general improvement may be checked in.
> >
> > My
ct such a list would bitrot at a rate that makes it not
> worth including in the official tier list, whether by those
> communities fading away or the platform being promoted to tier 3.
>
>
> On Thu, Mar 10, 2022 at 5:36 PM Brett Cannon wrote:
> > Tier 1
> > ==
>
On Fri, Mar 11, 2022 at 1:38 AM Christian Heimes
wrote:
> On 11/03/2022 00.35, Brett Cannon wrote:
> > I brought this up on python-dev at
> >
> https://mail.python.org/archives/list/python-...@python.org/thread/ZPBSHENP3V7KHNPYWE6BEQD5ASES2NLV/
> > <
> https:/
On Fri, Mar 11, 2022 at 1:26 AM Petr Viktorin wrote:
> On 11. 03. 22 0:35, Brett Cannon wrote:
> > I brought this up on python-dev at
> >
> https://mail.python.org/archives/list/python-...@python.org/thread/ZPBSHENP3V7KHNPYWE6BEQD5ASES2NLV/
> > <
> https://mail.p
for which binaries are built during the release and
> which are source only. At the moment, only Windows and
> macOS platforms have official binaries.
>
I was actually explicitly asked by someone who is part of doing releases
*not* to list installers as they would prefer they not be viewed as
en XXXXXX
Brett Cannon, Christian Heimes
wasm32-unknown-wasi XXXXXX
Brett Cannon, Christian
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
In the SC meeting today we discussed requiring two-factor authentication
(aka 2FA/MFA) and came away strongly considering it (but no definitive
plans yet). But we did agree that we should send a quick email encouraging
everyone to turn on 2FA for their GitHub Accounts regardless of what we
decide
I got @ mentioned on some bot stuff the other day on Discord and I realized
I am no longer in a good position to be considered the person to loop in on
that sort of stuff. My code contribution rate in CPython isn't high enough
right now for me to drive what our workflow should be, but I'm not a
Based on the results of the poll on discuss.python.org, the core dev
sprints will be from October 18 - 24. Based on feedback from last year and
for simplicity reasons, the sprints will be hosted on the core dev Discord
server (link in the Inquisition category on discuss.python.org to keep it
For all PEPs we ask the core dev who is sponsoring/(co-)authoring to list
themselves in https://github.com/python/peps/blob/master/.github/CODEOWNERS
so you get notified when a PR comes in for the PEP.
___
python-committers mailing list --
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
Just add the `discord` key to your entry in
https://github.com/python/voters/blob/master/python-core.toml with your
username. Totally optional as always, but since we now have a core dev
Discord server I figured it made sense to start recording this.
___
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
ree to speak up, otherwise I assume it's a situation
like Tim where we just need to help you figure out how to make it work).
-Brett
>
>
>
> On Mon, Jun 14, 2021 at 12:38 PM Brett Cannon wrote:
>
>> I have discovered someone tried to break into my GitHub account (you can
>&
I have discovered someone tried to break into my GitHub account (you can
check yourself by going to https://github.com/settings/security-log and
looking for "failed to login" attempts for potentially odd geographical
locations for yourself). CPython probably would have been the biggest
target for
As a data point for where newer language communities have ended up, Rust is
on Discord and Zulip.
On Fri., May 14, 2021, 19:14 Dong-hee Na, wrote:
> Believe it or not, there are people who are not familiar with the IRC
> culture.
> And those people are who enter the opensource culture after the
On Fri, May 14, 2021 at 6:48 AM Senthil Kumaran wrote:
> On Fri, May 14, 2021 at 09:36:52AM +0200, Antoine Pitrou wrote:
> > #python-dev on IRC has been wildly successful until perhaps 2015.
> > Personally, I would have no problem using IRC if wanted to connect to a
> chat
> > for CPython at
EOM
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
list?
>
If someone knows of a way to make that work in Discourse I would personally
support it.
-Brett
>
> --
> Senthil
>
> On Thu, Apr 29, 2021 at 01:55:25PM -0700, Brett Cannon wrote:
> > https://discuss.python.org/t/vote-to-promote-irit-katriel/8457
>
> >
https://discuss.python.org/t/vote-to-promote-irit-katriel/8457
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
We have added https://github.com/python/peps/blob/master/.github/CODEOWNERS
to the peps repo to help automatically add core devs who are authors or a
sponsor of PEPs to PRs. This will help alleviate the load on the PEP
editors as a decent chunk of time is taken up routing PRs to the
appropriate
On Mon, Apr 5, 2021 at 12:57 PM Ewa Jodlowska wrote:
>
>
>
> On Mon, Apr 5, 2021 at 2:36 PM Victor Stinner wrote:
>
>> Hi Ewa,
>>
>> This is really awesome! It's great that the PSF can now hire someone for
>> that!
>>
>> The job offer is great, but I would like some clarification :-) (While
>>
On Wed, Mar 3, 2021 at 1:32 PM Christian Heimes
wrote:
> On 03/03/2021 21.54, Brett Cannon wrote:
> > Has this been submitted to the SC yet? I can't find an email or anything
> > at
> >
> https://github.com/python/steering-council/issues?q=is%3Aissue+is%3Aopen+644
&g
On Wed, Mar 3, 2021 at 8:08 AM Christian Heimes
wrote:
> On 03/03/2021 16.06, Senthil Kumaran wrote:
> > On Tue, Mar 2, 2021 at 8:29 PM Gregory P. Smith wrote:
> >>
> >> For lack of better things to do with that...
> https://bugs.python.org/issue43382 filed to track it.
> >
> > Actually, that
BTW if people want to help move Bedevere's functionality out of the bot and
into GitHub Actions so it's more visible and easier for others to help
maintain then that would be appreciated (I'm planning to spend my
holidays developing a GitHub Action to take over the news entry file check
and very
Ernest closed the nominations and we ended up with 10 nominees! Thanks to
everyone who stepped forward to serve on the SC.
I would like to encourage people to take the time to read everyone's
nomination posts as stances on a wide variety of topics ranging from
pattern matching to the Code of
During the latest SC meeting we discussed the fact that none of us felt we
had a clear view of whether consensus was around pattern matching and the
current PEPs exists simply due to the volume of discussion. As such we
decided to create a poll to see what the general feeling was among
everybody:
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
Our lesson from our "innocuous" addition of booleans makes me leery of
anything that tweaks the API such that it isn't compatible in the same
feature release.
On Fri, Oct 23, 2020 at 3:16 PM Barry Warsaw wrote:
> Over in:
>
> * https://bugs.python.org/issue30681
> *
https://www.python.org/dev/peps/pep-0641/ (once the cron job runs)
https://discuss.python.org/t/pep-641-using-an-underscore-in-the-version-portion-of-python-3-10-compatibility-tags/5513
for discussions.
This was discussed at the core dev sprints and has RM sign-off. The plan is
to discuss this
On Tue, Oct 20, 2020 at 3:07 PM Brett Cannon wrote:
>
>
> On Tue, Oct 20, 2020 at 2:58 PM Nathaniel Smith wrote:
>
>> How are you measuring "activity"? Just commits?
>>
>
> Same as it has always been since the voters repo has existed and we
>
ther author a PR that someone else merges or you
can merge someone else's PR and that counts as active (or author and merge
your own PR).
-Brett
>
> On Tue, Oct 20, 2020 at 12:16 PM Brett Cannon wrote:
>
>> With the next SC election fast approaching, I did the final tweaks I
>&
With the next SC election fast approaching, I did the final tweaks I wanted
to make to the voters repo to address visibility issues we had in the last
election.
First, there is now a monthly cron job that will run at
On Mon, Oct 19, 2020 at 11:22 AM Ned Deily wrote:
> On Oct 19, 2020, at 13:59, Brett Cannon wrote:
> > On Sun, Oct 18, 2020 at 2:21 PM Ethan Furman wrote:
> >> On 10/18/20 1:18 PM, Ned Deily wrote:
> >> > On Oct 18, 2020, at 15:45, Carol Willing wrote:
> &g
On Sun, Oct 18, 2020 at 2:21 PM Ethan Furman wrote:
> On 10/18/20 1:18 PM, Ned Deily wrote:
> > On Oct 18, 2020, at 15:45, Carol Willing wrote:
> >> We've largely moved away from Travis for Jupyter testing in favor of
> Azure pipelines and CircleCI as Travis was becoming increasingly slow and
>
On Fri, Oct 16, 2020 at 11:58 AM Pablo Galindo Salgado
wrote:
> > We should simply mark the github actions "Tests / Ubuntu" CI as
> required.
>
> +1 I completely agree with everything Gregory said.
>
+1 from me as well.
-Brett
>
>
> On Fri, 16 Oct 2020 at 19:36, Gregory P. Smith wrote:
>
>>
Should we consider dropping Travis CI as a CI provider if it continues to
be so flaky? Otherwise isn't it becoming just noise on a PR?
On Fri, Oct 16, 2020 at 1:42 AM Victor Stinner wrote:
> Hi,
>
> Python has no mandatory Linux CI job on pull requests anymore. Right
> now Windows (x64) remains
On Thu, Oct 8, 2020 at 5:21 PM Barry Warsaw wrote:
> On Oct 8, 2020, at 14:34, Ethan Furman wrote:
> >
> > Sure, but I don't know who they are. Besides, if the SC did not do the
> banning/moderating then they should find out what happened.
> >
> > If the SC did do the banning/moderating then
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
[This has been sent to python-committers, python-dev, and python-ideas]
Recently, a series of discussions on this mailing list resulted in behavior
that did not live up to the standards of the Python Community. The PSF
Board of Directors, Python Steering Council, and the PSF Conduct Working
For those of you not on python-dev, the SC today chose to accept PEP 387.
https://www.python.org/dev/peps/pep-0387/
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
Can we wait until after 3.10 development opens up? And could it be a `-X` flag?
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
joannah nanjekye wrote:
> Hey all,
> Unfortunately this year am too busy and cant even attend the language
> summit mostly.
:( Sorry to hear that.
> However if I knew the schedule, I could sign up for a session or two online.
Schedule can be found at
And just in time for the language summit! :)
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Dong-hee Na wrote:
[SNIP]
> cc.
> If I had to wait for the announcement of the Steering Committee
> (https://discuss.python.org/t/vote-to-promote-dong-hee-na/3794/2
> )
> before writing this email,
> Thank you for your understanding in advance.
Nope, no need to wait. Me granting access came after
Assuming I didn't botch anything, Dong-hee should be all set up!
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
With two votes opened in 48 hours, I figured it was a good time to point out
that https://devguide.python.org/coredev/#gaining-commit-privileges outlines
the process of promoting someone from how to structure the vote to getting the
person their commit privileges.
FYI we have codecov configured to turn off the comment (and have since I think
we started using codecov). See the issue for more details about a potential bug
on codecov's side.
___
python-committers mailing list -- python-committers@python.org
To
The steering council is interested in hearing from *core developers* about
their thoughts around the idea of hiring people to help with the project.
The thinking is if we can pay people to help/assist with the aspects of
development that us volunteers do not enjoy doing or simply lack the time.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
I just wanted to say congratulations to everyone for reaching this point! I
know it has been a long time coming and quite the struggle sometimes over the
past decade, but we reached our (extended) end for Python 2 without having the
entire community and language collapse as some had predicted
I want to make two quick points and then I'm bowing out of this conversation as
this isn't going to change anything for this vote beyond the exemption we have
already granted and no changes to PEP 13 have been proposed. I was trying to
avoid this conversation dragging out right now, but people
We discussed the situation on the steering council and we are fine with making
an exception for folks who felt caught off-guard asking Ernest to be added to
the voter roll even though voting has already started.
In the new year I will work with Ernest to draft up a proposal for changing PEP
13
ough the usual vote process?
> > Or should we just add it back whenever they ask?
> > Victor
> > Le mer. 4 déc. 2019 à 21:23, Brett Cannon br...@python.org a écrit :
> > >
> > You ask me to do it. :) I have gone ahead and
> > revoked them.
> > Thanks for all
You ask me to do it. :) I have gone ahead and revoked them.
Thanks for all your help over the years, Lars!
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
Nominations closed out and it looks like the following people will be running:
01. Gregory P. Smith
02. Pablo Galindo Salgado
03. Kushal Das
04. Christian Heimes
05. Victor Stinner
06. Guido van Rossum
07. Thomas Wouters
08. Carol Willing
09. Barry Warsaw
10. Brett Cannon
Thanks to everyone who
The steering council was asked to address the idea of code ownership in the
project, and so we wanted to publicly state that we view everything as
communally owned by everyone on the development team. That means no one has
exclusive control over any part of the code base.
Having said that, we do
In case people are thinking about nominations next month and wanted to know
what it's like and the time commitment involved, I wrote a blog post on the
subject at
https://snarky.ca/what-its-like-to-be-on-the-python-steering-council/.
___
In case people didn't notice, the poll closed and Thomas' proposal passed with
97% of the vote.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
[this is being emailed out to python-committer and python-dev separately,
so apologies for those who get a duplicate email]
The steering council wanted to let everyone know that the PSF released a
new Code of Conduct which was announced at
The steering council also proposes that no changes be made to PEP 13 between
Nov 1 and Dec 15.
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
1 - 100 of 530 matches
Mail list logo
