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
In my current workflow, I occasionally export PyRIT's results to Excel files. However, when using Python 3.12, my script that converts DuckDB entries to Excel in PyRIT silently crashed.
Upon investigating, I noticed that the project is locked to DuckDB version 0.10.0 in the pyproject.toml file.
Is there a specific reason for using this version? Running my conversion script with DuckDB 1.1.3 no longer crashes Python 3.12 and doesn't appear to affect PyRIT.
The text was updated successfully, but these errors were encountered:
Interesting! Thanks for raising this. I hadn't noticed that we're pinning this. I'm working through a bunch of issues before our next release, so I can look into upgrading to duckdb>=1.0.0 which is probably the difference between the failures and the working state that you're observing post-v1. I suspect this will require a few changes, though, since upgrades of the major version usually have breaking changes.
romanlutz
changed the title
DuckDB Version
MAINT DuckDB Version upgrade
Nov 19, 2024
Hi!
In my current workflow, I occasionally export PyRIT's results to Excel files. However, when using Python 3.12, my script that converts DuckDB entries to Excel in PyRIT silently crashed.
Upon investigating, I noticed that the project is locked to DuckDB version 0.10.0 in the pyproject.toml file.
Is there a specific reason for using this version? Running my conversion script with DuckDB 1.1.3 no longer crashes Python 3.12 and doesn't appear to affect PyRIT.
The text was updated successfully, but these errors were encountered: