[Python-Dev] Re: Defining tiered platform support

On 08. 03. 22 0:30, Brett Cannon wrote: On Mon, Mar 7, 2022 at 11:05 AM Christian Heimes > wrote: On 07/03/2022 18.02, Petr Viktorin wrote: >> Why the devguide? I view the list of platforms as important for public >> consumption as for the cor

[Python-Dev] Re: Defining tiered platform support

On Mon, Mar 7, 2022 at 11:05 AM Christian Heimes wrote: > On 07/03/2022 18.02, Petr Viktorin wrote: > >> Why the devguide? I view the list of platforms as important for public > >> consumption as for the core dev team to know what to (not) accept PRs > >> for. > > > > So, let's put it in the main

[Python-Dev] Re: Defining tiered platform support

On Mon, Mar 7, 2022 at 11:01 AM Christian Heimes wrote: > On 04/03/2022 21.41, Brett Cannon wrote: > > Therefore I propose that we target the oldest manylinux standard > > accepted by PyPI, for which the operating system has not reached its > > EOL. At the moment this is manylinux2014

[Python-Dev] Re: Defining tiered platform support

On 07/03/2022 18.02, Petr Viktorin wrote: Why the devguide? I view the list of platforms as important for public consumption as for the core dev team to know what to (not) accept PRs for. So, let's put it in the main docs? Yes, I guess the devguide is a weird place to check for this kind of i

[Python-Dev] Re: Defining tiered platform support

On 04/03/2022 21.41, Brett Cannon wrote: Therefore I propose that we target the oldest manylinux standard accepted by PyPI, for which the operating system has not reached its EOL. At the moment this is manylinux2014, aka CentOS 2024 with EOL June 2024. We could also state that we

[Python-Dev] [RELEASE] Python 3.11.0a6 is available

There are no easy releases these days! :sweat: After a week of delay due to several release blockers, buildbot problems and pandemic-related difficulties here is 3.11.0a6 for you to test. https://www.python.org/downloads/release/python-3110a6/ **This is an early developer preview of Python 3.11**

[Python-Dev] Re: RFC on PEP 655: Required[] and NotRequired[] for TypedDict

Maybe this shouldn't be called syntax but notation or convention? On Mon, Mar 7, 2022 at 7:00 AM Petr Viktorin wrote: > Hello, > I'm sorry for my late reply -- keeping up with all the PEPs is > somewhat challenging. > > The one nitpick I have is that the PEP should make a few things more > clear

[Python-Dev] Re: Defining tiered platform support

On 04. 03. 22 21:48, Brett Cannon wrote: On Fri, Mar 4, 2022 at 1:44 AM Petr Viktorin > wrote: On 04. 03. 22 0:30, Brett Cannon wrote: > Do we officially support NetBSD? Do you know how to find out if we do? > You might think to look at > ht

[Python-Dev] Re: RFC on PEP 655: Required[] and NotRequired[] for TypedDict

Hello, I'm sorry for my late reply -- keeping up with all the PEPs is somewhat challenging. The one nitpick I have is that the PEP should make a few things more clear to people outside the typing-sig: - if this PEP really only affects typing.py and external projects/tools, it should say so clearly

[Python-Dev] Re: Improvements to the sys.path initialization documentation

On Mon, 7 Mar 2022, 7:42 pm Victor Stinner, wrote: > On Fri, Mar 4, 2022 at 1:37 PM Eryk Sun wrote: > > I don't understand. The site packages directories, including virtual > > environments, are a site extension. > > I propose to change that. Move all code related to sys.path from the > site mod

[Python-Dev] Re: Improvements to the sys.path initialization documentation

On Fri, Mar 4, 2022 at 1:37 PM Eryk Sun wrote: > I don't understand. The site packages directories, including virtual > environments, are a site extension. I propose to change that. Move all code related to sys.path from the site module to the Modules/getpath.py module. Victor -- Night gathers,