This is relevant only for those who run web2py server (from compiled distributions) under windows. It's impossible to import modules residing on network share specified by UNC path notation (for examlpe \\server\web2py), even if they reside in the same folder tree as the server itself. The reason for that is incomplete support for UNC notations in python, therefore one possible solution is to map the network share to drive letter, and make sure that the server and the modules are accessed throught the regular windows path notation using drive letter (for example, Y:\web2py). This issue won't manifest itself when running server from source, because CMD doesn't allow to invoke python from the UNC path. I hope this will spare you a few moments of frustration. I've spent several hours trying to figure what's exactly is wrong with my module.
-- 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.
