Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

UX bug with pyblish plugins with same classname #395

Open
hannesdelbeke opened this issue Oct 29, 2023 · 2 comments · May be fixed by #397
Open

UX bug with pyblish plugins with same classname #395

hannesdelbeke opened this issue Oct 29, 2023 · 2 comments · May be fixed by #397

Comments

@hannesdelbeke
Copy link
Contributor

hannesdelbeke commented Oct 29, 2023 •
edited
Loading

if 2 pyblish plugins have the same class name, they don't load in Pyblish.
But since no error is thrown, it's hard to spot why the plugins don't load.

A suggestion would be to e.g. print an error message to the console.

(not tested with logging.debug yet, which by default is not enabled.)
@BigRoy
Copy link
Member

BigRoy commented Oct 29, 2023 •
edited
Loading

It should be hitting this by default, skipping the duplicates and debug logging the entry.

@hannesdelbeke
Copy link
Contributor Author

Thank you for locatting the exact line that handles this Roy.

It likely does hit that.
Since log.debug is not enabled by default, the maya console prints nothing.
Would changing this to a debug.warning (so it prints by default to the console) be a worse way of handling this?

This is a similar issue to this ticket #374

@hannesdelbeke hannesdelbeke linked a pull request Nov 19, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

clarify fail and warning messages hannesdelbeke/pyblish-base
2 participants
@BigRoy @hannesdelbeke