[Python-Dev] Re: build cpython on M1 Pro mac

Guido van Rossum wrote: > On Wed, Mar 2, 2022 at 8:34 AM Yves Duprat ydup...@gmail.com wrote: > > How did you find that issue? > > This message printed from VSCode when I ran my script in debug mode > > Oh, I see, this is something that pydevd prints when it doesn't understand > the .pyc file. We

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

Hi, I will add a link to https://docs.python.org/dev/c-api/init_config.html#python-path-configuration as we're trying to at least mention every way sys.path can be initialised. I think the audience for the C API docs are likely to be more knowledgeable than those reading the Setup and Usage

[Python-Dev] Summary of Python tracker Issues

ACTIVITY SUMMARY (2022-02-25 - 2022-03-04) Python tracker at https://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open7224 ( +4) closed 51425 (+62) total 58649 (+66) Open issues

[Python-Dev] Re: Defining tiered platform support

On Fri, Mar 4, 2022 at 12:48 AM Christian Heimes wrote: > Hi Brett, > > thanks for starting the discussion! Much appreciated. > > On 04/03/2022 00.30, Brett Cannon wrote: > > Tier 1 is the stuff we run CI against: latest Windows, latest macOS, > > Linux w/ the latest glibc (I don't know of a

[Python-Dev] Re: Defining tiered platform support

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 > > https://www.python.org/dev/peps/pep-0011/#supporting-platforms > >

[Python-Dev] Re: Defining tiered platform support

On Fri, Mar 4, 2022 at 1:32 AM Ronald Oussoren wrote: > > > On 4 Mar 2022, at 00: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 > https://www.python.org/dev/peps/pep-0011/#supporting-platforms , but that > just

[Python-Dev] Re: Defining tiered platform support

Hi Brett, thanks for starting the discussion! Much appreciated. On 04/03/2022 00.30, Brett Cannon wrote: Tier 1 is the stuff we run CI against: latest Windows, latest macOS, Linux w/ the latest glibc (I don't know of a better way to define Linux support as I don't know if a per-distro list is

[Python-Dev] Re: Defining tiered platform support

> On 4 Mar 2022, at 00: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 > https://www.python.org/dev/peps/pep-0011/#supporting-platforms > , but

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

Unrelated to the doc, now that getpath has been rewritten in pure Python, thanks to Steve Dower!, it would be nice to move the last bits of the sys.path initialization from the site module to the getpath module. It's unpleasant to have a different sys.path depending if the site module is loaded or

[Python-Dev] Re: Defining tiered platform support

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 https://www.python.org/dev/peps/pep-0011/#supporting-platforms , but that just loosely

[Python-Dev] Re: Defining tiered platform support

+10 on making the tier platform support explicit. I would vote not to require involving the SC in the tier changes unless there is a strong reason to do so (e.g. there is controversy, or e.g. Tier 1 implies a commitment of PSF infrastructure). The SC has a lot of decisions to make as it is &

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

On 3/4/22, Victor Stinner wrote: > it would be nice to move the last bits of the sys.path initialization > from the site module to the getpath module. It's unpleasant to > have a different sys.path depending if the site module is loaded > or not. I don't understand. The site packages