Skip to content
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

ThreadWorker: Kompatibilität mit DuckDB (und vermutlich anderen Paketen) herstellen #131

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

MHajoha
Copy link
Member

@MHajoha MHajoha commented Jan 13, 2025

No description provided.

DuckDB (and likely other packages) manually add their submodules (e.g. duckdb.duckdb.functional) during side-effects when the "parent" (e.g. duckdb.duckdb) is loaded. Since extension modules can't be reloaded, it is impossible to re-run these side-effects to recreate these modules. This commit preserves modules without the __loader__ attribute (which is added by Python's normal import machinery), sacrificing isolation for compatibility.
@MHajoha MHajoha requested a review from MartinGauk January 13, 2025 16:54
MHajoha added a commit to questionpy-org/questionpy-sdk that referenced this pull request Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant