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
TILEDB_STRING_ASCII Now Displaying As UTF-8 / str Everywhere
* Previously `TILEDB_STRING_ASCII` data was inconsistently displayed
as `bytes`
* There is a need to coerce to `str` everywhere because (1) previously
the resulting dataframe displayed ASCII as bytes with Pyarrow disabled
but as str with Pyarrow enabled, and (2) this fix would remove the
need to copy large amounts of data to convert back and forth in the
TileDB-SingleCell Python API
* Warning now emitted to the user to pass `dtype="ascii"` for string dim
types in lieu of `np.bytes_` or `np.str_` for clarity. All three still
work and under the hood use `np.str_` and `TILEDB_STRING_ASCII`
* `repr` of string dimensions is now always displayed as `dtype="ascii"`.
Calling `.dtype()` will return `np.dtype('U')` as the return signature
of `dtype` requires a Numpy dtype
Copy file name to clipboardExpand all lines: HISTORY.md
+3
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,8 @@
1
1
# In Progress
2
2
3
+
## API Changes
4
+
*`TILEDB_STRING_ASCII` displaying as `str` instead of `bytes`[#1304](https://github.com/TileDB-Inc/TileDB-Py/pull/1304)
5
+
3
6
## Misc Updates
4
7
* Wheels will no longer be supported for macOS 10.15 Catalina; the minimum supported macOS version is now 11 Big Sur [#1300](https://github.com/TileDB-Inc/TileDB-Py/pull/1300)
5
8
* Wheels will no longer supported for Python 3.6 [#1300](https://github.com/TileDB-Inc/TileDB-Py/pull/1300)
0 commit comments