[Python-Dev] build cpython on M1 Pro mac

2022-03-01 Thread Yves Duprat 
Hi,

I built cpython on a mac OSX 12.01. Python runs well. 
When starts, Python shows that version info which looks good:
'Python 3.11.0a5+ (heads/fix-issue-43352:f899da7fe5, Feb 25 2022, 10:04:53) 
[Clang 13.0.0 (clang-1300.0.29.30)] on darwin'

But when I want to used it in VSCode to debug a script, I have the following 
message:
---
This version of python seems to be incorrectly compiled
(internal generated filenames are not absolute).
This may make the debugger miss breakpoints.
Related bug: http://bugs.python.org/issue1666807
---
What do I miss ? I looked for a specific option in ./configure but seen nothing 
 ? 
Can someone help me please ?
Thank

Yves
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/DISAPV26T2U6CHHSGXTD5EWX54CPMB6Z/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] October/November/December Steering Council update

2022-03-01 Thread Pablo Galindo Salgado 
We’ve just published the October, November and December steering council
update for 2021, also included below:

https://github.com/python/steering-council/blob/main/updates/2021-10-steering-council-update.md
https://github.com/python/steering-council/blob/main/updates/2021-11-steering-council-update.md
https://github.com/python/steering-council/blob/main/updates/2021-12-steering-council-update.md

Just as a reminder, if you have any questions or concerns, feel free to
contact us or open an issue in the SC repo:
https://github.com/python/steering-council


*October 11*

   - SC met with the Developer-in-Residence and provided feedback on the
   Developer-in-Residence activity blog.
   - SC decided to keep 2020 dates for 2021 election.
   - SC discussed the draft about the SC's position on the PEP 649 / PEP
   563 situation (stringified annotations) and provided feedback.
   - SC discussed whether or not they should extend their weekly meetings
   and/or do more async communications. They also decided that the SC should
   continue having meetings and working during the elections.


*October 18*

   - Steering Council met with the GitHub Issues PM for an update on the
   migration. Priority right now is getting a testing repo out to the core dev
   sprint and triagers by Wednesday.
   - SC reviewed PEP 663 (Standardizing Enum str(), repr(), and format()
   behaviors) and potential PEP Delegates.
   - SC reviewed and discussed issues open on
   https://github.com/python/steering-council/issues


*October 19*

   - SC met with the Search Firm the PSF is using for the Executive
   Director search, to provide input on the search parameters, and suggest
   potential candidates.


*October 25*

   - Steering Council did a one hour Q&A recorded session with Visionary
   sponsor, Bloomberg.
   - Steering Council discussed PEP 649 and PEP 563 (stringified
   annotations). The group may want to delegate this to Łukasz but will
   discuss this more next week.
   - The candidate PEP Delegate for PEP 663 (Standardizing Enum str(),
   repr(), and format() behaviors) declined. The Steering Council will think
   of who else it can be delegated to, or take it on themselves.

