Project isn't dead! bitmath 2.0.0 coming soon! about bitmath HOT 5 OPEN

Docs are building on read the docs now: https://bitmath.readthedocs.io/en/2023-01-26-no-more-py2/index.html

from bitmath.

This is great to hear. One thing I was recently confused about is parse_string_unsafe: "unsafe" means to me that should not use this on untrusted inputs (security) but it seems the function just uses some heuristics/there is some ambiguity. It would be nice if the name reflects that in 2.0. Using an "unsafe" function will be flagged in every code review and will cause the reviewer to dig into the implementation to verify that this is really "safe" to use.

from bitmath.

This is great to hear. One thing I was recently confused about is parse_string_unsafe: "unsafe" means to me that should not use this on untrusted inputs (security) but it seems the function just uses some heuristics/there is some ambiguity. It would be nice if the name reflects that in 2.0. Using an "unsafe" function will be flagged in every code review and will cause the reviewer to dig into the implementation to verify that this is really "safe" to use.

That's a very smart idea. I'll add that to the list

from bitmath.

This is great to hear. One thing I was recently confused about is parse_string_unsafe: "unsafe" means to me that should not use this on untrusted inputs (security) but it seems the function just uses some heuristics/there is some ambiguity. It would be nice if the name reflects that in 2.0. Using an "unsafe" function will be flagged in every code review and will cause the reviewer to dig into the implementation to verify that this is really "safe" to use.

Can I have your thoughts on this?

#101

from bitmath.