🌐 Mailman 3 February 2025 - Python-list - python.org

Re: Book recommendation? For getting up to date
by rbowman Feb. 16, 2025

Feb. 16, 2025

On Sun, 16 Feb 2025 22:00:11 +0100, Jan Erik Moström wrote: > I have done so ... to be really honest, it was when I couldn't remember > how to create an iterator for a class I was writing, that I realized > that I needed a refresher. Most of my Python was related to Esri's ArcGIS version. Up until a few years ago installing their product would install Python 2.7. With Esri 11, they moved to Python 3. Modifying my scripts wasn't difficult but I thought I should expand my Python knowledge. There were quite a few features like list comprehensions I'd never used. I also appreciated f strings when they were introduced, the walrus operator, and other enhancements. Another part of my renewed interest was the advent of many microcontrollers capable of running MicroPython, which is a subset of Python 3.x.

1 0

Re: Book recommendation? For getting up to date
by rbowman Feb. 16, 2025

Feb. 16, 2025

On Sun, 16 Feb 2025 13:50:33 +0100, Jan Erik Moström wrote: > I used to be fairly good at Python, but I haven't done any serious > programming in the last 10 years or so. So I would like something that > got me up-to-date with the latest features. David Beasley's 'Python Distilled'. The author doesn't enumerate Python 3 features specifically but as the title suggests hits the important concepts. https://www.dabeaz.com/python-distilled/

2 1

Building CPython from source, stripping executable
by Keith Thompson Feb. 11, 2025

Feb. 11, 2025

I'm building CPython 3.14.0a5 from source on Ubuntu 22.04.5. Is there some way to specify that the python3.14 executable should be stripped? (Stripping reduces the size of the executable from 33M to 5.8M.) Of course I can run "strip" manually after installing, but I'm looking for a way to do it as part of the build. For a lot of software packages, invoking "make install-strip" rather than "make install" does this, but CPython's generated Makefile doesn't include this target. Diving into the Makefile, I see this: # Option to install to strip binaries STRIPFLAG=-s but STRIPFLAG is used only if PYTHONFRAMEWORKDIR is set, which seems to be Mac-specific. The Makefile also has: INSTALL= /usr/bin/install -c (The "-c" option is ignored by the GNU Coreutils install command.) I tried setting INSTALL to "install -s", and the installation failed because it tried to strip Python scripts as well as the python3.14 executable: install -s -m 644 ./Tools/gdb/libpython.py python-gdb.py strip: python-gdb.py: file format not recognized install: strip process terminated abnormally make: *** [Makefile:1117: python-gdb.py] Error 1 Is there a straightforward way to strip executables during installation? If not, I'll run "strip" manually for now and submit an issue on <https://github.com/python/cpython/issues> suggesting adding an "install-strip" target to the Makefile. I don't think this is a new issue in 3.14.0a5; that's just where I happened to run into it. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u(a)gmail.com void Void(void) { Void(); } /* The recursive call of the void */

1 0

Python 3.14.0 alpha 5
by Hugo van Kemenade Feb. 11, 2025

Feb. 11, 2025

Here comes the antepenultimate alpha. https://www.python.org/downloads/release/python-3140a5/ This is an early developer preview of Python 3.14. Major new features of the 3.14 series, compared to 3.13: Python 3.14 is still in development. This release, 3.14.0a5, is the fifth of seven planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2025-05-06) and, if necessary, may be modified or deleted up until the release candidate phase (2025-07-22). Please keep in mind that this is a preview release and its use is not recommended for production environments. Many new features for Python 3.14 are still being planned and written. Among the new major new features and changes so far: - PEP 649: deferred evaluation of annotations - PEP 741: Python configuration C API - PEP 761: Python 3.14 and onwards no longer provides PGP signatures for release artifacts. Instead, Sigstore is recommended for verifiers. - Improved error messages - A new type of interpreter. For certain newer compilers, this interpreter provides significantly better performance. Opt-in for now, requires building from source. - Python removals and deprecations - C API removals and deprecations - (Hey, fellow core developer, if a feature you find important is missing from this list, let Hugo know.) The next pre-release of Python 3.14 will be the penultimate alpha, 3.14.0a6, currently scheduled for 2025-03-14. More resources: - Online documentation: https://docs.python.org/3.14/ - PEP 745, 3.14 Release Schedule: https://peps.python.org/pep-0745/ - Report bugs at https://github.com/python/cpython/issues - Help fund Python and its community: https://www.python.org/psf/donations/ And now for something completely different! 2025-01-29 marked the start of a new lunar year, the Year of the Snake 🐍 (and the Year of Python?). For centuries, π was often approximated as 3 in China. Some time between the years 1 and 5 CE, astronomer, librarian, mathematician and politician Liu Xin (劉歆) calculated π as 3.154. Around 130 CE, mathematician, astronomer, and geographer Zhang Heng (張衡, 78–139) compared the celestial circle with the diameter of the earth as 736:232 to get 3.1724. He also came up with a formula for the ratio between a cube and inscribed sphere as 8:5, implying the ratio of a square’s area to an inscribed circle is √8:√5. From this, he calculated π as √10 (~3.162). Third century mathematician Liu Hui (刘徽) came up with an algorithm for calculating π iteratively: calculate the area of a polygon inscribed in a circle, then as the number of sides of the polygon is increased, the area becomes closer to that of the circle, from which you can approximate π. This algorithm is similar to the method used by Archimedes in the 3rd century BCE and Ludolph van Ceulen in the 16th century CE (see 3.14.0a2 release notes), but Archimedes only went up to a 96-sided polygon (96-gon). Liu Hui went up to a 192-gon to approximate π as 157/50 (3.14) and later a 3072-gon for 3.14159. Liu Hu wrote a commentary on the book The Nine Chapters on the Mathematical Art which included his π approximations. In the fifth century, astronomer, inventor, mathematician, politician, and writer Zu Chongzhi (祖沖之, 429–500) used Liu Hui’s algorithm to inscribe a 12,288-gon to compute π between 3.1415926 and 3.1415927, correct to seven decimal places. This was more accurate than Hellenistic calculations and wouldn’t be improved upon for 900 years. Happy Year of the Snake! Enjoy the new release Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organisation contributions to the Python Software Foundation. Regards from a remarkably snowless Helsinki, Your release team, Hugo van Kemenade Ned Deily Steve Dower Łukasz Langa

1 0

Version of OpenSSl ?
by vincent.vandevyvre＠oqapy.eu Feb. 10, 2025

Feb. 10, 2025

Hi, Trying to compile Python-3.12.9 on Ubuntu-24.04 The compilation is complete without errors but I have this message: -------------------------------------------------------------------------------------------------------- The necessary bits to build these optional modules were not found: _hashlib _ssl nis To find the necessary bits, look in configure.ac and config.log. Could not build the ssl module! Python requires a OpenSSL 1.1.1 or newer -------------------------------------------------------------------------------------------------------- But I have a more newer version: ------------------------------------------------------------------------------------------------------- $ openssl version OpenSSL 3.0.13 30 Jan 2024 (Library: OpenSSL 3.0.13 30 Jan 2024) ------------------------------------------------------------------------------------------------------- What can I do for that ? Vincent.

5 6

Re: RE Version of OpenSSl ?
by Keith Thompson Feb. 10, 2025

Feb. 10, 2025

vincent.vandevyvre(a)oqapy.eu writes: >> In case this helps you find the correct package to install: >> >> $ python3 -c "if True: >> > import ssl >> > print('Ok.') >> > " >> Ok. >> >> $ cat /etc/lsb-release >> DISTRIB_ID=Ubuntu >> DISTRIB_RELEASE=24.04 >> DISTRIB_CODENAME=noble >> DISTRIB_DESCRIPTION="Ubuntu 24.04.1 LTS" >> >> $ apt list --installed | grep ssl >> >> WARNING: apt does not have a stable CLI interface. Use with caution in >> scripts. >> >> libssl-dev/noble-updates,noble-security,now 3.0.13-0ubuntu3.4 amd64 >> [installed] >> libssl3t64/noble-updates,noble-security,now 3.0.13-0ubuntu3.4 amd64 >> [installed,automatic] >> libxmlsec1t64-openssl/noble,now 1.2.39-5build2 amd64 [installed,automatic] >> openssl/noble-updates,noble-security,now 3.0.13-0ubuntu3.4 amd64 >> [installed,automatic] >> ssl-cert/noble,noble,now 1.1.2ubuntu1 all [installed,automatic] > > Thanks Jason, I have near the same result of you. > I need to explain the context. > I'm on a new machine with a fresh install of Ubuntu 24.04 wich embed Python 3.12.3, no problem with that. > > As I'm maintainer of some Python modules published on PyPI, I've the > habit of testing my modules in different virtual environments. For now > Python 3.11, 3.12 and 3.13. > > So, I've maybe found a solution: > > I've create in my home a dir named /opt, download into it the latest version of openssl-1.1.1 and uncompress it.(*) > ------------------------------------------------------------- > $ cd opt/openssl-1.1.1w > $ ./config && make && make test > $ mkdir $HOME/opt/lib > $ mv $HOME/opt/openssl-1.1.1w/libcrypto.so.1.1 $HOME/opt/lib/ > $ mv $HOME/opt/openssl-1.1.1w/libssl.so.1.1 $HOME/opt/lib/ > $ export LD_LIBRARY_PATH=$HOME/opt/lib:$LD_LIBRARY_PATH > -------------------------------------------------------------- > And rerun the compilation of 3.12.9 without problem with openssl. > > (*) https://openssl-library.org/source/old/1.1.1/index.html OpenSSL 1.1.1 is pretty old, released in 2018 if I'm not mistaken. An environment on Ubuntu 24.04 with OpenSSL 1.1.1 libraries is a bit unusual. If your goal is to ensure that you can build Python with the oldest OpenSSL it claims to support, what you're doing makes sense. But if you have libssl-dev already installed and your Python build complains "Python requires a OpenSSL 1.1.1 or newer", then something weird is going on, and it's probably worth tracking it down. The best solution *should* be to install the current libssl-dev package from the package manager, not to build an old version of OpenSSL from source. I've built Python-3.12.9 from source on Ubuntu-22.04 with no problems (I have libssl-dev installed). To be clear, what is the output of "dpkg -l libssl-dev" on your Ubuntu 24.04 system? If you get something similar to this: ``` $ dpkg -l libssl-dev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-================-==============-============-================================================ ii libssl-dev:amd64 3.3.1-2ubuntu2 amd64 Secure Sockets Layer toolkit - development files ``` then I don't understand why you'd get the "Python requires a OpenSSL 1.1.1 or newer" message. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u(a)gmail.com void Void(void) { Void(); } /* The recursive call of the void */

1 0

RE Version of OpenSSl ?
by vincent.vandevyvre＠oqapy.eu Feb. 9, 2025

Feb. 9, 2025

> > In case this helps you find the correct package to install: > > $ python3 -c "if True: > > import ssl > > print('Ok.') > > " > Ok. > > $ cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=24.04 > DISTRIB_CODENAME=noble > DISTRIB_DESCRIPTION="Ubuntu 24.04.1 LTS" > > $ apt list --installed | grep ssl > > WARNING: apt does not have a stable CLI interface. Use with caution in > scripts. > > libssl-dev/noble-updates,noble-security,now 3.0.13-0ubuntu3.4 amd64 > [installed] > libssl3t64/noble-updates,noble-security,now 3.0.13-0ubuntu3.4 amd64 > [installed,automatic] > libxmlsec1t64-openssl/noble,now 1.2.39-5build2 amd64 [installed,automatic] > openssl/noble-updates,noble-security,now 3.0.13-0ubuntu3.4 amd64 > [installed,automatic] > ssl-cert/noble,noble,now 1.1.2ubuntu1 all [installed,automatic] Thanks Jason, I have near the same result of you. I need to explain the context. I'm on a new machine with a fresh install of Ubuntu 24.04 wich embed Python 3.12.3, no problem with that. As I'm maintainer of some Python modules published on PyPI, I've the habit of testing my modules in different virtual environments. For now Python 3.11, 3.12 and 3.13. So, I've maybe found a solution: I've create in my home a dir named /opt, download into it the latest version of openssl-1.1.1 and uncompress it.(*) ------------------------------------------------------------- $ cd opt/openssl-1.1.1w $ ./config && make && make test $ mkdir $HOME/opt/lib $ mv $HOME/opt/openssl-1.1.1w/libcrypto.so.1.1 $HOME/opt/lib/ $ mv $HOME/opt/openssl-1.1.1w/libssl.so.1.1 $HOME/opt/lib/ $ export LD_LIBRARY_PATH=$HOME/opt/lib:$LD_LIBRARY_PATH -------------------------------------------------------------- And rerun the compilation of 3.12.9 without problem with openssl. (*) https://openssl-library.org/source/old/1.1.1/index.html Vincent.

2 1

RE Version of OpenSSl ?
by vincent.vandevyvre＠oqapy.eu Feb. 9, 2025

Feb. 9, 2025

> HI Vincent. > > You need the sources of the OpenSSL library, not the compiled library. > On Ubuntu, the packages with sources are typically named xxx-dev where > xxx is the package that provides the library. I don't have a Ubuntu > currently, but try looking for something like openssl-dev or > libopenssl-dev etc. Thanks, the dev packege seems named libssl-dev. But: ---------------------------------------------------------------- $ sudo apt install libssl-dev [sudo] Mot de passe de vincent : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait libssl-dev est déjà la version la plus récente (3.0.13-0ubuntu3.4). ---------------------------------------------------------------- In english: "libssl-dev is already the most recent version (3.0.13-0ubuntu3.4). Vincent

1 0

Re: Version of OpenSSl ?
by Keith Thompson Feb. 9, 2025

Feb. 9, 2025

vincent.vandevyvre(a)oqapy.eu writes: > Hi, > > Trying to compile Python-3.12.9 on Ubuntu-24.04 > > The compilation is complete without errors but I have this message: > -------------------------------------------------------------------------------------------------------- > The necessary bits to build these optional modules were not found: > _hashlib _ssl nis > To find the necessary bits, look in configure.ac and config.log. > > Could not build the ssl module! > Python requires a OpenSSL 1.1.1 or newer > -------------------------------------------------------------------------------------------------------- > > But I have a more newer version: > > ------------------------------------------------------------------------------------------------------- > $ openssl version > OpenSSL 3.0.13 30 Jan 2024 (Library: OpenSSL 3.0.13 30 Jan 2024) > ------------------------------------------------------------------------------------------------------- You have the openssl command, but do you have the openssl development libraries? For Ubuntu, you need to install the libssl-dev package. `dpkg -l libssl-dev` will tell you whether you have it. If you don't, `sudo apt-get install libssl-dev` will install it. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u(a)gmail.com void Void(void) { Void(); } /* The recursive call of the void */

1 0

Re: [RELEASE] Python 3.13.2 and 3.12.9 now available!
by Rust Buckett Feb. 6, 2025

Feb. 6, 2025

Thomas Wouters <thomas(a)python.org> writes: > A small release day today! That is to say the releases are relatively > small; the day itself was of average size, as most days are. nice. -- this is my clever sig.

1 0