Mailman 3 July 2022 - Python-announce-list

structlog 22.1.0
by Hynek Schlawack July 20, 2022

July 20, 2022

I’m happy to announce a new release of structlog! With more than 4 million downloads per month, structlog is the most popular solution for structured logging in Python. It doesn’t just allow you to log key-value pairs in a structured manner, it also makes it EASIER and FASTER. Check out <https://www.structlog.org/en/stable/why.html> if you’re intrigued but not convinced! My heartfelt thanks go to: - My generous GitHub sponsors <https://github.com/sponsors/hynek>, - companies subscribing to structlog on Tidelift <https://tidelift.com/subscription/pkg/pypi-structlog>, - and people who buy me coffees on <https://ko-fi.com/the_hynek>! That's the support that made me maintain structlog for almost a decade with no end in sight! <3 ------------------------------------------------------------------------ (alternatively, see <https://github.com/hynek/structlog/releases/tag/22.1.0> for a richer-formatted version of the following) Highlights This is a (too) big release, so it has many highlights! Firstly, rendering exceptions in machine-readable logs (usually JSON) got a big upgrade: thanks to structlog.processors.dict_tracebacks you can now have fully structured exceptions in your logs! To ease getting started with structlog, we're now shipping structlog.stdlib.recreate_defaults() that recreates structlog's default behavior, but on top of standard library's logging. The output looks the same, but it runs through logging's machinery and integrates itself easier. The default configuration now also merges your contextvars-based context, so enjoy structlog.contextvars.bind_contextvars() without configuring anything! Another request wish that kept coming up is naming the message key differently than event. We're aware that nowadays keys like msg are more common, but structlog pre-dates the software that introduced and popularized it. To allow for more consistency across your platforms, structlog now ships structlog.processors.EventRenamer that allows you to rename the default event key to something else and additionally also allows you to rename another key to event. Full Changelog Removed - Python 3.6 is not supported anymore. - Pickling is now only possible with protocol version 3 and newer. Deprecated - The entire structlog.threadlocal module is deprecated. Please use the primitives from structlog.contextvars instead. If you're using the modern APIs (bind_threadlocal() / merge_threadlocal()) it's enough to replace them 1:1 with their contextvars counterparts. The old approach around wrap_dict() has been discouraged for a while. Currently there are no concrete plans to remove the module, but no patches against it will be accepted from now on. #409 Added - structlog.processors.StackInfoRenderer now has an additional_ignores parameter that allows you to filter out your own logging layer. #396 - Added structlog.WriteLogger, a faster – but more low-level – alternative to structlog.PrintLogger. It works the way PrintLogger used to work in previous versions. #403 #404 - structlog.make_filtering_bound_logger()-returned loggers now also have a log() method to match the structlog.stdlib.BoundLogger signature closer. #413 - Added structured logging of tracebacks via the structlog.tracebacks module, and most notably the structlog.tracebacks.ExceptionDictTransformer which can be used with the new structlog.processors.ExceptionRenderer to render JSON tracebacks. #407 - structlog.stdlib.recreate_defaults(log_level=logging.NOTSET) that recreates structlog's defaults on top of standard library's logging. It optionally also configures logging to log to standard out at the passed log level. #428 - structlog.processors.EventRenamer allows you to rename the hitherto hard-coded event dict key event to something else. Optionally, you can rename another key to event at the same time, too. So adding EventRenamer(to="msg", replace_by="_event") to your processor pipeline will rename the standard event key to msg and then rename the _event key to event. This allows you to use the event key in your own log files and to have consistent log message keys across languages. - structlog.dev.ConsoleRenderer(event_key="event") now allows to customize the name of the key that is used for the log message. Changed - structlog.make_filtering_bound_logger() now returns a method with the same signature for all log levels, whether they are active or not. This ensures that invalid calls to inactive log levels are caught immediately and don't explode once the log level changes. #401 - structlog.PrintLogger – that is used by default – now uses print() for printing, making it a better citizen for interactive terminal applications. #399 - structlog.testing.capture_logs now works for already initialized bound loggers. #408 - structlog.processors.format_exc_info() is no longer a function, but an instance of structlog.processors.ExceptionRenderer. Its behavior has not changed. #407 - The default configuration now includes the structlog.contextvars.merge_contextvars processor. That means you can use structlog.contextvars features without configuring structlog. Fixed - Overloaded the bind, unbind, try_unbind and new methods in the FilteringBoundLogger Protocol. This makes it easier to use objects of type FilteringBoundLogger in a typed context. #392 - Monkeypatched sys.stdouts are now handled more gracefully by ConsoleRenderer (that's used by default). #404 - structlog.stdlib.render_to_log_kwargs() now correctly handles the presence of exc_info, stack_info, and stackLevel in the event dictionary. They are transformed into proper keyword arguments instead of putting them into the extra dictionary. #424, #427

1 0

python-oracledb 1.0.2
by Anthony Tuininga July 18, 2022

July 18, 2022

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 is intended to eventually replace cx_Oracle. Where do I get it? https://pypi.org/project/oracledb/1.0.2/ The easiest method to install/upgrade python-oracledb is via pip as in python -m pip install oracledb --upgrade What's new? This release addresses a number of reported issues. It also adds Linux ARM 64-bit binaries for the first time. 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

ANN: distlib 0.3.5 released on PyPI
by Vinay Sajip July 14, 2022

July 14, 2022

I've recently released version 0.3.5 of distlib 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: * Fixed #161: Updated test case. * Fixed #164: Improved support for reproducible builds by allowing a fixed date/time to be inserted into created .exe files. Thanks to Somber Night for the patch. * Fixed #169: Removed usage of deprecated imp module in favour of importlib. * Fixed #170: Corrected implementation of ``get_required_dists()``. * Fixed #172: Compute ABI correctly for Python < 3.8. * Changed the default locator configuration. * Made updates in support of PEP 643 / Metadata 2.2. * Updated launcher executables. Thanks to Michael Bikovitsky for his help with the launcher changes. * Updated to write archive path of RECORD to RECORD instead of staging path. Thanks to Pieter Pas for the patch. 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! [3] Regards, Vinay Sajip [1] https://pypi.org/project/distlib/0.3.5/ [2] https://distlib.readthedocs.io/en/0.3.5/ [3] https://github.com/pypa/distlib/issues/new/choose

1 0

[RELEASE] The cursed fourth Python 3.11 beta (3.11.0b4) is available
by Pablo Galindo Salgado July 11, 2022

July 11, 2022

I cannot believe I am writing this, but Python 3.11.b4 is finally available!! [image: :scream:] [image: :tada:] [image: :tada:] [image: :tada:] https://www.python.org/downloads/release/python-3110b4/ ##[image: :warning:][image: :warning:][image: :warning:] PLEASE HELP US TO TEST THIS RELEASE [image: :warning:][image: :warning:][image: :warning:] Due to the modified release schedule and the stability concerns regarding the past beta releases, please, please, please, please, help us to test Python 3.11 by testing this beta releases. * if you maintain a library or a third-party package. Test the beta releases! * If you have code that you maintain at work/research centre/classroom/whatever. Test the beta releases! * If you are a multi-million corporation that uses Python. Test the beta releases! * If you are a single-person company that uses Python. Test the beta releases! * If you have a bunch of Python scripts. Test the beta releases! * If you use Python for work, research, teaching or literally for anything. Test the beta releases! * If you ... In summary: no matter who you are or what you do. Test the beta releases! Is **very** important for us that we identify all possible things that may break your code **before** the final release is done and we can only do this if you help us by testing the beta releases and then report anything that doesn't work! ## Credit where credit is due [image: :pray:] Lots of thanks to Christian Heimes, Brandt Bucher, Irit Katriel, Mark Shannon, Dennis Sweeney, Kumar Aditya and other contributors (sorry if I am missing any names) that worked really hard against time to help me and the release team with the release blockers. They are all awesome and we and the Python community are very lucky to have them in the team [image: :heart:] ## What happens with the next betas? As stated in [my previous communication]( https://mail.python.org/archives/list/python-dev@python.org/thread/3JWVCSBP…) we are in a special situation regarding beta releases. As the requirements to continue with the regular schedule are met, we are going to still target the final release of Monday, 2022-10-03. Python 3.11.0b5 was supposed to be released two days ago, so we are obviously delayed. As we are targeting the regular release schedule, I'm going to try to release 3.11.0b5 on Thursday, 2022-07-25. ## This is a beta preview of Python 3.11 Python 3.11 is still in development. 3.11.0b4 is the fourth of five planned beta release previews. 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.11** during the beta phase and report issues found to [the Python bug tracker](https://github.com/python/cpython/issues) 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 (Monday, 2021-08-02). Our goal is have no ABI changes after beta 5 and as few code changes as possible after 3.11.0rc1, the first release candidate. To achieve that, it will be **extremely important** to get as much exposure for 3.11 as possible during the beta phase. 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.11 series, compared to 3.10 Some of the new major new features and changes in Python 3.11 are: ## General changes * [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include Fine-Grained Error Locations in Tracebacks * [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups and except* * [PEP 680](https://www.python.org/dev/peps/pep-0680/)-- tomllib: Support for Parsing TOML in the Standard Library * [PEP 681](https://www.python.org/dev/peps/pep-0681/)-- Data Class Transforms * [bpo-46752](https://bugs.python.org/issue46752)-- Introduce task groups to asyncio * [bpo-433030](https://github.com/python/cpython/issues/34627/) -- Atomic grouping ((?>...)) and possessive quantifiers (`*+, ++, ?+, {m,n}+`) are now supported in regular expressions. * The [Faster Cpython Project](https://github.com/faster-cpython/) is already yielding some exciting results. Python 3.11 is up to 10-60% faster than Python 3.10. On average, we measured a 1.22x speedup on the standard benchmark suite. See [Faster CPython]( https://docs.python.org/3.11/whatsnew/3.11.html#faster-cpython) for details. ## Typing and typing language changes * [PEP 673](https://www.python.org/dev/peps/pep-0673/) -- Self Type * [PEP 646](https://www.python.org/dev/peps/pep-0646/)-- Variadic Generics * [PEP 675](https://www.python.org/dev/peps/pep-0675/)-- Arbitrary Literal String Type * [PEP 655](https://www.python.org/dev/peps/pep-0655/)-- Marking individual TypedDict items as required or potentially-missing <small>(Hey, **fellow core developer,** if a feature you find important is missing from this list, [let Pablo know](mailto:pablogsal@python.org ).)</small> The next pre-release of Python 3.11 will be 3.11.0b5, currently scheduled for Thursday, 2022-07-25. # More resources * [Online Documentation](https://docs.python.org/3.11/) * [PEP 664](https://www.python.org/dev/peps/pep-0664/), 3.11 Release Schedule * Report bugs at [https://bugs.python.org](https://bugs.python.org). * [Help fund Python and its community](/psf/donations/). # And now for something completely different The Planck temperature is 1.416784×10**32 K. At this temperature, the wavelength of light emitted by thermal radiation reaches the Planck length. There are no known physical models able to describe temperatures greater than the Planck temperature and a quantum theory of gravity would be required to model the extreme energies attained. Hypothetically, a system in thermal equilibrium at the Planck temperature might contain Planck-scale black holes, constantly being formed from thermal radiation and decaying via Hawking evaporation; adding energy to such a system might decrease its temperature by creating larger black holes, whose Hawking temperature is lower. Rumours say the Planck temperature can be reached in some of the hottest parts of Spain in summer. # We hope you enjoy the new releases! 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 organization contributions to the Python Software Foundation. https://www.python.org/psf/ If you have any questions, please reach out to me or another member of the release team :) Your friendly release team, Ned Deily @nad https://discuss.python.org/u/nad Steve Dower @steve.dower https://discuss.python.org/u/steve.dower Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal

1 1

Mongo DRF Endpoint Logger - The log process is now simple.
by İnan DELİBAŞ July 11, 2022

July 11, 2022

Hi all, Use it if you're using Django Rest and need to log your endpoint requests to a database. There is no need for migration, and sensitive data is hidden while logging. You are free to log any specific request status code or method. pip install mongo-drf-endpoint-logger Pypi : https://pypi.org/project/mongo-drf-endpoint-logger/ Github: https://github.com/inanpy/mongo_drf_endpoint_logger Thank you for support.

1 0

Mongo
by İnan DELİBAŞ July 11, 2022

July 11, 2022

Hi all, Use it if you're using Django Rest and need to log your endpoint requests to a database. There is no need for migration, and sensitive data is hidden while logging. You are free to log any specific request status code or method. pip install mongo-drf-endpoint-logger Pypi : https://pypi.org/project/mongo-drf-endpoint-logger/ Github: https://github.com/inanpy/mongo_drf_endpoint_logger Thank you for support.

1 0

ANN: Mongo DRF Endpoint Logger 0.0.2 released!
by İnan DELİBAŞ July 11, 2022

July 11, 2022

Hi all, Use it if you're using Django Rest and need to log your endpoint requests to a database. There is no need for migration, and sensitive data is hidden while logging. You are free to log any specific request status code or method. pip install mongo-drf-endpoint-logger Pypi : https://pypi.org/project/mongo-drf-endpoint-logger/ Github: https://github.com/inanpy/mongo_drf_endpoint_logger Thank you for support.

1 0

竜 TatSu 5.8.1
by Juancarlo Añez July 11, 2022

July 11, 2022

竜 TatSu is a tool that takes grammars in a variation of EBNF as input, and outputs memoizing (Packrat) PEG parsers in Python. This release provides a set of bug fixes, optimizations, and code modernizations. - https://github.com/neogeny/TatSu - https://tatsu.readthedocs.io/en/stable/ -- Juancarlo Añez mailto:apalala@gmail.com

1 0

ANN: poliastro 0.17.0 released 🚀
by Juan Luis Cano Rodríguez July 11, 2022

July 11, 2022

Hi all, It fills us with astronomical joy to announce the release of poliastro 0.17.0! 🚀 poliastro is an open source (MIT) pure Python library for interactive astrodynamics and orbital mechanics, with a focus on ease of use, speed, and quick visualization. It provides a simple and intuitive API, and handles physical quantities with units. It is used in academia and the industry by people from all around the world. You can install poliastro using pip, conda, or mamba: pip install "poliastro==0.17.0" mamba install "poliastro=0.17.0" --channel conda-forge This release brought a number of new features, most notably an Orbit.to_ephem method for retrieving the propagation time history from an osculating orbit, a GabbardPlotter class to plot Gabbard diagrams, a new recursive series Kepler solver for elliptical orbits, and a new Orbit.elevation method. In addition, we have refactored the propagation code and deprecated or deleted several parts of the API, so existing users are encouraged to read the full release notes before upgrading: https://docs.poliastro.space/en/0.17.x/changelog.html#poliastro-0-17-0- 2022-07-10 We will present poliastro at SciPy 2022, the 21st annual Scientific Computing with Python conference, will be held in Austin, TX July 11-17, 2022. If you want to get a sneak peek, don't miss my talk on the Open Source Cubesat Workshop held at the European Space Operations Centre in 2017: https://youtu.be/KnoYzqAw_vM?t=1h36m14s And feel welcome to join our community chat on Matrix: http://chat.poliastro.space Per Python ad astra! --- Juan Luis Cano Rodríguez poliastro lead developer

1 0

NumPy 1.23.1 released
by Charles R Harris July 9, 2022

July 9, 2022

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 1.23.1. NumPy 1.23.1 is a maintenance release that fixes bugs discovered after the 1.23.0 release. Notable fixes are: - Fix searchsorted for float16 NaNs - Fix compilation on Apple M1 - Fix KeyError in crackfortran operator support (Slycot) The Python versions supported for this release are 3.8-3.10. Wheels can be downloaded from PyPI <https://pypi.org/project/numpy/1.23.1>; source archives, release notes, and wheel hashes are available on Github <https://github.com/numpy/numpy/releases/tag/v1.23.1>. *Contributors* A total of 7 people contributed to this release. People with a "+" by their names contributed a patch for the first time. - Charles Harris - Matthias Koeppe + - Pranab Das + - Rohit Goswami - Sebastian Berg - Serge Guelton - Srimukh Sripada + *Pull requests merged* A total of 8 pull requests were merged for this release. - #21866: BUG: Fix discovered MachAr (still used within valgrind) - #21867: BUG: Handle NaNs correctly for float16 during sorting - #21868: BUG: Use ``keepdims`` during normalization in ``np.average`` and... - #21869: DOC: mention changes to ``max_rows`` behaviour in ``np.loadtxt`` - #21870: BUG: Reject non integer array-likes with size 1 in delete - #21949: BLD: Make can_link_svml return False for 32bit builds on x86_64 - #21951: BUG: Reorder extern "C" to only apply to function declarations... - #21952: BUG: Fix KeyError in crackfortran operator support Cheers, Charles Harris

1 0