From: "Mr. Daniel Browne" <dbrowne@(email surpressed)>
Subject: Re: CentOS 6 Python error
   Date: Tue, 12 Mar 2013 15:50:07 -0400
Msg# 2296
View Complete Thread (19 articles) | All Threads
Last Next
I just came across an article relating to this issue on the autodesk site (from a google search).

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=13375416&linkID=9242258

However, though it finds the os module, it now cannot find the time module which theoretically should be in the same path. Here are my exports I prepended to the rest of the os.system() call in Maya:

export PYTHONHOME=/usr/;export PYTHONPATH="/usr/lib64/python2.6/:$PYTHONPATH"


On Mar 11, 2013, at 10:38 PM, Greg Ercolano wrote:

[posted to rush.general]

On 03/11/13 20:30, Mr. Daniel Browne wrote:
> [posted to rush.general]
> 
> I've opened a ticket with autodesk; I could swear I hadn't encountered =
> this issue before.
> 
> The Rush window will show when I set PYTHONHOME to =
> /usr/autodesk/maya2013-x64, but I get the error again when I press the =
> submit button.

	Great.

	BTW, I'm assuming if you try running that hello script (or for that matter
	the rush submit script) from /OUTSIDE/ maya, it works normally.. and that
	it's only /inside/ maya it doesn't work (as per the original post).

	With autodesk, focus on just trying to get the simple hello program
	to work without erroring out on the "import os,sys" line. Once you fix
	that, the rush stuff should work too.

	The hello example is a good way of replicating the problem for Autodesk
	support without involving any of the rush stuff.

	That 'import os' line should not be failing with that error you sent me,

ImportError: No module named os

	..as /that/ is a big problem for any python script.

	My guess is something changed in the environment that is preventing
	maya's python from finding the 'import os' module. Probably something
	in a customized maya startup file (MEL or python) that is changing
	the PATH or PYTHONPATH in such a way that maya's internal version of
	python can no longer find its own 'import os' module.

	It might even be other seemingly unrelated variables like
	LD_LIBRARY_PATH, or some such. Or perhaps even a file system problem,
	or problem with the linux upgrade scripts that might have messed up
	Maya's own version of python. (Though if it did that, I'd think Maya
	wouldn't open up at all, as I'm sure it probably uses the os module
	itself heavily)


-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/

Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)


----------
Dan "Doc" Browne
System Administrator
Evil Eye Pictures

dbrowne@(email surpressed)
Office: (415) 777-0666 x105


Last Next