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

routingpy ipykernel update #66

Closed
ArterialMapping opened this issue Apr 27, 2022 · 1 comment
Closed

routingpy ipykernel update #66

ArterialMapping opened this issue Apr 27, 2022 · 1 comment

Comments

@ArterialMapping
Copy link

ArterialMapping commented Apr 27, 2022

Is it possible to update routingpy per this documentation? opengeos/geospatial#16

@ArterialMapping It appears that routingpy requires ipykernel >=5.3.4,<6, which was released over a year ago. Many packages in the geospatial stack require a much newer version of ipykernel. routingpy needs to bring ipykernel up to date before it can be added to geospatial.

https://github.com/conda-forge/routingpy-feedstock/blob/c32ee1d1500c3f6bbda723b342886b9b45488513/recipe/meta.yaml#L30 image

[image

@nilsnolde
Copy link
Owner

problem is that we didn't even know that routingpy is on conda-forge. it's a separate repo, they didn't even tell us it exists or ask for upstream support, and now it's stale, because they didn't touch it in 1 year. either someone steps up and includes a direct conda-forge support in routingpy (this repo) or they'll be better following upstream releases or we'll remove routingpy entirely from conda.

this is the repo, I already opened an issue, let's see what they say: https://github.com/conda-forge/routingpy-feedstock

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

No branches or pull requests

2 participants