-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
GDAL_PYTHON_BINDINGS_WITHOUT_NUMPY is ignored #11853
Comments
the way it is is implemented is more about GDAL_PYTHON_BINDINGS_WITHOUT_NUMPY=1 not erroring out if building without numpy. |
rouault
added a commit
to rouault/gdal
that referenced
this issue
Feb 20, 2025
…RUE or NO/0/OFF/FALSE Fixes OSGeo#11853
rouault
added a commit
to rouault/gdal
that referenced
this issue
Feb 20, 2025
…RUE or NO/0/OFF/FALSE Fixes OSGeo#11853
rouault
added a commit
to rouault/gdal
that referenced
this issue
Feb 20, 2025
…RUE or NO/0/OFF/FALSE Fixes OSGeo#11853
rouault
added a commit
to rouault/gdal
that referenced
this issue
Feb 20, 2025
…RUE or NO/0/OFF/FALSE Fixes OSGeo#11853
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the bug?
When defining GDAL_PYTHON_BINDINGS_WITHOUT_NUMPY=1, when numpy package is installed, gdal will still use the numpy despite being told not to.
Steps to reproduce the issue
Versions and provenance
latest
Additional context
No response
The text was updated successfully, but these errors were encountered: