> No, the problem persists:
>
> $ py2dsp -v pystow
> D: py2dsp py2dsp:156: version: 3.20220707
> D: py2dsp py2dsp:157: ['/usr/bin/py2dsp', '-v', 'pystow']
> /usr/bin/py2dsp:163: DeprecationWarning: There is no current event loop
> loop = asyncio.get_event_loop()
> D: py2dsp py2dsp:44: args: Namespace(verbose=True, quiet=False,
> root='/tmp/result', clean=False, build=False, application=False,
> profile=None, github=None, distribution='UNRELEASED', revision='0~py2deb',
> message='converte0~py2deb', name='pystow')
> E: py2dsp py2dsp:167: 'releases'
> Traceback (most recent call last):
> File "/usr/bin/py2dsp", line 165, in <module>
> loop.run_until_complete(main(args))
> File "/usr/lib/python3.10/asyncio/base_events.py", line 646, in
> run_until_complete
> return future.result()
> File "/usr/bin/py2dsp", line 74, in main
> fname = yield from download(name, version=version, destdir=args.root)
> File "/usr/share/pypi2deb/pypi2deb/pypi.py", line 124, in download
> release = details['releases'].get(version, {})
> KeyError: 'releases'
this seems to be related to
https://discuss.python.org/t/backwards-incompatible-change-to-pypi-json-api/17154
, although they say /pypi/<project>/json (what py2dsp uses to gather
the latest released verison) still contains the releases key, what i
noticed is that endpoint now returns 2 concatenated jsons, and aiohttp
json() (quite understandably) returns the latest one, which does not
contain releases.
appreciate if you can log a bug via reportbug
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi
