fast_float: updated to 8.2.1
8.2.1
fix for issue 354
8.2.2
Added template overloads for integer_times_pow10()
Made function non-template
Added corner cases around max value/infinity
Fixes compilation on GCC/MinGW
oss-fuzz: Add unit test build
documenting better which types we support
adding IP address benchmark
faster uint8_t parsing
Fixed UB
sfeed: Update to 2.3
Changes:
2.3
For this release if you use sfeed_mbox: because of some changes the Message-ID
value will be different. This may be important for example if you use this
header for filtering duplicate messages.
See below for detailed information.
Fixes:
* sfeed_update: when merging a record: change the default to use the last record
In many cases it makes sense to use the last record (merged by default based
on the combination id, title, link).
Thanks Ivo Cicchese for the feedback!
* sfeed_mbox:
* The To header could contain characters that are invalid.
* The Message-ID field could contain spaces or invalid characters. Now it is
"@newsfeed.local".
[35 lines not shown]
py-coverage: updated to 7.13.1
Version 7.13.1 — 2025-12-28
- Added: the JSON report now includes a ``"start_line"`` key for function and
class regions, indicating the first line of the region in the source. Closes
`issue 2110`_.
- Added: The ``debug data`` command now takes file names as arguments on the
command line, so you can inspect specific data files without needing to set
the ``COVERAGE_FILE`` environment variable.
- Fix: the JSON report used to report module docstrings as executed lines,
which no other report did, as described in `issue 2105`_. This is now fixed,
thanks to Jianrong Zhao.
- Fix: coverage.py uses a more disciplined approach to detecting where
third-party code is installed, and avoids measuring it. This shouldn't change
any behavior. If you find that it does, please get in touch.
[12 lines not shown]
py-tldextract: updated to 5.3.1
5.3.1 (2025-12-28)
* Bugfixes
* Drop support for EOL Python 3.9
* Support Python 3.14 + PyPy 3.11
* Speed up IP address search space with `isdecimal()` instead of `isdigit()`
* Docs
* Reorganize, dedupe, and shorten README
pkg-vulnerabilities: spell gnupg2 correctly
Add the missing trailing "2".
Please also note that at the moment only CVE-2025-68973 is fixed on 2.5.x
release.
py-psutil: update to 7.2.1.
7.2.1
=====
2025-12-29
**Bug fixes**
- 2699_, [FreeBSD], [NetBSD]: `heap_info()`_ does not detect small allocations
(<= 1K). In order to fix that, we now flush internal jemalloc cache before
fetching the metrics.
kew: update to 3.7.3
- Optimisations for large music collections/slow disks and a key
binding/input handling overhaul.
- kew play <filepath> , plays a file or a the contents of a
directory.
- Added support for USLT lyrics tag including USLT with embedded
synchronized lrc content
- bug fixes
racket: update to 9.0
- Supports parallel threads
- Parallel threads can be created using the #:pool argument to
thread creation.
- Threads created with #:keep set to 'results
will record their results for later retrieval with thread-wait.
- The black-box wrapper prevents the optimizing compiler from
optimizing away certain computations entirely. This can be helpful
in ensuring that benchmarks are accurate.
- The decompile-linklet function can map linklets back to
s-expressions.
- When using BC Racket, the processor-count function is changed to
always return the parallel count.
- We now distribute “natipkg” packages for AArch64, useful for
[8 lines not shown]
OpenJPH: update to 0.26.0.
This version:
Renames src/core/common to src/core/openjph, as request by @cary-ilm. It is best to use his words
" OpenJPH headers are included in application code via #include <openjph/ojph_version.h>. The headers are expected to be in a folder named "openjph". The cmake configuration places them there in the installation step.
However, if OpenJPH is incorporated into an application via cmake's add_subdirectory, there is no installation step, the headers are included directly out of the source tree. There is no "openjph" folder, leading the #include <openjph/ojph_version.h> to fail.
Renaming the "common" directory to "openjph" resolves the build issue, since the headers then live inside the source tree in a directory with same name as the installation. The use of the "common" directory name is entirely internal to the OpenJPH build, it has no impact on the installation. The name should be arbitrary, so there should be no downside to renaming it this way."
Modifies error message names. This may break your code.
The modified versions are more descriptive, and less likely to be caught in a preprocessor macro.
Address an issue identified by @clshortfuse. Thank you Carlos.
During compilation on windows using clang-cl, the compiler may received flags designed for clang or gcc.
What's Changed
Merges PR #236, and another two smaller issues. by @aous72 in #237
lcov: update to 2.4.
Changes since v2.3.2:
enhanced criteria.pm module, to check function, branch, and MC/DC metrics.
enhance llvm2lcov to support llvm/21 and higher.
various bug fixes
