do you mean 0.7 or 0.9? because 0.7 is really old. on our downloads page
we've posted 0.9.3, which is a beta version that is more forward compatible
with 1.0 (it offers a pymel.all, just like 1.0). i think a bit more work might
need to be done to 0.9.3 to make it more forward compatible (like adding
pymel.core.nt and pymel.core.dt aliases) , but you're gonna have to ditch the
0.7 branch.
if you're using 0.9.3 and 1.0 then you can just do:
from pymel.all import *
both versions provide a converter that will change all imports of pymel to
pymel.all.
-chad
On Feb 4, 2010, at 10:45 AM, Count Zer0 wrote:
> Is there a better way to have multiple versions of pymel (.7 & 1.0)
> installed and not have this at the top of every one of my scripts:
>
> "
> import maya.mel as mm
> ver = mm.eval("getApplicationVersionAsFloat")
> if ver >= 2008: from pymel.core import *
> else: from pymel import *
> "
>
> We'll have multiple teams using different versions of Maya (some
> possibly using Maya 8.5 which does not work w/ pymel 1.0). Each team
> will be calling from scripts that will be importing pymel. I need to
> make sure every script imports the right version of pymel at the top,
> thus my hacky code above. Just a little bulky is all. I tried to
> create a little module with those lines and call that, but then, of
> course, pymel is not loaded into the namespace of the actual script
> I'm trying to run.
>
> Perhaps there is a larger view I'm missing? a better way to install
> multiple versions of pymel for multiple versions of Maya and let users
> all call from the same Maya Python scripts?
>
> Thanks,
>
> -jason
>
> --
> http://groups.google.com/group/python_inside_maya
--
http://groups.google.com/group/python_inside_maya
