Hi, Munyoki Kilyungi <m...@bonfacemunyoki.com> writes:
> "jgart" <jg...@dismail.de> aliandika: > >>> Sometimes, PyPI versions lag behind upstream versions. >> >> Hi Bonz, >> >> Yes, in my experience that has sometimes been the case because maintainers >> don't make timely releases to PyPI. >> >>> What's the policy on this. Shouldn't we prefer upstream over PyPI? >> >> Our importer works with the JSON API that PyPI provides at >> https://pypi.org/pypi/baz/json >> >> See here: >> >> https://git.savannah.gnu.org/cgit/guix.git/tree/guix/import/pypi.scm?h=master#n141 >> >> That API provides a lot of package data that GitHub does not track in a >> unified and structured way. >> > Then given the above ... >>> Adding extra glue can add unnecessary complexity. >> >> You're right. I thought about that after I sent the email with the idea ;() >> > > PyPi unless we need to use upstream is the way to > go ;) Yes, I was thinking continuing to use PyPI, but attempt to find the repository URL from PyPI's metadata and used that when generating a package definition with the pypi importer. I don't know how feasible that would be. -- Thanks, Maxim
