Open
Description
@dylan-sa has written a Python script to materialize the subclass inferences as per issues #819 and #714. I would like it to go into the pre-commit hook so it's always up-to-date for use during development, not just in released versions. I can see two possible implementations, but there may be others:
- Rewrite the Python script in Java/Jena and create a jar file to run from the main pre-commit hook.
- Retain the Python script. In order to ensure that everyone has Python, this entails additions to setup.cmd:
a. Install Python
b. Create a virtual environment
Then the main pre-commit hook would run the Python script.
Approach 1 seems a lot cleaner. I can't evaluate the relative effort. @Jamie-SA @e2dubba @eddie-thomas @dhurlburtusa @coltonglasgow @justin2004 Thoughts? Maybe other approaches?