Mailman 3 August 2021 - Python-Dev

API's to interface python with Eclipse to execute and debug C/C++ Source files.
by Chandrakant Shrimantrao Sept. 4, 2021

Sept. 4, 2021

Hi, We would like to know if there is any option available to execute and debug( setting break point and delete break point) C/C++ Source files Python API's inside Eclipse IDE after interfacing Pydev with Eclipse. Please let us know. Thanks and regards. Chandrakant shrimantrao. L&T Technology Services Ltd www.LTTS.com L&T Technology Services Limited (LTTS) is committed to safeguard your data privacy. For more information to view our commitment towards data privacy under GDPR, … [View More]

3 2

Is anyone relying on new-bugs-announce/python-bugs-list/bugs.python.org summaries
by Ammar Askar Sept. 3, 2021

Sept. 3, 2021

Hey everyone, As part of PEP 588, migrating bugs.python.org issues to Github, there are two current mailing list related items that need a replacement or need to be turned down. 1. Weekly summary emails with bug counts and issues from the week, example: https://mail.python.org/archives/list/python-dev@python.org/thread/JRFJ4QH7… 2. Emails sent to the new-bugs-announce and python-bugs-list for new issues and comments to existing issues. I wanted to quickly gauge if anyone is relying on … [View More]

7 6

PEP-535 (Rich comparison chaining) Discussion?
by Angus Hollands Sept. 2, 2021

Sept. 2, 2021

Hi all, PEP 535 was deferred until Python 3.8. I would like to discuss the PEP given that some time has passed, and I _personally_ would benefit from its acceptance. ## A little about me: As a reasonably long-time Python user (well, 16 years), I have gradually moved from using only the core language to working within the DSLs (NumPy et al.) of the Scientific Python ecosystem. Most recently, I've been using Awkward Arrray (https://github.com/scikit-hep/awkward-1.0), which generalises the … [View More]regular NumPy array programming paradigm into "jagged" data structures, and was initially aimed at the High Energy Physics (HEP) domain. ## TL;DR of the PEP's Motivations: Various aspects of NumPy's API have become a "lingua-franca" in the Scientific Python domain, such as strongly-overloaded index operations. One such overload allows "mask arrays" — arrays with boolean entries corresponding to a per-element mask — to select a subset of the array. These mask arrays are conveniently built from the rich comparison operators that Python supports, e.g. ```python x = np.array(...) y = x[(2 < x) & (x < 8)] ``` As discussed in PEP 535, the limitation on comparison chaining (namely that it is not possible for rich comparisons) makes the above syntax more clunky than it might otherwise be. The main repercussion of this limitation is lower readability: - operator precedence of bitwise and/or requires a reasonable number of parentheses (https://docs.python.org/3/reference/expressions.html#operator-precedence) - repetition of the rich-object (array) With PEP 535 (and the necessary library changes), this would look more like ```python x = np.array(...) y = x[2 < x < 8] ``` This is already well described in the PEP, so I'll leave the example there! ## Community Survey The Oct 2020 Python Developers Survey (https://www.jetbrains.com/lp/python-developers-survey-2020/) suggests that 62% of respondents use NumPy. Additionally, 37% of respondents list "Simple syntax, syntactic sugar, easy to learn" and 30% list "Easy to write & read code, high-level language" amongst their three most liked features in the Python language (to clarify, these answers may overlap by respondent!) From these results, I would make a tentative case that this PEP would have a reasonable impact on the Python community, given that libraries benefitting from this proposal (e.g. NumPy) are used by a "majority" of those surveyed. ## Conclusion This is a bit of a long opener to this list (apologies!). Is there any interest in pushing this PEP along? Thanks, Angus Hollands [View Less]

4 4

[RELEASE] Python 3.9.7 and 3.8.12 are now available
by Łukasz Langa Aug. 30, 2021

Aug. 30, 2021

