Ondřej Samohel

> Hi @antirotor, revisiting this long-forgotten issue and would like to merge it. It's a good feature! There are just a few notes left before a first 1.0 of the...

In fact the fix doesn't work as I thought because it will then left whole string unformatted. Damn.

Sorry, I've noticed your comment just now. > What are you trying to achieve? We just need to keep strings like `{C[x]}` unformatted. That they'll pass through `acre.compute()` just as...

Don't look at it as formatting string. Look at it as raw data - environment variables can have whatever you want inside and I think acre should be able to...

I think that solution with the `ACRE_VERBOSE` is fine. Or maybe we could introduce something like `ACRE_STRICT=1` that will cause acre to fail when it cannot format and it will...

> This PR's Rez integration is solely regarding the addons and modules in the backend, not the running of the actual DCC application and tools, right? So it's not for...

So, based on our discussion with @BigRoy and @iLLiCiTiT , this is example mockup code that might be solution: ```python import subprocess from ayon_core.lib import EnumDef, BoolDef, TextDef, ButtonDef from...

> I quickly prototyped something in the following PR. This is without any guidance. So its a very rudimentary solution. > > This was done before you posted your code...

> EDIT: i realized the `.python-version` file only in the end. i think this would be better than adding the python flag to `uv venv` Ah, I've never get into...

So there is another use case perfect for uv - we can solve some of the issues like [this one](https://github.com/ynput/ayon-unreal/issues/158) or in general all cases where we now install pyside2/6...