Autogenerate code when running setup.py

bessman commented 4 years ago

As discussed in https://github.com/christoph2/pyA2L/issues/13.

setup.py will now generate python code from the antlr grammars as part of the build_py step. It looks for the antlr jar-file in the locations suggested by antlr's documentation. Alternatively, the location of the jar can be specified via the environment variable ANTLR_JAR. I will update the documentation accordingly.

This pull request also removes the py2/3 subpackages (since python2 is deprecated), so the Lexers and Parsers are now part of the main pya2l package. It also removes aml.g, which is superseded aml.g4, as well as all antlr *tokens-files, which are not needed at run-time.

Finally, it adds a .gitignore which, among other things, is configured to ignore Lexer.py and Parser.py to avoid those files being added by mistake in the future.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

bessman commented 4 years ago

Most of the pylint warnings look like false positives to me. Not sure why ANTLR_JAR isn't being set in AppVeyor.

christoph2 commented 4 years ago

OK, let's give it a try.

christoph2 commented 4 years ago

CLASSPATH needs also to be considered, I will fix it.

christoph2 / pyA2L

Autogenerate code when running setup.py #14

Types of changes