🌐 Mailman 3 July 2025 - Python-announce-list - python.org

python-oracledb 3.3.0
by Anthony Tuininga July 29, 2025

July 29, 2025

What is python-oracledb? python-oracledb is a Python extension module that enables access to Oracle Database for Python and conforms to the Python database API 2.0 specifications with a number of enhancements. This module replaces cx_Oracle. Where do I get it? https://pypi.org/project/oracledb/3.3.0/ The easiest method to install/upgrade python-oracledb is via pip as in python -m pip install oracledb --upgrade What's new? This release has the following highlights: - support for sessionless transactions with Oracle Database 23ai - support for ingestion of dataframes - support for the ArrowArrayStream PyCapsule interface - pre-built binaries for Python 3.14 (this version is in the release candidate phase currently) See the full release notes for all of the details: https://python-oracledb.readthedocs.io/en/latest/release_notes.html#oracled… Please provide any feedback via GitHub issues: https://github.com/oracle/ python-oracledb/issues or discussions: https://github.com/oracle/python- oracledb/discussions

1 0

Python by the Sea, Bexhill-on-Sea, 23-25 September, 2025
by Steve Holden July 29, 2025

July 29, 2025

Hi there, This is just a quick note to let people know about Python by the Sea, a small (20-40 people) unconference focused more on face-to-face meetings than planned presentations. This is the first event I've organised in over a decade, and seems much more in the spirit of the times than larger gatherings. With luck it should also be less demanding to manage. You can find out more about the conference at https://python-by-the-sea.org, and early bird tickets are now available at https://pybysea.eventbrite.com. I hope to see friends old and new there. Please pass the message on! -- Kind regards Steve Python by the Sea, a friendly little unconference: https://python-by-the-sea.org Author, Python in a Nutshell: https://www.oreilly.com/library/view/python-in-a/9781098113544/

1 0

NumPy 2.3.2 released
by Charles R Harris July 24, 2025

July 24, 2025

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.3.2. The NumPy 2.3.2 release is a patch release with a number of bug fixes and maintenance updates. The highlights are: - Wheels for Python 3.14.0rc1 - PyPy updated to the latest stable release - OpenBLAS updated to 0.3.30 This release supports Python 3.11-3.14. Wheels can be downloaded from PyPI <https://pypi.org/project/numpy/2.3.2>; source archives, release notes, and wheel hashes are available on Github <https://github.com/numpy/numpy/releases/tag/v2.3.2>. *Contributors* A total of 9 people contributed to this release. People with a "+" by their names contributed a patch for the first time. - !DWesl - Charles Harris - Joren Hammudoglu - Maanas Arora - Marco Edward Gorelli - Matti Picus - Nathan Goldbaum - Sebastian Berg - kostayScr + *Pull requests merged* A total of 16 pull requests were merged for this release. - #29256: MAINT: Prepare 2.3.x for further development - #29283: TYP: Work around a mypy issue with bool arrays (#29248) - #29284: BUG: fix fencepost error in StringDType internals - #29287: BUG: handle case in mapiter where descriptors might get replaced... - #29350: BUG: Fix shape error path in array-interface - #29412: BUG: Allow reading non-npy files in npz and add test - #29413: TST: Avoid uninitialized values in test (#29341) - #29414: BUG: Fix reference leakage for output arrays in reduction functions - #29415: BUG: fix casting issue in center, ljust, rjust, and zfill (#29369) - #29416: TYP: Fix overloads in ``np.char.array`` and ``np.char.asarray``... - #29417: BUG: Any dtype should call ``square`` on ``arr \*\* 2`` (#29392) - #29424: MAINT: use a stable pypy release in CI - #29425: MAINT: Support python 314rc1 - #29429: MAINT: Update highway to match main. - #29430: BLD: use github to build macos-arm64 wheels with OpenBLAS and... - #29437: BUG: fix datetime/timedelta hash memory leak (#29411) Cheers, Charles Harris

1 0

Python 3.14 release candidate 1 is go!
by Hugo van Kemenade July 22, 2025

