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é <anar...@debian.org> wrote: > On 2023-07-27 13:04:22, Riccardo Coccioli wrote: > > 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/502 > > [2] https://github.com/pyparsing/pyparsing/issues/501 > > Hi! > > Thanks for this! It looks like those are fixed upstream, do we need to > update pyparsing to 3.1.2 to fix this bug or what's the next step? > > (upstream 502 is fixed in 3.1.1, in unstable, but 501 is only in > 3.1.2...) > > a. > > -- > Sous le projecteur, on ne voit pas les autres. > - Félix Leclerc >
