bitmath icon indicating copy to clipboard operation
bitmath copied to clipboard

Published 20 hours ago • verified publisher icon tbielawa

Project isn't dead! bitmath 2.0.0 coming soon!

Open tbielawa opened this issue 1 year ago • 4 comments

2.0.0 is coming and it will be python 3 only. Keep up with progress on this branch as I work up to the release.

Watch the news file for specifics. https://github.com/tbielawa/bitmath/compare/master...2023-01-26-no-more-py2#diff-61d113525e9cc93565799a4bb8b34a68e2945b8a3f7d90c81380614a4ea39542R25

PR's welcome. Existing PR's will get reviewed to see how they fit into the future direction of the project.

tbielawa avatar Jan 28 '23 02:01 tbielawa

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

tbielawa avatar Feb 06 '23 00:02 tbielawa

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.

FelixSchwarz avatar Feb 12 '23 10:02 FelixSchwarz

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

tbielawa avatar Feb 12 '23 14:02 tbielawa

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?

https://github.com/tbielawa/bitmath/issues/101

tbielawa avatar Feb 13 '23 23:02 tbielawa