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.

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

findMelOnlyCommands() broken #412

Closed
YKdvd opened this issue Jun 7, 2018 · 2 comments
Closed

findMelOnlyCommands() broken #412

YKdvd opened this issue Jun 7, 2018 · 2 comments

Comments

@YKdvd
Copy link

YKdvd commented Jun 7, 2018

pymel.tools.mel2py.findMelOnlyCommands() doesn't seem to work. mel2py imports the factories module, and the findMelOnlyCommands() routine then tries to call factories.mayaDocsLocation(). Unfortunately, "mayaDocsLocation()" is apparently in the sibling "parsers" module, not "factories".

Both Maya 2013 (pymel 1.0.4) and 2018 (1.0.10) seem to have the error, so it would seem this has been broken for quite some time?

If I ever get a chance I might try and fix the mayaDocsLocation() import/call, although perhaps this code relied on Maya documentation formatting that has changed/broken over the years?

@pmolodo
Copy link
Contributor

pmolodo commented Jul 18, 2018

Hmm... we should probably get rid of this function, or at least make it private. You were correct in guessing that the code relies on formatting that has changed... so this is definitely not something we would expect to work for end users.

pmolodo added a commit that referenced this issue Jan 2, 2019
was apparently broken, and is no longer used.

addresses: #412
@pmolodo
Copy link
Contributor

pmolodo commented Jan 3, 2019

I removed this command, since it's not really used anywhere. Thanks for the report!

31e2769

@pmolodo pmolodo closed this as completed Jan 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants