The pyblish.util.publish() function (and all helpers for specific CVEI stage) can take a list of targets but pyblish.util._convenience_iter() uses the global registration in the backend, which causes a bunch of issues:
Targets previously registered get de-registered when process ends (as described in #345)
The pyblish.util.publish() function (and all helpers for specific CVEI stage) can take a list of targets but pyblish.util._convenience_iter() uses the global registration in the backend, which causes a bunch of issues:
It would be nice to modify the logic so that targets explicitly passed to these functions don't get registered globally. What do you think?