Python 3.9.7 Get it here: https://www.python.org/downloads/release/python-397/ <https://www.python.org/downloads/release/python-397/> Python 3.9.7 is the newest major stable release of the Python programming language, and it contains many new features and optimizations. There’s been 187 commits since 3.9.6 which is a similar amount compared to 3.8 at the same stage of the release cycle. See the change log <https://docs.python.org/release/3.9.7/whatsnew/changelog.html> for details. … [View More]On macOS, we encourage you to use the universal2 binary installer variant whenever possible. The legacy 10.9+ Intel-only variant will not be provided for Python 3.10 and the universal2 variant will become the default download for 3.9.8. You may need to upgrade third-party components, like pip, to later versions. You may experience differences in behavior in IDLE and other Tk-based applications due to using the newer version of Tk. As always, if you encounter problems when using this installer variant, please check https://bugs.python.org <https://bugs.python.org/> for existing reports and for opening new issues. The next Python 3.9 maintenance release will be 3.9.8, currently scheduled for 2021-11-01. <https://discuss.python.org/t/python-3-9-7-and-3-8-12-now-available/10401#th…>The Second Security-Only Release of Python 3.8 Get it here: https://www.python.org/downloads/release/python-3812/ <https://www.python.org/downloads/release/python-3812/> Security content in this release contains four fixes. There are also four additional fixes for bugs that might have lead to denial-of-service attacks. Finally, while we’re not providing binary installers anymore, for those users who produce installers, we upgraded the OpenSSL version used to 1.1.1l. Take a look at the change log <https://docs.python.org/release/3.8.12/whatsnew/changelog.html> for details. According to the release calendar specified in PEP 569 <https://www.python.org/dev/peps/pep-0569/>, Python 3.8 is now in “security fixes only” stage of its life cycle: 3.8 branch only accepts security fixes and releases of those are made irregularly in source-only form until October 2024. Python 3.8 isn’t receiving regular bug fixes anymore, and binary installers are no longer provided for it. Python 3.8.10 was the last full bugfix release of Python 3.8 with binary installers. <https://discuss.python.org/t/python-3-9-7-and-3-8-12-now-available/10401#se…>Security releases of 3.7.12 and 3.6.15 Those aren’t ready just yet but are soon to follow. Similarly to 3.8, Python 3.7 and 3.6 are now in “security fixes only” stage of their life cycle. Python 3.7 will be providing source archives until June 2023 while Python 3.6 ends its life in December 2021. <https://discuss.python.org/t/python-3-9-7-and-3-8-12-now-available/10401#we…>We hope you enjoy the new releases Your friendly release team, Ned Deily @nad <https://discuss.python.org/u/nad> Steve Dower @steve.dower <https://discuss.python.org/u/steve.dower> Łukasz Langa @ambv <https://discuss.python.org/u/ambv> [View Less]

1 0

(Adaptive) Shivers sort variant of Tim sort
by Laurent Lyaudet Aug. 29, 2021

Aug. 29, 2021

