830c3fe794
As it was decided that the name "tags" would be better for the clarity of the feature, all files and code named "cluster" or "worker cluster" have been removed and replaced with "tag" and "worker tag". This is only a name change, no other features were touched. This addresses part of #104204. Reviewed-on: https://projects.blender.org/studio/flamenco/pulls/104223 As a note to anyone who already ran a pre-release version of Flamenco and configured some worker clusters, with the help of an SQLite client you can migrate the clusters to tags. First build Flamenco Manager and start it, to create the new database schema. Then run these SQL queries via an sqlite commandline client: ```sql insert into worker_tags (id, created_at, updated_at, uuid, name, description) select id, created_at, updated_at, uuid, name, description from worker_clusters; insert into worker_tag_membership (worker_tag_id, worker_id) select worker_cluster_id, worker_id from worker_cluster_membership; ``` |
||
---|---|---|
.. | ||
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.