This is an attempt to "nitpick" small edge cases that might be responsible for occasionally returning `1` as a factor when the number to factor is _not_ prime. It might increase reliability, somewhat. (At least from this point, it's not clear if there even _is_ an edge case bug in this library, insofar as I can't identify one in something like only 800 lines of code in total besides wheel arrays. We can't blame the ABI without due diligence, but the ABI is not infallible. Another possibility is edge cases in the Boost `cpp_int` type.)
**Full Changelog**: https://github.com/vm6502q/FindAFactor/compare/v1.8.0...v1.8.1
sha1sum results:
fa367f1f353704e1b20834b378f48355e74ab54a FindAFactor-1.8.1-cp310-cp310-manylinux_2_35_x86_64.whl
7f44fd608c9a92a75277ef55d17b5ded422b00c0 FindAFactor-1.8.1-cp312-cp312-manylinux_2_39_x86_64.whl
dfc185ac97a9f771a470fd4aa22452543865a8a4 FindAFactor-1.8.1-cp38-cp38-manylinux_2_31_x86_64.whl
1bf178f37994329625fdb97629865206ea7713e4 findafactor-1.8.1.tar.gz