Implementing this in 1.1.3 for release on Monday.
It's due to just having realised that Maya on Linux refers to it's
python-bin, thus not registering as Maya at all. And, realising that there will be more of these scenarios popping up, like with Hiero and @tokejepsen just recently, it felt like a necessary next step.
Practically, everything will still work, including
current_host (which is now deprecated, read on) with the added requirement that an integration must be loaded for plug-ins to filter against it.
For example, when you load Maya, it's the Pyblish for Maya integration that registers the host,
maya. If this doesn't happen, then plug-ins filtered by
hosts = ["maya"] won't get run.
You have most likely already done this, as it's how Pyblish QML automatically registers itself as well, but in the rare case where you are using a host, along with plug-ins filtered by that host, but haven't registered the integration, you will notice a change in behaviour.
Like mentioned above,
current_host is still alive and well, but is to be considered deprecated, as it will only return the last registered host. I've made it so that Maya, for example, registers
maya in this order, meaning
current_host will still return the expected
maya for backwards compatibility.
registered_hosts() is the official method with which to query which hosts are currently supported.
>>> import pyblish.api
["python", "mayabatch", "mayapy", "maya"]
python is automatically registered during initialisation, but can be removed, along with every other hosts, should you need, via
Here are all the new functions related to this functionality.