On 3/10/25 2:35 PM, Colin Watson wrote:
Source: python-omegaconf
Version: 2.3.0-3
Severity: normal
Prompted by looking into some specific test issues in python-moto, I
began considering what it would take to upgrade python3-antlr4 to
something newer than 4.9.2. This is difficult because ANTLR 4.10
introduced incompatible changes to the lexers and parsers that cause (at
least) test problems in a number of other packages
(https://github.com/antlr/antlr4/releases/tag/4.10); some of these have
been masked by disabling tests, but they still exist. But we now have
some packages that require >= 4.10 as well as some packages that require
< 4.10, so we kind of need to sort this out.
One of the issues is in python-omegaconf, probably best described in
https://github.com/omry/omegaconf/pull/1114. There have been a couple
of .dev releases that included this, but not a proper release, and
https://github.com/omry/omegaconf/issues/1200 doesn't paint a very rosy
picture of its upstream maintenance.
Given that there seem to be no reverse-dependencies in Debian, would it
be better to just remove this and simplify a future python3-antlr4
upgrade?
Thanks,
Hi Colin,
Sorry for the enormous amount of time to reply to this bug.
I do believe omegaconf is useful by itself. Some of my colleagues use it
in (non-free) code they wrote. It's the only nice lib that I know that
parses config in the form of complex yaml file.
Now, if you do have issues with antlr3, and there's a patch available
upstream, just let me know, and I'll apply it to the current version of
omegaconf in Debian.
In the mean time, I'll just close the bug since it seems that was the
only thing you needed. If you need me to add the patch, let me know. In
such case, feel free to reopen this bug, or open a new one (as I'll be
closing it because I'm triaging all remaining bugs in the OpenStack team).
Cheers,
Thomas Goirand (zigo)
