We haven't, we're using sitecustomize.py to insert a new system path and import pymel, it's all explained in the docs. So you won't need to remove any default Maya folders.
The problem is that sitecustomize needs to be in the Maya/Python/Libs/SitePackages folder on every machine. We have an Art Pipelines installer that manages that copy. If this is wrong then I'd like to know if sitecustomize can be run from a different location. We have multiple teams on different branches of code. Each team will be locked on that branch (unless they need to take a new release) and therefore each branch could have a different pymel version. I believe we had 4 different version of pymel at one time. We only have 1 now. But the sitecustomize method worked for us. On Tue, Jun 15, 2010 at 6:10 PM, hapgilmore <[email protected]> wrote: > Does that require manually deleting the pymel folder from the maya > 2011 install folder? > > On Jun 10, 11:50 pm, Chad Dombrova <[email protected]> wrote: >> i'd just like to stress that the best solution is to use pymel 1.0 for both >> 2009 and 2011. you can put a single installation on a network mount and >> point both versions of maya at it. >> >> -chad > > -- > http://groups.google.com/group/python_inside_maya > -- David Moulder http://www.google.com/profiles/squish3d -- http://groups.google.com/group/python_inside_maya