July 22, 2025

It’s the first 3.14 release candidate! https://www.python.org/downloads/release/python-3140rc1/ This release, 3.14.0rc1, is the penultimate release preview. Entering the release candidate phase, only reviewed code changes which are clear bug fixes are allowed between this release candidate and the final release. The second candidate (and the last planned release preview) is scheduled for Tuesday, 2025-08-26, while the official release of 3.14.0 is scheduled for Tuesday, 2025-10-07. There will be no ABI changes from this point forward in the 3.14 series, and the goal is that there will be as few code changes as possible. Call to action We strongly encourage maintainers of third-party Python projects to prepare their projects for 3.14 during this phase, and where necessary publish Python 3.14 wheels on PyPI to be ready for the final release of 3.14.0, and to help other projects do their own testing. Any binary wheels built against Python 3.14.0rc1 will work with future versions of Python 3.14. As always, report any issues to the Python bug tracker. Please keep in mind that this is a preview release and while it’s as close to the final release as we can get it, its use is not recommended for production environments. Core developers: time to work on documentation now - Are all your changes properly documented? - Are they mentioned in What’s New? - Did you notice other changes you know of to have insufficient documentation? Major new features of the 3.14 series, compared to 3.13 Some of the major new features and changes in Python 3.14 are: New features - PEP 779: Free-threaded Python is officially supported - PEP 649: The evaluation of type annotations is now deferred, improving the semantics of using annotations. - PEP 750: Template string literals (t-strings) for custom string processing, using the familiar syntax of f-strings. - PEP 734: Multiple interpreters in the stdlib. - PEP 784: A new module compression.zstd providing support for the Zstandard compression algorithm. - PEP 758: except and except* expressions may now omit the brackets. - Syntax highlighting in PyREPL, and support for color in unittest, argparse, json and calendar CLIs. - PEP 768: A zero-overhead external debugger interface for CPython. - UUID versions 6-8 are now supported by the uuid module, and generation of versions 3-5 are up to 40% faster. - PEP 765: Disallow return/break/continue that exit a finally block. - PEP 741: An improved C API for configuring Python. - A new type of interpreter. For certain newer compilers, this interpreter provides significantly better performance. Opt-in for now, requires building from source. - Improved error messages. - Builtin implementation of HMAC with formally verified code from the HACL* project. - A new command-line interface to inspect running Python processes using asynchronous tasks. - The pdb module now supports remote attaching to a running Python process. (Hey, fellow core developer, if a feature you find important is missing from this list, let Hugo know.) For more details on the changes to Python 3.14, see What’s new in Python 3.14. The next pre-release of Python 3.14 will be the final release candidate, 3.14.0rc2, scheduled for 2025-08-26. https://docs.python.org/3.14/whatsnew/3.14.html Build changes - PEP 761: Python 3.14 and onwards no longer provides PGP signatures for release artifacts. Instead, Sigstore is recommended for verifiers. - Official macOS and Windows release binaries include an experimental JIT compiler. Incompatible changes, removals and new deprecations - Incompatible changes - Python removals and deprecations - C API removals and deprecations - Overview of all pending deprecations Python install manager The installer we offer for Windows is being replaced by our new install manager, which can be installed from the Windows Store or from its download page. See our documentation for more information. The JSON file available for download below contains the list of all the installable packages available as part of this release, including file URLs and hashes, but is not required to install the latest release. The traditional installer will remain available throughout the 3.14 and 3.15 releases. 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 Today, 22nd July, is Pi Approximation Day, because 22/7 is a common approximation of π and closer to π than 3.14. 22/7 is a Diophantine approximation, named after Diophantus of Alexandria (3rd century CE), which is a way of estimating a real number as a ratio of two integers. 22/7 has been known since antiquity; Archimedes (3rd century BCE) wrote the first known proof that 22/7 overestimates π by comparing 96-sided polygons to the circle it circumscribes. Another approximation is 355/113. In Chinese mathematics, 22/7 and 355/113 are respectively known as Yuelü (约率; yuēlǜ; “approximate ratio”) and Milü (密率; mìlǜ; “close ratio”). Happy Pi Approximation Day! 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 Helsinki heatwave after an excellent EuroPython, Your release team, Hugo van Kemenade Ned Deily Steve Dower Łukasz Langa

1 0

ANN: Python-Blosc2 3.6.1 is out!
by Francesc Alted July 18, 2025

July 18, 2025

Announcing Python-Blosc2 3.6.1 ============================== In this release: ✅ Blosc2 now suppports fancy indexing (and orthogonal indexing) ✅ Added fast path for 1D fancy indexing ✅ More complex slicing is now supported for lazy expressions ✅ Blosc2 indexing more consistent with NumPy ✅ Comprehensive ``squeeze`` function which squeezes only specified dimensions ✅ Correctly point to most recent C-blosc2 version 2.19.1 We have blogged about the new fancy indexing support: https://www.blosc.org/posts/blosc2-fancy-indexing/ You can think of Python-Blosc2 3.x as an extension of NumPy/numexpr that: - Can deal with ndarrays compressed using first-class codecs & filters. - Performs many kind of math expressions, including reductions, indexing... - Supports NumPy ufunc mechanism: mix and match NumPy and Blosc2 computations. - Integrates with Numba and Cython via UDFs (User Defined Functions). - Adheres to modern NumPy casting rules way better than numexpr. - Performs linear algebra operations (like ``blosc2.matmul()``). Install it with:: pip install blosc2 --update # if you prefer wheels conda install -c conda-forge python-blosc2 mkl # if you prefer conda and MKL For more info, you can have a look at the release notes in: https://github.com/Blosc/python-blosc2/releases Code example:: from time import time import blosc2 import numpy as np # Create some data operands N = 20_000 a = blosc2.linspace(0, 1, N * N, dtype="float32", shape=(N, N)) b = blosc2.linspace(1, 2, N * N, shape=(N, N)) c = blosc2.linspace(-10, 10, N) # broadcasting is supported # Expression t0 = time() expr = ((a**3 + blosc2.sin(c * 2)) < b) & (c > 0) print(f"Time to create expression: {time()-t0:.5f}") # Evaluate while reducing (yep, reductions are in) along axis 1 t0 = time() out = blosc2.sum(expr, axis=1) t1 = time() - t0 print(f"Time to compute with Blosc2: {t1:.5f}") # Evaluate using NumPy na, nb, nc = a[:], b[:], c[:] t0 = time() nout = np.sum(((na**3 + np.sin(nc * 2)) < nb) & (nc > 0), axis=1) t2 = time() - t0 print(f"Time to compute with NumPy: {t2:.5f}") print(f"Speedup: {t2/t1:.2f}x") assert np.all(out == nout) print("All results are equal!") This will output something like (using an Intel i9-13900K CPU here):: Time to create expression: 0.00033 Time to compute with Blosc2: 0.46387 Time to compute with NumPy: 2.57469 Speedup: 5.55x All results are equal! See a more in-depth example, explaining why Python-Blosc2 is so fast, at: https://www.blosc.org/python-blosc2/getting_started/overview.html#operating… Sources repository ------------------ The sources and documentation are managed through github services at: https://github.com/Blosc/python-blosc2 Python-Blosc2 is distributed using the BSD license, see https://github.com/Blosc/python-blosc2/blob/main/LICENSE.txt for details. Mastodon feed ------------- Follow https://fosstodon.org/@Blosc2 to get informed about the latest developments. Enjoy! - Blosc Development Team Compress Better, Compute Bigger

1 0

Announcement: distlib 0.4.0 released on PyPI
by Vinay Sajip July 17, 2025

July 17, 2025