November 1

   - The SC discussed PEP 649 -- Deferred Evaluation Of Annotations Using
   Descriptors  & PEP 563 --
   Postponed Evaluation of Annotations
   . The SC decided it would
   tell the community that more information is needed. Barry will draft an
   email explaining the current situation and calling for help from static and
   dynamic typing users.
   - The SC reviewed the open issues in the public Steering Council repo:
   https://github.com/python/steering-council/issues.
   - The SC discussed SC promotion during the call for nomination period,
   which started on Nov 1.
   - The SC discussed PEP 663 - Standardizing Enum str(), repr(), and
   format() behaviors  and that
   Barry would write the rejection draft.
   - Brett informed the SC of an issue involving the return type of
   iterators and the SC decided it would continue discussing it at the next
   meeting (https://bugs.python.org/issue45250).

November
8

   - The SC had their bi-weekly meeting with the Developer-in-Residence.
   Received an update from Łukasz on what he is working on.
   - The SC discussed PEP 663 - Standardizing Enum str(), repr(), and
   format() behaviors  and after
   some initial discussion, it was decided that it needs more discussion on
   python-dev@.
   - The SC discussed PEP 467 -- Minor API improvements for binary sequences
   . bchr() was taken out like
   the SC had requested and then an ascii() method was added in without any
   mention. Pablo will draft a response.
   - PEP 554 -- Multiple Interpreters in the Stdlib
    was discussed. A proof of
   concept is needed and the SC is not yet ready to review the PEP without it.

November
15

   - The SC met with Ezio and got an update on what Ezio was working on. SC
   told Ezio not to be overly concerned with perfection and not to strive for
   it. The SC gave Ezio a deadline of Dec 7th to get everything migrated over.
   - The SC discussed a PR to the CPython repo regarding __iter__ and
   iterators being inconsistently required by CPython (
   https://github.com/python/cpython/pull/29170). The SC's decision was to
   update the definitions to say it's a CPython implementation detail that it
   is inconsistent in its checking whether what an iterable returns is a
   proper iterator or not (i.e. keep the __iter__ requirement but admit it

[Python-Dev] Re: October/November/December Steering Council update

2022-03-01 Thread Joannah Nanjekye 
> Steering Council did a one hour Q&A recorded session with Visionary
sponsor, Bloomberg.

Is it possible to access this recording for transparency purposes or is
it confidential?

I saw some people in another language community on a twitter thread where
people were having
rumours and speculations of similar discussions, thinking such companies
influence community decisions.

Disclaimer: I personally trust the SC.



On Tue, Mar 1, 2022 at 7:39 PM Pablo Galindo Salgado 
wrote:

> We’ve just published the October, November and December steering council
> update for 2021, also included below:
>
>
> https://github.com/python/steering-council/blob/main/updates/2021-10-steering-council-update.md
>
> https://github.com/python/steering-council/blob/main/updates/2021-11-steering-council-update.md
>
> https://github.com/python/steering-council/blob/main/updates/2021-12-steering-council-update.md
>
> Just as a reminder, if you have any questions or concerns, feel free to
> contact us or open an issue in the SC repo:
> https://github.com/python/steering-council
>
>
> *October 11*
>
>- SC met with the Developer-in-Residence and provided feedback on the
>Developer-in-Residence activity blog.
>- SC decided to keep 2020 dates for 2021 election.
>- SC discussed the draft about the SC's position on the PEP 649 / PEP
>563 situation (stringified annotations) and provided feedback.
>- SC discussed whether or not they should extend their weekly meetings
>and/or do more async communications. They also decided that the SC should
>continue having meetings and working during the elections.
>
>
> *October 18*
>
>- Steering Council met with the GitHub Issues PM for an update on the
>migration. Priority right now is getting a testing repo out to the core dev
>sprint and triagers by Wednesday.
>- SC reviewed PEP 663 (Standardizing Enum str(), repr(), and format()
>behaviors) and potential PEP Delegates.
>- SC reviewed and discussed issues open on
>https://github.com/python/steering-council/issues
>
>
> *October 19*
>
>- SC met with the Search Firm the PSF is using for the Executive
>Director search, to provide input on the search parameters, and suggest
>potential candidates.
>
>
> *October 25*
>
>- Steering Council did a one hour Q&A recorded session with Visionary
>sponsor, Bloomberg.
>- Steering Council discussed PEP 649 and PEP 563 (stringified
>annotations). The group may want to delegate this to Łukasz but will
>discuss this more next week.
>- The candidate PEP Delegate for PEP 663 (Standardizing Enum str(),
>repr(), and format() behaviors) declined. The Steering Council will think
>of who else it can be delegated to, or take it on themselves.
>
> November 1
>
>- The SC discussed PEP 649 -- Deferred Evaluation Of Annotations Using
>Descriptors  & PEP 563 --
>Postponed Evaluation of Annotations
>. The SC decided it would
>tell the community that more information is needed. Barry will draft an
>email explaining the current situation and calling for help from static and
>dynamic typing users.
>- The SC reviewed the open issues in the public Steering Council repo:
>https://github.com/python/steering-council/issues.
>- The SC discussed SC promotion during the call for nomination period,
>which started on Nov 1.
>- The SC discussed PEP 663 - Standardizing Enum str(), repr(), and
>format() behaviors  and
>that Barry would write the rejection draft.
>- Brett informed the SC of an issue involving the return type of
>iterators and the SC decided it would continue discussing it at the next
>meeting (https://bugs.python.org/issue45250).
>
>
> November
> 8
>
>- The SC had their bi-weekly meeting with the Developer-in-Residence.
>Received an update from Łukasz on what he is working on.
>- The SC discussed PEP 663 - Standardizing Enum str(), repr(), and
>format() behaviors  and
>after some initial discussion, it was decided that it needs more discussion
>on python-dev@.
>- The SC discussed PEP 467 -- Minor API improvements for binary
>sequences . bchr() was
>taken out like the SC had requested and then an ascii() method was
>added in without any mention. Pablo will draft a response.
>- PEP 554 -- Multiple Interpreters in the Stdlib
> was discussed. A proof of
>concept is needed and the SC is not yet ready to review the PEP without it.
>
>
> November
> 15
>
>

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

2022-03-01 Thread Guido van Rossum 
How did you find that issue? It seems unlikely that a problem with 3.11 is
caused by an issue reported for Python 2.5 in 2007.

My own understanding of the problem with the VS Code debugger and 3.11
(which I have experienced myself as well :-) is that since 3.11 is still in
alpha mode, the Pydev extension used by VS Code doesn't yet work well with
the changes in 3.11 internals. You should probably inquire with either the
Pydev extension (https://github.com/fabioz/Pydev) or the VS Code team about
what their plans are for fixing this -- I wouldn't blame them if they
decided to wait until 3.11 beta 1 is released, which should happen on or
after May 6th this year.

On Tue, Mar 1, 2022 at 8:25 AM Yves Duprat  wrote:

> Hi,
>
> I built cpython on a mac OSX 12.01. Python runs well.
> When starts, Python shows that version info which looks good:
> 'Python 3.11.0a5+ (heads/fix-issue-43352:f899da7fe5, Feb 25 2022,
> 10:04:53) [Clang 13.0.0 (clang-1300.0.29.30)] on darwin'
>
> But when I want to used it in VSCode to debug a script, I have the
> following message:
> ---
> This version of python seems to be incorrectly compiled
> (internal generated filenames are not absolute).
> This may make the debugger miss breakpoints.
> Related bug: http://bugs.python.org/issue1666807
> ---
> What do I miss ? I looked for a specific option in ./configure but seen
> nothing  ?
> Can someone help me please ?
> Thank
>
> Yves
> ___
> Python-Dev mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/DISAPV26T2U6CHHSGXTD5EWX54CPMB6Z/
> Code of Conduct: http://python.org/psf/codeofconduct/
>


-- 
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*

___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/56TM7JH7MFTEHFWPKBRE3MWVG6CRIPO4/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: October/November/December Steering Council update

2022-03-01 Thread Brett Cannon 
On Tue, Mar 1, 2022 at 9:00 AM Joannah Nanjekye 
wrote:

> > Steering Council did a one hour Q&A recorded session with Visionary
> sponsor, Bloomberg.
>
> Is it possible to access this recording for transparency purposes or is
> it confidential?
>

We can ask, but I vaguely remember the folks at Bloomberg being told they
could ask us questions involving internal tech.


>
> I saw some people in another language community on a twitter thread where
> people were having
> rumours and speculations of similar discussions, thinking such companies
> influence community decisions.
>
>
If I remember correctly it was the same type of questions we have gotten
from the host of the core dev sprints: where do you see things going, do
you have plans for this, what's the next challenge for Python, etc. It's
actually just like the kind of Q&A that has occurred at PyCon US as well.
Usually the private nature stems more from people saying, "we have this
system at work that does this and what do you think of that," and not any
influence campaign.

The fact that I can't remember what was asked shows how influential the Q&A
was. 😄

And in case anyone happens to be ever concerned, the 2/5 rule for any
single company being on the SC is a direct way this is kind of concern is
stopped. After that is not voting for anyone you think won't put Python's
best interest ahead of corporate interests.


> Disclaimer: I personally trust the SC.
>

Thanks! 🙂

-Brett


>
>
>
> On Tue, Mar 1, 2022 at 7:39 PM Pablo Galindo Salgado 
> wrote:
>
>> We’ve just published the October, November and December steering council
>> update for 2021, also included below:
>>
>>
>> https://github.com/python/steering-council/blob/main/updates/2021-10-steering-council-update.md
>>
>> https://github.com/python/steering-council/blob/main/updates/2021-11-steering-council-update.md
>>
>> https://github.com/python/steering-council/blob/main/updates/2021-12-steering-council-update.md
>>
>> Just as a reminder, if you have any questions or concerns, feel free to
>> contact us or open an issue in the SC repo:
>> https://github.com/python/steering-council
>>
>>
>> *October 11*
>>
>>- SC met with the Developer-in-Residence and provided feedback on the
>>Developer-in-Residence activity blog.
>>- SC decided to keep 2020 dates for 2021 election.
>>- SC discussed the draft about the SC's position on the PEP 649 / PEP
>>563 situation (stringified annotations) and provided feedback.
>>- SC discussed whether or not they should extend their weekly
>>meetings and/or do more async communications. They also decided that the 
>> SC
>>should continue having meetings and working during the elections.
>>
>>
>> *October 18*
>>
>>- Steering Council met with the GitHub Issues PM for an update on the
>>migration. Priority right now is getting a testing repo out to the core 
>> dev
>>sprint and triagers by Wednesday.
>>- SC reviewed PEP 663 (Standardizing Enum str(), repr(), and format()
>>behaviors) and potential PEP Delegates.
>>- SC reviewed and discussed issues open on
>>https://github.com/python/steering-council/issues
>>
>>
>> *October 19*
>>
>>- SC met with the Search Firm the PSF is using for the Executive
>>Director search, to provide input on the search parameters, and suggest
>>potential candidates.
>>
>>
>> *October 25*
>>
>>- Steering Council did a one hour Q&A recorded session with Visionary
>>sponsor, Bloomberg.
>>- Steering Council discussed PEP 649 and PEP 563 (stringified
>>annotations). The group may want to delegate this to Łukasz but will
>>discuss this more next week.
>>- The candidate PEP Delegate for PEP 663 (Standardizing Enum str(),
>>repr(), and format() behaviors) declined. The Steering Council will think
>>of who else it can be delegated to, or take it on themselves.
>>
>> November 1
>>
>>- The SC discussed PEP 649 -- Deferred Evaluation Of Annotations
>>Using Descriptors  & PEP
>>563 -- Postponed Evaluation of Annotations
>>. The SC decided it would
>>tell the community that more information is needed. Barry will draft an
>>email explaining the current situation and calling for help from static 
>> and
>>dynamic typing users.
>>- The SC reviewed the open issues in the public Steering Council
>>repo: https://github.com/python/steering-council/issues.
>>- The SC discussed SC promotion during the call for nomination
>>period, which started on Nov 1.
>>- The SC discussed PEP 663 - Standardizing Enum str(), repr(), and
>>format() behaviors  and
>>that Barry would write the rejection draft.
>>- Brett informed the SC of an issue involving the return type of
>>iterators and the SC decided it would continue discussing it at the next
>>meeting (https://bugs.python.org/issue45250

[Python-Dev] Making Cinder more broadly available

2022-03-01 Thread Dino 
Hi,

Cinder  is Meta’s
performance-oriented version of CPython 3.8. It has been in use as the
production Python behind Instagram server for years, as well as powering
various other Python applications across Meta.

We are interested in making the improvements in Cinder more broadly
available to the Python community. As a collection of features and
components built on top of CPython, we’d like to:

   1. Merge the feature into CPython for core features that are highly
   coupled with CPython internals (after we port it over to the main branch)
   2. For features that *can* work as extension modules (like Cinder JIT) -
   extract them as a new open source standalone pip-installable extension
   module.
   3. To enable the pip-installable extension module, we will need to add a
   few extension hooks to CPython,
   which we intend to carve out and port over to the main branch in order
   to merge upstream.

Please read more about our upstreaming strategy and a few Cinder features
in this document:
https://docs.google.com/document/d/1l8I-FDE1xrIShm9eSNJqsGmY_VanMDX5-aK_gujhYBI/edit?usp=sharing

Complete source code of our CPython fork:
https://github.com/facebookincubator/cinder

We started filing bpo issues for a few of the pieces we want to merge
upstream (links are in the google doc), and are looking forward to feedback
from the community on the issues, overall approach, or any feedback on the
features themselves.

Cheers,
Dino
___
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/4HLXWXJTZD2YHMBZIDBJ2RCWNDHWSUYV/
Code of Conduct: http://python.org/psf/codeofconduct/