PyMEL included in Maya 2011

By now you may have seen the announcements for Maya 2011. It’s my pleasure to tell you that PyMEL will be shipped with Maya, right alongside the maya python package. Those of you still sitting on the fence can now safely get off :slight_smile:

PyMEL is still open source and will stay that way. the PyMEL team is responsible for delivering a stable version of PyMEL to Autodesk for each release, and PyMEL’s unit test suite is now run as part of Maya’s testing framework, so if Autodesk makes a change that break something, we’ll all know about it.

The version of PyMEL included with 2011 will be 1.0.0, but we will still be doing point releases that you can install over top of the pre-installed version in the usual ways. we actually have a 1.0.1 with fixes discovered since the 2011 code freeze that we’ll release shortly. the current set of installation instructions should work across all versions, including 2011. those of you who have tested 1.0 now have some insight into why the installation became more complex: pymel 1.0 comes with modifications to the maya package that are now standard with 2011, but which need to be installed for prior versions of Maya.

the official repo for PyMEL is now on github:GitHub - LumaPictures/pymel: Python in Maya Done Right
git and github are a great way for various users and studios to collaborate on this project. if you go to “network” you can already see we have several users who have forked the pymel project and put in their own features and bug fixes, which we then review and pull in to the main repo (andrew, i’ll get to yours soon, i swear!). I hope that you and your studio will do the
same.

the official homepage and issue tracker for PyMEL is still googlecode:Google Code Archive - Long-term storage for Google Code Project Hosting.

Awesome! This is fantastic.
I was definitely a fence-sitter, as a python user and Maya user prior to being a python-in-Maya user, certain aspects of pymel always made me uncomfortable, but the old pynode refactpr, the recent changes to packaging, and this change in landscape are bloody brilliant. Consider me safely off the fence. That said, there are still things that make me a little uneasy like the operator overloading… (Division for path concatination…?) but some of them like the connection syntax and the reappropriation of the with-statement are pretty inspired.

Congratulations! This is great news, hopefully I’ll find some places I can do some contributions to the codebase!

Very cool development. Congrats!

Wooo!!!

This is fantastic news Chad! Massive props to you and the other contributors for putting together such a phenomenal package. And Autodesk gets a big +1 in my book recognizing its value.

[QUOTE=Lithium;5589](Division for path concatination…?) [/QUOTE]

on unix systems ‘/’ is the path separator, so this actually makes visual sense:

Path(‘/this/that’) / ‘something/else’

anyway, thanks for the props, and keep in mind we’re always open to suggestions for improvements. make a ticket, or better yet, make a fork of the project and implement your change.

Congrats Chad! Definitely great news. Great that’s its remaining open source too. Good lookin’ out. :slight_smile:

Whoa, this is awesome! Congratulations!