-
Notifications
You must be signed in to change notification settings - Fork 718
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Please support DuckDB 1.0 #590
Comments
|
@longxiaofei - thank you! I see you did this 0b4df99 This means you constantly have to chase every major/minor/bugfix release of DuckDB to allow DuckDB users to install it with pygwalker (unless they know how to override your version constraint which is what I did yesterday when I ran into this issue). I think if you simply did Note that for me and I think most |
Hi @cdeil I agree with your point. Previously, the upgrade from DuckDB 0.8 to 0.9 caused some commonly used features in PyGWalker to stop working. As a result, we had to restrict the DuckDB version and were cautious about updating it. Now, it seems that DuckDB has become more stable. In the next version of PyGWalker, we plan to remove the version restriction on DuckDB. |
DuckDB released version 1.0 ( see HERE) which we are using in our project.
You are currently forcing DuckDB 0.10 here:
pygwalker/pyproject.toml
Line 22 in 7a846a1
and when I ran
pip install pygwalker
to use it for exploratory analysis this downgraded and installed the old DuckDB you are requiring currently.I think DuckDB didn't change much between 0.10 and 1.0 and they almost never break backward compatibility. Could you please try to remove the upper bound and support use DuckDB 1.0 together with PygWalker?
Please, please, please ... :-)
The text was updated successfully, but these errors were encountered: