osrm-backend
osrm-backend copied to clipboard
New repo for Python bindings
Hi @DennisOSRM ,
we're about to start the GSoC project to publish proper Python bindings for OSRM. They'd ideally be hosted under the Project-OSRM namespace for some level of authenticity:) @SiarheiFedartsou and me are mentoring.
Are you ok with adding a repo there? The name is still a bit unclear, so no need for action yet. PyPI has already tons of OSRM packages. Since we already have a few others for similar projects and they all follow a pattern, I'd like to have OSRM following the same, i.e. calling it pyosrm. Which is of course taken.. I asked the author if he'd be ok yanking his project from PyPI: https://github.com/enricodvn/pyosrm/issues/8
Sounds excellent! Thumbs up from my side.
Some update here: @whytro has been working on the OSRM python bindings over in https://github.com/gis-ops/py-osrm (README is not done yet ;)). We're already in the packaging stage, so it'll be done soon-ish, latest in 4 weeks when GSoC is over. The bindings are fairly closely modeled after the node bindings.
Can we open the repository for the project @DennisOSRM ? We called it "py-osrm" now, since that's still available on PyPI (which is quite overcrowded with OSRM related libs). In the end people should be able to do import engine from osrm though, it's just the project name. For dev & maintenance it'd be good to have @whytro, @SiarheiFedartsou and myself as admins of the repo. Does that sound okay?
Do you want to transfer the repo over to the OSRM org?
Jep, that’d be ideal I think, for visibility/credibility etc. At least if we can get admin rights there, that’d be important. WDYT?
Sounds good to me.
@DennisOSRM do you have time to look into this soon-ish? We're in the last week of GSoC now and it'd be cool to move to the official repo for the evaluation.
To host it on PyPI, should we create a OSRM account there? How is npm handled? Is there already a shared email address we can use for this? Cc @SiarheiFedartsou
This issue seems to be stale. It will be closed in 30 days if no further activity occurs.