Version 0.4.0 of distlib has recently been released on PyPI [1]. For newcomers, distlib is a library of packaging functionality which is intended to be usable as the basis for third-party packaging tools. The main changes in this release are as follows: * Add the ``interpret_parsed`` function to ``markers``. * Fix #238: Add build tag to wheel metadata if specified. * Fix #243: Update to support free-threading version of Python (3.13t). * Fix #246: Support subdirectories in the dist-info directory. Thanks to Pieter P for the patch. * Fix #248: Fix path normalization issue caused by the fix for #246. * Move import in script wrapper to ``if __name__ == 'main'`` clause. * Fix #245: Skip test_package_data if a ``SKIP_EXT_PACKAGE_DATA`` environment variable is present. A more detailed change log is available at [2]. Please try it out, and if you find any problems or have any suggestions for improvements, please give some feedback using the issue tracker at [3]. Regards, Vinay Sajip [1] https://pypi.org/project/distlib/0.4.0/ [2] https://distlib.readthedocs.io/en/latest/overview.html#change-log-for-distl… [3] https://github.com/pypa/distlib/issues/new/choose

1 0

pysonar 1.1.0.2035 for SonarQube
by Jean Jimbo July 14, 2025

July 14, 2025

Hello Python developers, We've made some quality of life updates to the pysonar scanner https://pypi.org/project/pysonar/ and documentation, including an in-product set-up guide. We also welcome your contributions to the project (see https://github.com/SonarSource/sonar-scanner-python). Official documentation: https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/… Latest analyzer updates: https://community.sonarsource.com/t/write-quality-comprehensions-coroutines… pysonar requirements: SonarQube Sever 10.6 or higher or SonarQube Cloud Python 3.9 or higher Happy scanning! -Team Sonar

1 0

Roundup 2.5.0 release announcement (including security fix)
by John P. Rouillard July 13, 2025

July 13, 2025

Hello all: I'm proud to release version 2.5.0 of the Roundup issue tracker. This release is a bugfix and feature release, so make sure to read https://www.roundup-tracker.org/docs/upgrading.html to bring your tracker up to date. The 42 changes, as usual, include some new features and many bug fixes. One bug fix is an XSS security issue with CVE-2025-53865 primarily with the responsve and devel templates. See: https://www.roundup-tracker.org/docs/upgrading.html#xss-security-issue-with… Version 2.5.0 does not support Python 2. The minimum Python version is 3.7. Among the significant enhancements in version 2.5.0 compared to the 2.4.0 release are: * **XSS vulnerability with devel and responsive templates fixed** Just before release an XSS security issue with trackers based on the devel or responsive templates was discovered. The updating directions include instructions on fixing this issue with the html templates. * **The property/field advanced search expression feature has been enhanced and documented.** Search expressions are usually built using the expression editor on the search page. They can be built manually by modifying the search URL but the RPN search expression format was undocumented. Errors in expressions could return results that didn't match the user's intent. This release documents the RPN expression syntax, adds basic expression error detection, and improves error reporting. * **The default hash method for password storage is more secure.** We use PBKDF2 with SHA512 (was SHA1). With this change you can lower the value of password_pbkdf2_default_rounds in your tracker's config.ini. Check the upgrading documentation for more info. (Note this may cause longer authentication times, the upgrade doc describes how to downgrade the hash method if required.) * **Roundup's session token is now prefixed with the magic ``__Secure__`` tag when using HTTPS.** This adds another layer of protection in addition to the existing ``Secure`` property that comes with the session cookie. * **Data authorization can be done at the database level speeding up display of index pages.** Roundup verifies the user's authorization for the data fetched from the database after retrieving data from the database. A new optional ``filter`` argument has been added to Permission objects. When the administrator supplies a filter function, it can boost performance with SQL server databases by pushing selection criteria to the database. By offloading some permission checks to the database, less data is retrieved from the database. This leads to quicker display of index pages with reduced CPU and network traffic. * **The REST endpoint can supply binary data (images, pdf, ...) to its clients.** Requesting binary data from a REST endpoint has been a hassle. Since JSON can't handle binary data, images (and other binary data) need to be encoded. This makes them significantly larger. The workaround was to use a non-REST endpoint for fetching non-text attachments. This update lets the REST endpoint return raw message or file content data. You can utilize the ``binary_content`` endpoint along with an appropriate ``Accept`` header (e.g. ``image/jpeg``) in your request. * **Extract translatable strings from your tracker easily.** The ``roundup-gettext`` tool has been enhanced to extract translatable strings from detectors and extensions. This will simplify the process of translating your trackers. Other miscellaneous fixes include: * Fix a crash bug on Windows with Python 3.13. * Update documentation on required REST headers, along with other documentation updates. * Improve handling of an error condition generated when an invalid REST response format is requested. For example if XML output is requested, but dicttoxml is not installed, we now return an error without doing any work. * Fix an incorrect error report when a PUT REST request sets the user's email address to its current value. * Add support for the ``defusedxml`` Python module to enhance security when using XML. * Introduce the templating function: ``utils.set_http_response(integer)`` to set the HTTP return code directly from your template. This allows the template logic to return a 404 or other code when the user invokes a template incorrectly. * Add a new ``registerUtilMethod('name', my_function)``. which makes it easier to define and use complex templating utilities. It passes a default argument that allows access to the client instance, translation functions, and other templating utility functions. Previously you had to pass the arguments explicitly when calling the utility from the template. * Add the ability to generate native HTML date and number/integer inputs. Check the upgrading document for caveats. This feature is disabled by default. * Re-enable support for GPG/PGP signed emails, which requires installation from the test PyPi repository. The file CHANGES.txt has a detailed list of feature additions and bug fixes for each release. The most recent changes from there are at the end of this announcement. Also see the information in doc/upgrading.txt. If you find bugs, please report them to issues AT roundup-tracker.org or create an account at https://issues.roundup-tracker.org and open a new ticket. If you have patches to fix the issues they can be attached to the email or uploaded to the tracker. Upgrading ========= If you're upgrading from an older version of Roundup you *must* follow all the "Software Upgrade" guidelines given in the doc/upgrading.txt documentation. Note that you should run ``roundup-admin ... migrate`` for all your trackers to update the database schema version. Do this before you use the web, command-line or mail interface and before any users access the tracker. Roundup requires Python 3 newer than or equal to version 3.7 for correct operation. (Python 3.4 or 3.5, or 3.6 may work, but are not tested.) Note that Roundup 2.4.0 was the last release to support Python 2. You should deploy new trackers with Python 3 and plan on upgrading older trackers from Python 2 to Python 3. See the upgrade guide. You can install it with:: pip install roundup (preferably in a virtual environment). To download it, use:: pip download roundup then unpack and test/install from the tarball. To give Roundup a try, just download (directions above), unpack and run:: python demo.py then open the url printed by the demo app. Release info and download page: https://pypi.org/project/roundup/ Source and documentation is available at the website: https://www.roundup-tracker.org/ Mailing lists - the place to ask questions: https://sourceforge.net/p/roundup/mailman/ About Roundup ============= Roundup is a simple-to-use and install issue-tracking system with command-line, web and e-mail interfaces. It is based on the winning design from Ka-Ping Yee in the Software Carpentry "Track" design competition. Roundup manages a number of issues (with flexible properties such as "description", "priority", and so on) and provides the ability to: (a) submit new issues, (b) find and edit existing issues, and (c) discuss issues with other participants. The system facilitates communication among the participants by managing discussions and notifying interested parties when issues are edited. One of the major design goals for Roundup that it be simple to get going. Roundup is therefore usable "out of the box" with any Python 3.7+ installation. It doesn't even need to be "installed" to be operational, though an install script is provided. It comes with five basic issue tracker templates * a classic bug/feature tracker * a more extensive devel tracker for bug/features etc. * a responsive version of the devel tracker * a jinja2 version of the devel template (work in progress) * a minimal skeleton and supports four database back-ends (anydbm, sqlite, mysql and postgresql). Recent Changes ============== From 2.4.0 to 2.5.0 Fixed: - issue2551343 - Remove support for PySQLite. It is unmaintained and sqlite3 is used which is the default for a Python distribution. (John Rouillard) - replace use of os.listdir with os.scandir. Performance improvement. Using with Python 2 requires 'pip install scandir'. (John Rouillard) - issue2551131 - Return accept-patch if patch body not accepted (415 code). Accept-Patch returned with acceptable values. (John Rouillard) - issue2551074 - In "responsive" template: click on hide comment leads to a red error msg. (Report by Ludwig Reiter; fix John Rouillard) - issue2550698 - added documentation on filtering using RPN property expressions. (John Rouillard) - issue2551372 - Better document necessary headers for REST and fix logging to log missing Origin header (Ralf Schlatterbeck with suggestions on documentation by John Rouillard) - issue2551289 - Invalid REST Accept header with post/put performs change before returning 406. Error before making any changes to the db if we can't respond with requested format. (John Rouillard) - issue2551356 - Add etag header when If-Modified-Since GET request returns not-modified (304). Breaking change to function signature for client.py-Client::_serve_file(). (John Rouillard) - issue2551381 - roundup-server parses URI's with multiple '?" incorrectly. (John Rouillard) - issue2551382 - invalid @verbose, @page_* values in rest uri's generate 409 not 400 error. (John Rouillard) - fix issues with rest doc and use of PUT on a property item. Response is similar to use of PUT on the item, not a GET on the item. Discovered while fuzz testing. (John Rouillard) - issue2551383 - Setting same address via REST PUT command results in an error. Now the userauditor does not trigger an error if a user sets the primary address to the existing value. (John Rouillard) - issue2551253 - Modify password PBKDF2 method to use SHA512. The default password hashing algorithm has been upgraded to PBKDF2-SHA512 from PBKDF2-SHA1. The default pbkdf2 rounds in the config file has been changed to 250000. The admin should change it manually if it is at 2 million. PBKDF2-SHA512 (PBKDF2S5) has been available since release 2.3, but it required a manual step to make it the default. (John Rouillard) - fixed a crash with roundup-admin perftest password when rounds not set on command line. (John Rouillard) - issue2551374 - Add error handling for filter expressions. Filter expression errors are now reported. (John Rouillard) - issue2551384: Modify flow in client.py's REST handler to verify authorization earlier. The validation order for REST requests has been changed. Checking user authorization to use the REST interface is done before validating the Origin header. As a result, incorrectly formatted CORS preflight requests (e.g. missing Origin header) can now return HTTP status 403 as well as status 400. (John Rouillard) - issue2551387 - TypeError: not indexable. Fix crash due to uninitialized list element on a (Mini)FieldStorage when unexpected input is posted via wsgi. (Reported and debugged by Christof Meerwald; fix John Rouillard) - close http socket and send a 408 status when a timeout exception is handed in roundup-server. This prevents another exception caused by using a timed out socket. (John Rouillard) - issue2551391, partial fix for issue1513369. input fields were not getting id's assigned. Fixed automatic id assignment to input fields. Thinko in the code. (John Rouillard) - issue1895197 - translated help texts in admin.py not displayed correctly. (Initial patch tobias-herp, John Rouillard) - issue2551238 - roundup-server should exit with error if -d <pidfile> is used without -l <logfile>. Added code to report the issue. Added issue with relative paths for log file whn using -L and -d with roundup-server. (John Rouillard) - Allow the specification of a "form" parameter for Date fields to make the popup calendar work when the enclosing form has a name different from "itemSynopsis". (Ralf Schlatterbeck) - issue2551376: Fix tracebacks in item templates (Ralf Schlatterbeck) - issue2551396: Use of os.path.stat.ST_MTIME in python 3.13 crashes roundup on windows. Replaced with equivalent stat.ST_MTIME. (Randy on IRC, fix: John Rouillard and R. David Murray (bitdancer)) - issue2551323: remove functions used for XHTML template support. XHTML was deprecated in Roundup 2.3.0 and an invalid value in 2.4.0. (John Rouillard) - issue2551406: 'Templating Error: too many values to unpack' crash fixed. (reported by and patch Christof Meerwald, commit/test John Rouillard) - fix potential HTTP Response Splitting issue in roundup-server. Discovered by CodeQL in CI. (John Rouillard) Features: - issue2551287 - Enhance roundup_gettext.py to extract strings from detectors/extensions. If the polib module is available, roundup-gettext will extract translatable strings from the tracker's Python code. If polib is missing, it will print a warning. (Patch Marcus Priesch, cleanup to remove python 2 issues, John Rouillard.) - issue2551315 - Document use of RestfulInstance.max_response_row_size to limit data returned from rest request. (John Rouillard) - issue2551330 - Add an optional 'filter' function to the Permission objects and the addPermission method. This is used to optimize search performance by not checking items returned from a database query one-by-one (using the check function) but instead offload the permission checks to the database. For SQL backends this performs the filtering in the database. (Ralf Schlatterbeck) - issue2551370 - mark roundup session cookie with __Secure- prefix. (John Rouillard) - add -P flag to roundup-server to log client address from X-Forwarded-For reverse proxy header rather than connecting address. This logs the actual client address when roundup-server is run behind a reverse proxy. It also appends a + sign to the logged address/name. (John Rouillard) - issue2551068 - Provide way to retrieve file/msg data via rest endpoint. Raw file/msg data can be retrieved using the /binary_content attribute and an Accept header to select the mime type for the data (e.g. image/png for a png file). The existing html interface method still works and is supported, but is legacy. (John Rouillard) - added fuzz testing for some code. Found issue2551382 and others. (John Rouillard) - issue2551116 - Replace xmlrpclib (xmlrpc.client) with defusedxml. Added support for defusedxml to better secure the xmlrpc endpoint. (John Rouillard) - Added new instance.registerUtilMethod() method to make using complex templating easier as it provides a default Client instance to the templating method. (John Rouillard) - Added new templating utils.set_http_response(integer) method to allow reporting an error to the user from a template. (John Rouillard) - issue2551390 - Replace text input/calendar popup with native date input. Also add double-click and exit keyboard handlers to allow copy/paste/editing the text version of the date. Configurable via the use_browser_date_input setting in the [web] section of config.ini. By default browser native dates are turned off. (John Rouillard, Ralf Schlatterbeck) - Use native number type input for Number() and Integer() properties. Integer() uses step=1 as well. Configurable via the use_browser_number_input setting in the [web] section of config.ini. Set off by default. See https://issues.roundup-tracker.org/issue2551398 for discussion of issues with native number inputs. (John Rouillard, Ralf Schlatterbeck) - issue2551231 - template.py-HTMLClass::classhelp doesn't merge user defined classes. It now merges them in. (John Rouillard) - re-enable support for GPG/PGP encrypted emails using new python gpg package on the test pypi instance. (Paul Schwabauer) -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions.

