Sybren A. Stüvel
11a352968a
Two-way variable implementation in the job submission end-point. Where Flamenco v2 did the variable replacement in the add-on, this has now been moved to the Manager itself. The only thing the add-on needs to pass is its platform, so that the right values can be recognised. This also implements two-way replacement when tasks are handed out, such that the `{jobs}` value gets replaced to a value suitable for the Worker's platform as well. |
||
---|---|---|
.. | ||
flamenco | ||
.openapi-generator-ignore | ||
mypy.ini | ||
openapi-generator-cli.jar | ||
poetry.lock | ||
pyproject.toml | ||
README.md |
Flamenco 3 Blender add-on
Setting up development environment
~/workspace/blender-git/build_linux/bin/3.1/python/bin/python3.9 -m venv --upgrade-deps venv
. ./venv/bin/activate
pip install poetry
poetry install
Generating the OpenAPI client
- Make sure Java is installed (so
java --version
shows something sensible). - In the root directory of the repository, run
make generate-py
Type annotations and lazy imports
This add-on tries to only load Python packages from wheel files when necessary. Loading things from wheels is tricky, as they basically pollute the sys.modules
dictionary and thus can "leak" to other add-ons. This can cause conflicts when, for example, another add-on is using a different version of the same package.
The result is that sometimes there are some strange hoops to jump through. The most obvious one is for type annotations. This is why you'll see code like:
if TYPE_CHECKING:
from .bat_interface import _PackThread
else:
_PackThread = object
This makes it possible to declare a function with def func() -> _PackThread
, without having to load bat_interface
immediately at import time.