Hi, I'm getting the exact same error. typing: /usr/bin/env mayapy
launches a mayapy session no problem so thats OK, also, if I change the first line of ipymel to: #!$MAYA_LOCATION/bin/mayapy It makes no difference, and reports the same errors. Unfortunately, my current knowledge of the terminal is very limited so this has got me stumped. I wonder if there is a typo in the version of pymel I have: 0.9.0 ? pymel itself works OK though, either in a terminal shell, or the maya script editor. I would like to get ipymel going though:) Thanks for any help. Dave. On Apr 13, 8:36 pm, Chadrik <[email protected]> wrote: > It looks like the script is being interpreted as a shell script > instead of a python script. The very first line of tools/bin/ipymel > is a fancy way of informing the system what executable to use to > interpret the script: > > #!/usr/bin/env mayapy > > the reason i say it's "fancy" is because usually the path is hard- > coded to the location of the python binary, or in our case mayapy. > mayapy is not guaranteed to be in any one location on all systems so > I'm using the executable 'evn' to determine where to find the 'mayapy' > executable. > > if you open a new shell and type the following, it should start a > mayapy session: > > /usr/bin/env mayapy > > Let me know if that does not work. Also, I just realized that there > is a much simpler way to do this. replace the first line of ipymel > with the following > > #!$MAYA_LOCATION/bin/mayapy > > and just to make sure we're clear, to launch ipymel -- once its setup > properly -- all you need to do is type: > > ipymel > > -chad --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/python_inside_maya -~----------~----~----~----~------~----~------~--~---
