-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[python/c++] Connect libtiledbsoma to tiledbsoma readers for dataframes [WIP] #360
Conversation
f6bb262
to
07c55cf
Compare
973dc7d
to
9215877
Compare
0661600
to
681b743
Compare
c402bc0
to
fa97b8b
Compare
10d0d92
to
cab89ba
Compare
1e22705
to
2088997
Compare
2a60d1e
to
fc9fe5f
Compare
The fail is here:
https://gist.github.com/johnkerl/f93ad47c4bfa29fbb929f4e2d3cd83f0 Now we are intentionally suppressing type-checking for However, On the third hand, here diff --git a/apis/python/tests/__init__.py b/apis/python/tests/__init__.py
index 5df0213..8817d3e 100644
--- a/apis/python/tests/__init__.py
+++ b/apis/python/tests/__init__.py
@@ -1,7 +1,16 @@
import pyarrow as pa
-from typeguard.importhook import install_import_hook
+from typeguard.importhook import TypeguardFinder, install_import_hook
-install_import_hook("tiledbsoma")
+class CustomFinder(TypeguardFinder):
+ def should_instrument(self, module_name: str):
+ #print("\nSI >>", module_name, "<<\n")
+ if module_name == 'tiledbsoma.query_condition':
+ return False
+ if module_name == 'tiledb.query_condition':
+ return False
+ return True
+
+install_import_hook("tiledbsoma", cls=CustomFinder) and verified that the
😠 |
|
... behind that now-opened door lie more still-locked doors; upon them is written more typeguard |
0134179
to
fdef919
Compare
be4901b
to
1deb57e
Compare
1deb57e
to
3feb82e
Compare
Closing in favor of #400 |
Status
SOMADataFrame
andSOMAIndexedDataFrame
are on this PRSOMASparseNdArray
andSOMADenseNdArray
will be on a separate PRPR context
This is the three in a group of three related PRs:
read
returnpyarrow.Table
notpyarrow.RecordBatch
(as in an outdated version of that spec) -- now mergedmain-old
which will truly have ASCII columns, obviating the need for ourutil_arrow.ascii_to_unicode_pyarrow_readback
-- now mergedread
methods, which will go in cleanly nowpyarrow.Table
and with the first PR our unit tests will be ready to gopyarrow.LargeBinaryArray
(needing decode) but when we are properly writing ASCII cells via the Python write path then the C++ code will read ASCII cells and return them as strings (no longer needing decoding)