Ondřej Samohel

I wonder if we shouldn't be even more specific - be able to define review aovs (or the opposite) on publishing instance in creator. It would pull in the pattern...

first incompatibility: ``` Traceback (most recent call last): File "C:\Users\annat\.pyenv\pyenv-win\versions\3.9.6\lib\threading.py", line 973, in _bootstrap_inner self.run() File "C:\Users\annat\.pyenv\pyenv-win\versions\3.9.6\lib\threading.py", line 910, in run self._target(*self._args, **self._kwargs) File "C:\Users\annat\Documents\pype\op-p3.9\openpype\modules\ftrack\tray\ftrack_tray.py", line 207, in set_action_server elif...

I believe this is actually testable. Tested in Maya 2020 so far without trouble....

Tested on Centos 7, need tests on Macs

Should work on macs, tested on virtual Catalina

@BigRoy this might be the same case you've encountered in your studio?

First warning is on @iLLiCiTiT: ``` Warning, treated as error: Cannot resolve cyclic import: openpype.api, openpype.settings, openpype.settings.entities, openpype.settings.entities.base_entity, openpype.lib, openpype.lib.execute, openpype.lib.log, openpype.lib ```

> Current traceback is unknown for me and didn't find out what is the issue. I think this is caused by that `while True...` loop. It gets executed even when...

Nope, nothing is done yet.

FYI I've just added for one client very simple loader of bgeo to houdini. Nothing fancy. Publishing from standalone publisher has one limitation - it doesn't support `bgeo.sc` and `bgeo.gz`...