Thank you Thomas! We've been wanting to do this for a while. Having python-antlr3 in xenial is a big help. Thanks for the alert!
The main issues we still have are:
1. Not available in 14.04 (including backports). I need to confirm if it's okay to ditch 14.04 now in a new release.
2. For python3, we rely on upstream antlr3/python3 runtime not available in packages.
Long term we're still looking at replacing antlr3 completely because upstream development has moved on, but that's a complex job and in the mean time we still want to see what we can do.
@Tim, the antlr-3.5-complete.jar file is only used because the Makefile calls on antlr3 to re-generate the parser and lexer from the grammar file on each setup. Do you know why this was needed instead of just using the pre-generated parser and lexer in the repo?
A developer who changes the grammar will still need to use antlr3, but I don't think the end-users need it.
Thank you Thomas! We've been wanting to do this for a while. Having python-antlr3 in xenial is a big help. Thanks for the alert!
The main issues we still have are:
1. Not available in 14.04 (including backports). I need to confirm if it's okay to ditch 14.04 now in a new release.
2. For python3, we rely on upstream antlr3/python3 runtime not available in packages.
Long term we're still looking at replacing antlr3 completely because upstream development has moved on, but that's a complex job and in the mean time we still want to see what we can do.
@Tim, the antlr-3. 5-complete. jar file is only used because the Makefile calls on antlr3 to re-generate the parser and lexer from the grammar file on each setup. Do you know why this was needed instead of just using the pre-generated parser and lexer in the repo?
A developer who changes the grammar will still need to use antlr3, but I don't think the end-users need it.