But not just in that one directory. Now my several different installs all work and before that none of them did. So something is getting setup in the overall environment from running the dev install that is allowing vassal-shim to be found.
I can't explain how this could be happening.
vassal.py locates the JAR relative to itself, so there's no way it's going to find the JAR in another repo. Doing an editable install means that the code is run directly from where it is (instead of being copied over to
site-packages/ and run there), so by definition, it's a local, non-global installation.
Have you set up separate virtualenv's for each repo? One thing I can think of is that you're running the program using the
vasl-templates command, which is set up during the
pip install, and
is installed into the current virtualenv. So, if you activate the virtualenv for installation A,
cd to installation B, then run the
vasl-templates command, you will actually be running the code from installation A.
If you haven't created virtualenv's, each installation will be using the same
site-packages/ (whether it be system or user), then that could maybe explain how fixing one installation magically causes the others to start working. But I don't think so, since the JAR doesn't get installed when you do a non-editable install, so it's never going to work anyway.
But all this is moot, since the code should've picked up the JAR that's in source control. And even if you've rebuilt it, it should've overwritten the old one i.e. it will still live at the same file path.
The only way I can think of to get the outcome you've reported is that you done a non-editable install (so the code has gone into site-packages/), the code complained about not finding the JAR (because it doesn't get installed into site-packages/), so you've cd'ed into site-packages/vasl-templates/vassal-shim/ and built the vassal-shim JAR from there (not $/vassal-shim/ in your local repo), thus creating a new JAR at a location where the code in site-packages/ can find it, and ta-da: things work. No. this doesn't make sense either, because the
vassal-shim/ directory doesn't get installed into
site-packages/. I'm stumped
I would:
- delete all your installations
- make sure all your site-packages/ are clean i.e. there is no vasl-templates package, nor a possible spurious releases/ directory that may have inadvertently been created (if my hypothesis above is correct)
- clone the repo again, create a virtualenv, do an editable pip install
I just tried this on a clean installation of Fedora 36, and it works.