New release pending? / Python >= 3.11 need a compiler when installing

[amotl]

Dear Kenneth,

first things first: Thanks a stack for conceiving and maintaining this excellent package. We are using it for wrapping a HTTP API around Vasuki's core functions for quite a while, and absolutely love it.

Now, we are running into a problem, and hope you will be able to help.

With kind regards, Andreas.

Problem

• Responder version 2.0.7 has been released 4 years ago, and doesn't work well for us.
• Development head version works for us in development mode, but we can't release Vasuki using that version any longer to PyPI, because of increased constraints compared to the last release in 2023.

  ERROR    HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
           Can't have direct dependency: responder@ git+https://github.com/kennethreitz/responder.git@e9613500daf ; extra == "service". See
           https://packaging.python.org/specifications/core-metadata for more information.

References

• https://github.com/daq-tools/vasuki/pull/28

  building 'httptools.parser.parser' extension
  creating build/temp.linux-x86_64-cpython-311
  creating build/temp.linux-x86_64-cpython-311/httptools
  creating build/temp.linux-x86_64-cpython-311/httptools/parser
  creating build/temp.linux-x86_64-cpython-311/vendor
  creating build/temp.linux-x86_64-cpython-311/vendor/http-parser
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/opt/hostedtoolcache/Python/3.11.9/x64/include/python3.11 -I/tmp/pip-install-mznqineo/httptools_cb5a191155d74385884193c1d772c3df/vendor/http-parser -c httptools/parser/parser.c -o build/temp.linux-x86_64-cpython-311/httptools/parser/parser.o -O2
  httptools/parser/parser.c:212:12: fatal error: longintrepr.h: No such file or directory
  212 |   #include "longintrepr.h"
  |            ^~~~~~~~~~~~~~~

  -- https://github.com/daq-tools/vasuki/actions/runs/9038214344/job/24838867426?pr=28#step:5:218

^^ This is probably coming from an outdated version constraint in responder 2.0.7, which has been fixed already in the development head variant.

[amotl]

Apologies that I've missed to inspect that other report submitted by @michela more closely. It is probably the identical issue.

• GH-518

[amotl]

Hi again,

given that the code base already includes relevant fixes, fixing downstream issues would just be another release away. Let me also tag you, @kennethreitz, as well as @taoufik07, @tomchristie, and @BNMetrics, to humbly ask if anyone of you could make a difference satisfying downstream users?

Thanks a stack in advance!

With kind regards, Andreas.

[amotl]

Hi there,

can we humbly ask if someone would be able to support downstream users by running a corresponding release? Please let us know if you need any support on this matter, we may be able to lend a hand.

With kind regards, Andreas.