You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should start using int64 instead of uint64 wherever possible, since implicit conversions between the two can trip up commonly used libraries, and also cause subtle problems when serializing to language-agnostic formats, such as json, protobuf, and sqlite.
More crucially, the use of uint64 prevents us from using the numexpr library (or even having it installed), which is the preferred engine for pandas.DataFrame.query().
In practice, we never use the sign bit in our sv/body IDs, so there should be no problem switching to int64.
The text was updated successfully, but these errors were encountered:
We should start using
int64
instead ofuint64
wherever possible, since implicit conversions between the two can trip up commonly used libraries, and also cause subtle problems when serializing to language-agnostic formats, such as json, protobuf, and sqlite.More crucially, the use of
uint64
prevents us from using thenumexpr
library (or even having it installed), which is the preferred engine forpandas.DataFrame.query()
.In practice, we never use the sign bit in our sv/body IDs, so there should be no problem switching to
int64
.The text was updated successfully, but these errors were encountered: