Replies: 1 comment 1 reply
-
|
Thanks, I didn't get a notification for you starting this discussion so it took me a minute to see this.
The biggest issue for me is that many tables are irregular and the current API is broken for them. The second biggest issue is providing normalized tables and collections of tables for whole table sets. Thanks for the star. Seeing a couple of people take an interest makes me want to ship the changes that are necessary. I will try to close out all the open issues, hopefully something that looks like 1.0 is available by the end of October. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Great work!
Here're some points that I think may be worth considering.
tableNameother than passing a full table name especially for those who don't use VS code.loadto return a table as a DataFrame with MutiIndex would be nice.Beta Was this translation helpful? Give feedback.
All reactions