Pos

Latest version: v0.0.0

Safety actively analyzes 723177 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

0.12.41

Fixed

- When adding bitfield back-sort we broke compatibility with BSD. That is fixed in this release.

0.12.40

Added no bitfield plotting option (-e)

0.12.39

Added

- We now instrument temp space, time, and memory used building two k=27 on ci for performance tracking and comparison one for each back propagation method.

Changed

- We added a `-e` flag to allow you to choose between bitfield back propagation and the original back propagation. This brings performance a little ahead of the Beta 17 plotter release. However bitfield back propagation may perform faster on spinning disk. YMMV.
- More of the sorts in the bitfield sort use uniform sort for better performance.
- This version requires slightly more RAM at each k size.

Fixed

- Previous releases were not deleting temp files as they were no longer needed and therefor temp space needed for a k=32 went from 332 GiB to 499 GiB. This version only needs 332 GiB when using -u 64.
- Beta 17 style back prop had a buck that could occasionally lead to a segfault. We fixed that when using the `-e` flag.

0.12.38

Fixed

- We now close unused file-handles in the temp directory to avoid exceeding rlimit when using the new bitfield backprop and 128 sorting buckets.

0.12.37

Fixed

- Changed scope of match_indexes to make sure they are always reset even if R bucket is empty. This fixes "error 0" retrying in 5 minutes issues in certain edge cases.
- Windows plotting now correctly reports CPU utilization.

0.12.35

Added
- F1 generation is now fully parallel for a small speedup.
- We have bitfield optimized phase 2. There is only about a 1% increase in speed from this change but there is a 12% decrease in writes with a penalty of 3% more reads. More details in [PR 120](https://github.com/Chia-Network/chiapos/pull/120)
- You can now build chiapos with Cmake and MSVC. We know build and test C++ for Windows as well as create and test Windows wheels.

Changed
- We have moved from using gulrak/filesystem across all platforms to only using it on MacOS. It's required on MacOS as we are still targeting Mojave compatibility. This should resolve Windows path issues.
- Various pointers and memory management were modernized.

Fixed
- Starting with recent setuptools fixes, we can no longer pass an empty string to the linker on Windows when building binary wheels. Thanks jaraco for tracking this down.

Page 2 of 4

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.