Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
One of my Python scripts runs in interactive mode but fails when run from the command line. The difference is that when run from the command line, it imports modules from a bad .egg file, and when run interactively it uses my fixed (unzipped) version in the current directory.
My question is two-fold: a) why does Python load modules differently when run from these locations, and b) what are my options to work around it?
I don’t understand what do you mean by running script in interactive mode, so I can’t say exactly. But the first place to look for modules (
sys.path[0]) in interactive mode is current directory (even callingos.chdir()will affect imports), while for script it’s directory where the script is located (derived fromsys.argv[0]). Note that they are effectively the same when script is run from directory where it’s located, but could be different in other cases. Hope this helps.