Hi,
But this bug is also not related to Cumin in any way. Cumin doesn't have a
dependency on python-eventlet nor python3-trio, which are clearly
the culprit in the traceback.
I was able to reproduce the bug both on sid and trixie, you can see
the details in [0] (Cumin's bug tracking system).
Repo
Thanks for the report Antoine. I'm aware of some issues with Python
3.12/3.13 support, and I was already working on some fix in the upstream
repo to make it compatible with them.
I'll send a related patch to the debian repo once I have all that figured
out. I hope to be able to work on this next we
Pyparsing upstream finally made the v3.1.2 release the other day with the
fix. So I guess once that lands in unstable it should be ok.
On Sat, Apr 6, 2024 at 12:30 AM Antoine Beaupré wrote:
> On 2023-07-27 13:04:22, Riccardo Coccioli wrote:
> > I've checked the issue and opened
I've checked the issue and opened a bug upstream to pyparsing [1] as this
is indeed a regression.
Running CI on cumin I've also found that pylint is reporting new issues
related to pyparsing code, for which I've opened a separate bug upstream
[2].
[1] https://github.com/pyparsing/pyparsing/issues/
This seems to be caused by the version change of python3-pyparsing
fom 3.0.9-1 in bookworm to 3.1.0-1 in trixie/sid.
At first sight it looks like that this minor version change in pyparsing
has caused some backward incompatibility.
I'll have a look in the next few days at what changed and try to p
On Wed, Nov 23, 2022 at 5:15 PM Moritz Mühlenhoff
wrote:
> Hi Antoine,
>
> [Adding Riccardo Coccioli, my colleague at Wikimedia and the primary
> author of Cumin to CC]
>
> > which makes me wonder: should we drop the debian branch on github and
> > gerrit? or shou
6 matches
Mail list logo