1 0

Python 3.14.0 beta 4 is here!
by Hugo van Kemenade July 8, 2025

July 8, 2025

It’s the final 3.14 beta! https://www.python.org/downloads/release/python-3140b4/ This is a beta preview of Python 3.14 Python 3.14 is still in development. This release, 3.14.0b4, is the last of four planned beta releases. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We strongly encourage maintainers of third-party Python projects to test with 3.14 during the beta phase and report issues found to the Python bug tracker as soon as possible. While the release is planned to be feature-complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (Tuesday 2025-07-22). Our goal is to have no ABI changes after beta 4 and as few code changes as possible after the first release candidate. To achieve that, it will be extremely important to get as much exposure for 3.14 as possible during the beta phase. This includes creating pre-release wheels for 3.14, as it helps other projects to do their own testing. However, we recommend that your regular production releases wait until 3.14.0rc1, to avoid the risk of ABI breaks. Please keep in mind that this is a preview release and its use is not recommended for production environments. Major new features of the 3.14 series, compared to 3.13 Some of the major new features and changes in Python 3.14 are: New features - PEP 779: Free-threaded Python is officially supported - PEP 649: The evaluation of type annotations is now deferred, improving the semantics of using annotations. - PEP 750: Template string literals (t-strings) for custom string processing, using the familiar syntax of f-strings. - PEP 734: Multiple interpreters in the stdlib. - PEP 784: A new module compression.zstd providing support for the Zstandard compression algorithm. - PEP 758: except and except* expressions may now omit the brackets. - Syntax highlighting in PyREPL, and support for color in unittest, argparse, json and calendar CLIs. - PEP 768: A zero-overhead external debugger interface for CPython. - UUID versions 6-8 are now supported by the uuid module, and generation of versions 3-5 and 8 are up to 40% faster. - PEP 765: Disallow return/break/continue that exit a finally block. - PEP 741: An improved C API for configuring Python. - A new type of interpreter. For certain newer compilers, this interpreter provides significantly better performance. Opt-in for now, requires building from source. - Improved error messages. - Builtin implementation of HMAC with formally verified code from the HACL* project. - A new command-line interface to inspect running Python processes using asynchronous tasks. - The pdb module now supports remote attaching to a running Python process. (Hey, fellow core developer, if a feature you find important is missing from this list, let Hugo know.) For more details on the changes to Python 3.14, see What’s new in Python 3.14. The next pre-release of Python 3.14 will be the first release candidate, 3.14.0rc1, scheduled for 2025-07-22. https://docs.python.org/3.14/whatsnew/3.14.html Build changes - PEP 761: Python 3.14 and onwards no longer provides PGP signatures for release artifacts. Instead, Sigstore is recommended for verifiers. - Official macOS and Windows release binaries include an experimental JIT compiler. Incompatible changes, removals and new deprecations - Incompatible changes - Python removals and deprecations - C API removals and deprecations - Overview of all pending deprecations Python install manager The installer we offer for Windows is being replaced by our new install manager, which can be installed from the Windows Store or from its download page. See our documentation for more information. The JSON file available for download below contains the list of all the installable packages available as part of this release, including file URLs and hashes, but is not required to install the latest release. The traditional installer will remain available throughout the 3.14 and 3.15 releases. More resources - Online documentation](https://docs.python.org/3.14/) - PEP 745](https://peps.python.org/pep-0745/), 3.14 Release Schedule - 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 All this talk of π and yet some say π is wrong. Tau Day (June 28th, 6/28 in the US) celebrates τ as the “true circle constant”, as the ratio of a circle’s circumference to its radius, C/r = 6.283185… The Tau Manifesto declares π “a confusing and unnatural choice for the circle constant”, in part because “2π occurs with astonishing frequency throughout mathematics”. If you wish to embrace τ the good news is PEP 628 added math.tau to Python 3.6 in 2016: When working with radians, it is trivial to convert any given fraction of a circle to a value in radians in terms of tau. A quarter circle is tau/4, a half circle is tau/2, seven 25ths is 7*tau/25, etc. In contrast with the equivalent expressions in terms of pi (pi/2, pi, 14*pi/25), the unnecessary and needlessly confusing multiplication by two is gone. 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 cloudy Helsinki, looking forward to Prague and EuroPython next week, Your release team, Hugo van Kemenade Ned Deily Steve Dower Łukasz Langa

1 0

pyfiq: Pythonic FIFO microqueue
by Robert W July 5, 2025

July 5, 2025

Hey I recently started working on a new project and thought I’d share it. It’s a bit niche and in its early stages of development, but I’d be curious to hear what other Python devs think about this idea. pyfiq is a lightweight, MIT-licensed, Redis-backed FIFO task queue for Python. It lets you decorate (I/O-bound) functions with @pyfiq.fifo(...), enqueue them for execution, and ensures those functions run in strict order, even across multiple application instances. You can think of pyfiq as an embedded, Python-native alternative to AWS Lambda + SQS FIFO: no external infrastructure, no vendor lock-in--just drop it into your app. Check it out: https://github.com/rbw/pyfiq -- Robert Wikman 0xf6feb506ae5d3762

1 0