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
Since a few months I took over maintenance of ogr2osm and I noticed this project shows up in the github dependency graph, but it turns out you're depending on your own fork of the project. While github detects the wrong dependency, your setup script may work correctly, I didn't test this.
However, given ogr2osm is now available on pypi and its version is greater than 0.1.0, the risk exists that users have the wrong version installed. There is no obligation of course but as a solution I'd suggest depending on my fork in stead, some issues are fixed regarding both performance and functionality and you can directly use this version as a library in stead of using subprocess.check_call.
The text was updated successfully, but these errors were encountered:
Since a few months I took over maintenance of ogr2osm and I noticed this project shows up in the github dependency graph, but it turns out you're depending on your own fork of the project. While github detects the wrong dependency, your setup script may work correctly, I didn't test this.
However, given ogr2osm is now available on pypi and its version is greater than 0.1.0, the risk exists that users have the wrong version installed. There is no obligation of course but as a solution I'd suggest depending on my fork in stead, some issues are fixed regarding both performance and functionality and you can directly use this version as a library in stead of using subprocess.check_call.
The text was updated successfully, but these errors were encountered: