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
The least Python version supported by KNIME is 3.11
In our previous dependencies it says numpy=1.23.5 #required to fix problem with latest version of numpy and curl=8.1.2 #required by libgdal which includes an older version with vulnerabilities, do have have the nodes with these problems. especially for curl. It's better to have these nodes and tested if they got fixed by least version of the package
conda doesn't have the least version of keplergl, it can be installed by pip and pip will install ipykernel, so we can remove ipykernel depandacy
Below is some of the least version packages we can get when specify curl and numpy version. This way we will still use the same version of geopandas, if you can use least version of curl, then we can use the least version of geopandas.
name: geospatial_env
channels:
- knime
- conda-forge
dependencies:
- python=3.10
- knime-extension
- knime-python-base
- packaging
- curl=8.1.2 #required by libgdal which includes an older version with vulnerabilities
- cvxopt
- esda
- fiona
- folium
- geopandas=0.14.4
- geopy
- h3-py
- jmespath
- libgdal
- libpysal=4.12.1
- mgwr
- numpy=1.23.5 #required to fix problem with latest version of numpy
- osmnx
- polyline
- pyproj
- pysal=24.1
- rasterio
- seaborn
- shapely
- sympy
- pip
- pygeoda
- pointpats
- pip:
- ipinfo
- pulp
- keplergl
In general for now try to update as many dependencies as possible independent of the existing comments in the dependency file since they might no longer hold if we update the major dependencies.
In our previous dependencies it says numpy=1.23.5 #required to fix problem with latest version of numpy and curl=8.1.2 #required by libgdal which includes an older version with vulnerabilities, do have have the nodes with these problems. especially for curl. It's better to have these nodes and tested if they got fixed by least version of the package
For numpy we should update to the latest supported version and see if the nodes are still executing fine.
For curl the problem was that we couldn't update libgdal which had a dependency to a curl version with a security problem. However if we can update libgdal we should try to update curl as well to its latest version and check that this version has no known critical security problems.
To pick up a draggable item, press the space bar.
While dragging, use the arrow keys to move the item.
Press space again to drop the item in its new position, or press escape to cancel.
To pick up a draggable item, press the space bar.
While dragging, use the arrow keys to move the item.
Press space again to drop the item in its new position, or press escape to cancel.
@UrbanGISer I may need your help with these two nodes
Activity
[-]Update Python to 3.x[/-][+]Update dependencies to latest version[/+]wybert commentedon Feb 8, 2025
3.11
numpy=1.23.5 #required to fix problem with latest version of numpy
andcurl=8.1.2 #required by libgdal which includes an older version with vulnerabilities
, do have have the nodes with these problems. especially forcurl
. It's better to have these nodes and tested if they got fixed by least version of the packagekeplergl
, it can be installed by pip and pip will installipykernel
, so we can removeipykernel
depandacycurl
andnumpy
version. This way we will still use the same version ofgeopandas
, if you can use least version ofcurl
, then we can use the least version ofgeopandas
.koettert commentedon Feb 10, 2025
In general for now try to update as many dependencies as possible independent of the existing comments in the dependency file since they might no longer hold if we update the major dependencies.
For numpy we should update to the latest supported version and see if the nodes are still executing fine.
For curl the problem was that we couldn't update libgdal which had a dependency to a curl version with a security problem. However if we can update libgdal we should try to update curl as well to its latest version and check that this version has no known critical security problems.
wybert commentedon Feb 28, 2025
The nodes are still affected by the updates,
wybert commentedon Feb 28, 2025
The spatial heatmap is a bug from folium, see python-visualization/folium#2098
wybert commentedon Feb 28, 2025
The spatial weight can be fixed and could work on offline environment by removing the mock import.
wybert commentedon Mar 1, 2025
For LocationAnalysis category. Most of the nodes has problems because of the
pulp
updates. Some thing like below,These works well when
pulp==2.7.0
but not with the latest version ofpulp==3.0.2
wybert commentedon Apr 15, 2025
@UrbanGISer I may need your help with these two nodes
Update dependencies from #384 without version constraints
from #384 bruch
10 remaining items