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:
> • arch64-apple-darwin clang [...]
I added this comment to the PR:
If x86_64-appl
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 is already listed)
3. aarch64-windows-msvc
4. powerpcle-lin
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 h
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". IMO you must also put two names in front of each
platform. Otherwise, nobody will fix them when
Ok, I added myself on the PR.
Victor
___
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 archiv
On 25. 03. 22 11:43, Victor Stinner wrote:
You wrote that you want at least 2 core devs responsible for each tier
1 platform. I didn't understand if this requirement is also for Tier
2.
Who are these core devs? Is there a list?
The list will be in the PEP. Add yourself at
https://github.com/p
You wrote that you want at least 2 core devs responsible for each tier
1 platform. I didn't understand if this requirement is also for Tier
2.
Who are these core devs? Is there a list?
Victor
___
python-committers mailing list -- python-committers@pytho
