.... >> >> I've added the web2py.py path to sys.path using sys.path.append and >> verified using print sys.path > > Again - this would have an effect if you wrote a script that did > "import web2py" - but since web2py isn't a module (rather an > application) this is of little use. >
sorry - this is wrong (I was thinking ahead too fast); what sys.path does is the same thing as setting your windows PATH environment, but modifying only the current processes' copy of the execution environment (e.g. it is lost after that process exits). So if you type "set" in a windows command (or "env" in unix/linux) you will see your sys environment variables; same for inside a running pythong script - if you import sys, then the python interface for that environment is as you show, and you can extend / modify it in your running process. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
