I have made some changes for our internal use (logging, not popping static resources such as images or js, etc.) that I want to build into a standalone exe for others to use. They have mitmproxy installed, but not Python or the build tools.
I can run my changes in a virtualenv locally and verify that they work. I’m trying to build exes using the following command from .travis.yml:
tox -e rtool -- bdist
It builds executables in the release/build/binaries/windows folder, but their version number is not updated. I’m using 2.0.2 as my base, and updated version.py to 2.0.3 just so I could see if it actually updated. The zip file under release/dist has 2.0.3 in the name, but the exes report 2.0.2 (release version) as their version, and my changes are not present.
What step am I missing? I’ve also tried running both inside and outside a venv, random other
tox commands, etc.