Hello, I developed a C sorting algorithms library that currently has a few dozens of algorithms and thousands of variants when choosing parameters (like threshold for switching to insertion sort, etc.). (I compile each variant on demand in custom tests to avoid having a bloated source file.) My benchmarks could be improved but however I found that Shivers' sort and adaptive Shivers' sort (aka Jugé's sort) performs better than Tim's sort. I don't know if it will still be true with the … [View More]benchmarks in Python. If you're open to the idea that maybe Tim's sort can be improved and are willing to benchmark it, it can be done easily by switching the main natural merge strategy like I did here : https://github.com/LLyaudet/TSODLULS/commit/2968c4b4ca58ae794157dc9636ed870… The relevant code is not very long : /** * This strategy is from ShiversSort: * see the research report by Olin Shivers, Georgia Institute of Technology, 2002. * It uses bitwise tricks to check condition on floor of logarithms in base 2 of runs lengths. * When I benchmark it, it is slightly faster than Tim's sort strategy. */ #define TSODLULS_natural_merge_main_strategy__Shivers_sort \ while(merge_state.i_run_instances_count > 1){\ size_t i_merge_at = merge_state.i_run_instances_count - 2;\ size_t i_order_of_magnitude = merge_state.arr_run_instances[i_merge_at + 1].i_length;\ if(i_order_of_magnitude < ((~i_order_of_magnitude) & merge_state.arr_run_instances[i_merge_at].i_length) ){\ break;\ }\ i_compare_result = TSODLULS_MERGE_TWO_RUNS(&merge_state, i_merge_at);\ if(i_compare_result != 0){\ goto clean_and_return_error;\ }\ }\ /** * This strategy is from AdaptiveShiversSort: * see the articles by Vincent Jugé, for example 1024 Bulletin de la SIF, avril 2020, in French, * or the preprint on arXiv or SODA 2020 proceedings. * It uses bitwise tricks to check condition on floor of logarithms in base 2 of runs lengths. * When I benchmark it, it is slightly faster than Tim's sort strategy. * Despite its ressemblance with Shivers's sort, * the distinct properties of this strategy make that JugéSort would probably be a better name than AdaptiveShiversSort, * or an even better name for the whole algorithm should be TimShiversJugéSort and I must have missed many names ;) * With AdaptiveShiversSort we avoid 'é' and diacritics in function names ;P */ #define TSODLULS_natural_merge_main_strategy__adaptive_Shivers_sort \ while(merge_state.i_run_instances_count > 2){\ size_t i_merge_at = merge_state.i_run_instances_count - 3;\ size_t i_order_of_magnitude = merge_state.arr_run_instances[i_merge_at + 1].i_length | merge_state.arr_run_instances[i_merge_at + 2].i_length;\ if(i_order_of_magnitude < ((~i_order_of_magnitude) & merge_state.arr_run_instances[i_merge_at].i_length) ){\ break;\ }\ i_compare_result = TSODLULS_MERGE_TWO_RUNS(&merge_state, i_merge_at);\ if(i_compare_result != 0){\ goto clean_and_return_error;\ }\ }\ In my library the merge strategy is a parameter and I switch its macro when compiling competitors algorithms on demand. I hope it may help. Thanks for your time. If you want to look further at my library, it works with gcc and glibc. I have not tested it on other platforms and whilst I have no compilation warning on my personal dev laptop, I do have one when I run it on the laptop I'm currently writing this email. The tests passes nevertheless. Best regards, Laurent Lyaudet [View Less]

2 2

Summary of Python tracker Issues
by Python tracker Aug. 27, 2021

Aug. 27, 2021

ACTIVITY SUMMARY (2021-08-20 - 2021-08-27) 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: open 7413 (+15) closed 49352 (+54) total 56765 (+69) Open issues with patches: 2935 Issues opened (49) ================== #42085: Add dedicated slot for sending values https://bugs.python.org/issue42085 reopened by pablogsal #44964: Semantics of PyCode_Addr2Line(… [View More]

1 0

A ban from Core Developer spaces.
by Thomas Wouters Aug. 27, 2021

Aug. 27, 2021

All, After some consideration at our weekly meeting (this monday), and a recommendation from the Conduct WG (last friday), the Steering Council has decided to ban Marco Sulla from all Core Developer spaces for at least a year. (For the record, Brett abstained from voting on this issue.) We also agreed to add Ethan to the python-dev moderators, who's already taken the more specific action of banning Marco from python-dev for 3 months. If anyone else is interested in assisting with moderation on … [View More]

4 4

My apologies to the list
by Brett Cannon Aug. 27, 2021

Aug. 27, 2021

I just wanted to apologize for any angst or noise my replies to Marco caused folks. I should have known that correcting Marco on how to address me would have triggered an outsized reply (the real intent of that overall email was to communicate the process of banning someone to the rest of the list so people didn't leave faster than we addressed it; obviously didn't work). It appears my judgement was more impaired than I realized while I have been sick. As such, I have amended my rules for when … [View More]

6 5

PEP 667: Consistent views of namespaces
by Mark Shannon Aug. 27, 2021

Aug. 27, 2021

Hi all, I have submitted PEP 667 as an alternative to PEP 558. https://www.python.org/dev/peps/pep-0667/ Nick and I have agreed to disagree on the way to fix locals() and f_locals. We are both in agreement that it needs fixing. In summary, PEP 667 has roughly the same surface behavior as PEP 558 but is simpler and more consistent internally, at the expense of some minor C API backwards incompatibility issues. PEP 558 also has backwards incompatibility issues, but claims to be more … [View More]

8 22

Notes on PEP 8
by Christopher Barker Aug. 27, 2021

Aug. 27, 2021

As I was working on removing Python 2 references from PEP 8 (PR: https://github.com/python/peps/pull/2059), I tried to avoid any other copy-editing. However, I noted a few things that maybe could use some attention: stdlib or not? ########## Right at the top, it says: "This document gives coding conventions for the Python code comprising the standard library in the main Python distribution." However, it has become a de facto standard for all Python code, and in the document itself, there … [View More]

5 4