Hello, Here is a video I made discussing the various types of Python available in Maya. And when to use which API. A lot of people still use cmds, and haven't discovered the advantages of Pymel yet. Hopefully this will help spreading the word. The official Autodesk intro is also great at comparing both of them. And I go…
That's a very broad generalization - borderline trash talk. Too slow for what? Material managers? UV tools? Exporters? Auto-riggers? I have worked on everything of that except the latter (rigging is not my thing) and I've never had any performance problems what so ever. The real benefit is that developing tools with PyMEL…
Tbh, I've found that for situations where performance is an issue cmds isn't faster enough to make me want to use it over pymel. There's no doubt that pymel is slower - noticeably so in many situations - but if you're really interested in speed you don't want to be using python or even doing the work in Maya if you can…
@Deadly Nightshade I don't want to beat a dead horse, but I figured I would add some of my own speed comparisons... for science. I'm using Maya 2018 btw, maybe Pymel is way faster in newer versions. Pymel import time: 1.0759999752 secondsCmds import time: 0.00200009346008 secondsImporting Cmds is 537.974848015x faster than…
No trash talk, I was just stating that the performance does not suit my needs for production and I no longer use pymel for that reason. I don't see readability as an issue, if the implementation is difficult to read, you can always wrap up stuff yourself by writing your own functions or classes and comment on what you are…
I like the idea of Pymel, but I have found that it is way too slow for any real production use. I used to work with it all the time, but as my code grew, the sluggish performance became quite noticeable. If you are having to switch to OpenMaya for most procedures to speed up performance, I don't see what the real benefit…