On Thursday, August 16, 2012 12:24:34 AM UTC-4, Matt wrote: > > On Wed, Aug 15, 2012 at 10:03 PM, Anthony <abasta...@gmail.com> wrote: > >> Is there any way around this? This seems to have broken only with the > >> upgrade to Mountain Lion. We develop this app primarily on (and for) > linux, > >> however I do most of my development on my laptop, so it's quite > inconvenient > >> to have to use a separate install just on this computer. Do you have > any > >> idea where to look in order to solve this problem? I am very willing > (and > >> motivated!) to help fix this problem. > > > > > > What are you trying to work around? If you want to use the Python > installed > > on your system along with any modules you may have installed with it, > then > > just run the source version of web2py -- it works fine on OS X and is > just > > as easy to install (just download and unzip). What do you mean by "a > > separate install just on this computer" -- you'll need web2py installed > on > > any computer on which you want to use it? > > > > I might be experiencing a different problem here. I'm currently having > a problem where I can no longer import modules from the "modules" > directory in my application on osx. I've updated to the latest 1.99.7 > to no avail, and am currently trying to work through why it's no > longer loading properly (this worked just fine in 1.99.4, but as I > said I also upgraded to Mountain Lion this past weekend). > > I fixed this problem by just using local_import. I was under the impression this method was deprecated and I should just be able to use "import" directly. Hope this helps someone
> > Anthony > > > > -- > > > > > > > --
