On Thu, Dec 19, 2013 at 3:16 PM, Roy Smith <r...@panix.com> wrote: > It's pretty common here to have people ask questions about how import > works. How altering sys.path effects import. Why is import not finding > my module? You quickly get into things like virtualenv, and now you've > got modules coming from your source tree, from your vitualenv, from your > system library. You need to understand all of that to make it all work.
Python might one day want to separate "system paths" from "local paths", to give the same effect as: #include <stdio.h> #include "local_config.h" where the current directory won't be searched for stdio.h. But other than that, it's exactly the same consideration in either Python or C. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
