Andreas, > > Any hint would be welcome > > See: https://github.com/explosion/catalogue/issues/27 > > TLDR: skip that test on Python 3.10 for now.
this seemed an easy enough issue that, with some common and expected due diligence, you could have figured it out yourself: checking upstream issue tracker and in general google for an error is something i would say any maintainer is expected to do. since it's not the first time you write to this list with a traceback or error, asking for help, and the answer from here is generally pretty straight-forward, i'm wondering why you were not able to find the solution directly? some of your previous emails are really python 101 questions. If it's because you have too many things on your plate, it's one thing, if it's python knowledge is another, but it seems a pattern that only you engage in. I dont think it's a problem per se, but i also want to understand if the time debian-python@ dedicates to solve your issues is well spent. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi