outdated

[nilsnolde]

Comment:

Maintainer here: I wasn't even aware that someone put routingpy on conda. Just found it via a related discussion where someone reported they couldn't install routingpy because of outdated dependencies: opengeos/geospatial#16 (comment). Multiple ways how this could be fixed, but I think it's safe to never install those optional dependencies via conda, so they can go IMO. They're nice once you clone the original repository and want to run the example notebooks.

On a more general note: I don't really like that it's a separate repo here which apparently needs to be maintained separately and thus goes stale without the authors of the actual project even knowing about. While the intention is good, it's inevitably going to cause problems like the one that bubbled up now, ultimately frustrating users and giving bad rep to routingpy.

Is there a (low-maintenance) way of adding conda(-forge) support to the upstream repo? Maybe you have an example of another repo doing that? Ideally it's just an additional config file and a github action step. I personally have no interest in conda tbh, so the lower tech it is, the better:)

[knaaptime]

will create an issue upstream, but for context @nilsnolde, I'm happy to help maintain this recipe. The conda-forge tools have matured enough so it's not much of a chore. The bot will continuously look at pypi or github releases of routingpy, then update the recipe here accordingly. Would you be willing to do github releases or sdist releases on pypi?