[python-committers] Re: Python Language Summit at PyCon 2022 in Salt Lake City

[Mariatta]

Last call!

Please sign up for the language summit before this Saturday.

We received a number of topic proposals in the last few days, and we still
have room for more, so don't delay.

Full details at: https://us.pycon.org/2022/events/language-summit/

When: Wednesday, April 27, 2022
Where: in person during PyCon US, Salt Palace Convention Center, room TBD

Sign up to attend:  https://forms.gle/CS8B6wJdcaN3rtWV8  (closes March 25
th, 2022 AoE)
Sign up to discuss a topic: https://forms.gle/LAFE6TTYi15jL5RaA (closes
March 25th, 2022 AoE)



On Mon, Mar 21, 2022 at 9:14 AM Mariatta  wrote:

> Hi everybody,
>
> Just sending out a reminder to sign up for the language summit. The
> signups are open until EOD Friday this week.
>
> *When:* Wednesday, April 27, 2022
> *Where:* in person during PyCon US, Salt Palace Convention Center, room
> TBD
>
> *Sign up to attend:*  https://forms.gle/CS8B6wJdcaN3rtWV8
>  (closes March 25 th, 2022 AoE)
> *Sign up to discuss a topic:* https://forms.gle/LAFE6TTYi15jL5RaA (closes
> March 25th, 2022 AoE)
>
> Currently the room is more than half full! We have close to 30
> attendees signing up, but we haven't received a lot of presentation
> proposals yet. (less than 5)
>
> From the signups, it seems like attendees are interested in discussing
> topics like: Cinder, Faster CPython, and various PEPs. So if you've been
> thinking about submitting a proposal, please do it soon!
>
> Thank you,
>
> Mariatta, Łukasz, & Senthil
>
>
___
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 
https://mail.python.org/archives/list/python-committers@python.org/message/O7CY7EQZRBLR3KU6JA6CBBJOQWYXNMXA/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Proposed tiered platform support

[Brett Cannon]

Based on the positive feedback that I've gotten on this and the only other
suggestion was maybe bringing back tier 3 to represent, "being actively
worked on" support (which i think we can add later if we feel it's worth
it), I'm ready to ask folks to please start sending review suggestions on
https://github.com/python/peps/pull/2442 to add yourself as supporting a
platform (see
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request
if you don't know what I mean by "review suggestion").

I believe at least Victor is currently out at the moment, so I'm not
planning to rush this out and start removing platforms that lack two people
and merging this PR, but I also don't want to put it off either. As a
reminder, the platforms looking for declared support as a tier 2 platform
are:


   1. arch64-apple-darwin clang
   2. aarch64-linux-gnu glibc, gcc
   3. aarch64-linux-gnu glibc, clang
   4. aarch64-windows-msvc
   5. powerpcle-linux-gnu glibc, gcc
   6. powerpcle-linux-gnu glibc, clang
   7. s390x-linux-gnu glibc, gcc
   8. s390x-linux-gnu glibc, clang
   9. x86_64-linux-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 everyone's feedback, here are my proposed explanations
> for the tiers.
>
> Tier 1
> --
>
> - `CI failures <
> https://github.com/python/cpython/actions/workflows/build.yml?query=branch%3Amain+is%3Acompleted>`__
> block releases.
> - Changes which would break the ``main`` branch are not allowed to be
> merged;
>   any breakage may be reverted immediately.
> - All core developers are responsible to keep these platforms,
>   and thus ``main``, working.
> - Promotion to this tier requires team consensus/SC approval.
>
> Tier 2
> --
>
> - Must have a reliable buildbot.
> - At least **two** core developers are signed up to support the platform.
> - Changes which break any of these platforms are to be fixed or
>   reverted within 24 hours.
> - Failures on these platforms block a release.
> - Promotion to this tier requires consensus/SC approval.
>
> All other platforms
> ---
>
> Support for a platform may be partial within the code base, such as
> from active development around platform support or accidentally.
> Code changes to platforms not listed in the above tiers may rejected
> or removed from the code base without a deprecation process if they
> cause a maintenance burden or obstruct general improvements.
>
> Platforms not listed here may be supported by the wider Python
> community in some way. If your desired platform is not listed above,
> please perform a search online to see if someone is already providing
> support in some form.
>
>
> I have a draft PR up at https://github.com/python/peps/pull/2442 which
> can be previewed at
> https://pep-previews--2442.org.readthedocs.build/pep-0011/ (makes reading
> the table much easier). I made the platforms list the platform triple,
> libc, and compiler **without** version details.
>
> Once I have buy-in for the above I will explicitly ask folks to send
> review comments to that PR to add themselves to the platforms they are
> willing to support, and then drop any which lack two core developers
> (warnings to the Fedora/RH folks: most of those platforms are listed are
> using Fedora buildbots, so it might be up  to you ). I did drop
> powerpc-linux-gnu from the 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:
>>> > Greg proposed something like "Code changes to support platforms beyond
>>> tier1 or
>>> > tier2 may be rejected, broken, or removed from the CPython codebase
>>> without
>>> > notice if they cause a maintenance burden for tier1&2 or obstruct
>>> general
>>> > improvements." and drop the concept of tier 3. Does that work for you?
>>>
>>> Almost :-) I don't understand the "without notice". I guess Greg
>>> meant "without deprecation process". Removal of support code should
>>> be discussed on a ticket and then listed in PEP 11 and
>>> mentioned in the NEWS file, as usual.
>>>
>>
>> I guess I was trying to convey that we may not even have a way to know
>> that we're breaking something on a non-tier1/2 platform anyways so "without
>> notice" was just me trying to set people's expectations.  We don't go out
>> of our way to _try_ and break things most of the time.  "without a
>> deprecation process" is also reasonable wording.  Feel free to adopt those
>> words.
>>
>> Ideally we try to have discussion somewhere relevant when we _know_ we'd
>> intentionally be 

[python-committers] [RELEASE] Python 3.10.4 and 3.9.12 are now available out of schedule

[Łukasz Langa]

Did anybody say cursed releases 
?
 Well, it turns out that 3.10.3 and 3.9.11 both shipped a regression which 
caused those versions not to build on Red Hat Enterprise Linux 6. While this 
11-year-old version is now out of maintenance support 
, it’s still used in 
production workloads. Some of those rely on Python 3.9 and/or 3.10. In 
particular, our own manylinux2010 

 image used to build widely compatible Linux wheels is based on CentOS 6. 
(Don’t worry, we do have newer manylinux* variants, see PEP 599 
 and PEP 600 
 for details.)

Due to the out-of-schedule release, the respective versions released today 
contain a very limited set of changes. Python 3.9.12 only contains 12 other bug 
fixes on top of 3.9.11. Python 3.10.4 only contains 10 other bug fixes on top 
of 3.10.3.

Get 3.10.4 here: Python Release 3.10.4 | Python.org 

Get 3.9.12 here: Python Release 3.9.12 | Python.org 

Hopefully, the third time’s a charm and we’ll return no sooner than May with 
the regularly scheduled bug fix releases of 3.9 and 3.10.

 
We
 hope you enjoy the new releases

Your friendly release team,
Łukasz Langa @ambv 
Pablo Galindo Salgado @pablogsal 
Ned Deily @nad 
Steve Dower @steve.dower 


signature.asc
Description: Message signed with OpenPGP
___
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 
https://mail.python.org/archives/list/python-committers@python.org/message/SGB4B572RDPZ7SIJ5A6NZAI3Z3GKNIXA/
Code of Conduct: https://www.python.org/psf/codeofconduct/