I started using mod_proxy and everything is ok.

On Sep 24, 10:58 am, Necati Demir <[email protected]> wrote:
> I started to see error messages again. So it is not about 1.94.
>
> On Sep 24, 10:26 am, Necati Demir <[email protected]> wrote:
>
>
>
>
>
>
>
> > No. But I realized that I was using 1.94 and now switched to 1.99. I
> > will use 1.99 and see if there is a problem. Was there a problem like
> > that in 1.94?
>
> > On Sep 23, 11:44 pm, Massimo Di Pierro <[email protected]>
> > wrote:
>
> > > Do you touch sys.path in your code?
>
> > > On Sep 23, 3:21 pm, Necati Demir <[email protected]> wrote:
>
> > > > I say "randomly" because
>
> > > > When i refresh page, it works. And another refresh; it gives error:
> > > > ImportError: No module named testapp.modules.mymodule
> > > > With another page refresh it works bu if your unlucky it gives error
> > > > again.
>
> > > > I did not found any patterns.
> > > > But I noticed something; when it starts to give errors, I restart
> > > > apache* and I do not get errors for some time (say 1 hour).
>
> > > > * I use apache+mod_wsgi
>
> > > > On Sep 23, 5:08 pm, Massimo Di Pierro <[email protected]>
> > > > wrote:
>
> > > > > True it is deprecated but still, it should work. What do you me
> > > > > "randomly does not work". Is this for a specific module or app?
>
> > > > > On Sep 23, 8:50 am, Anthony <[email protected]> wrote:
>
> > > > > > As of version 1.96.1, local_import() has been deprecated. You 
> > > > > > should be able
> > > > > > to do:
>
> > > > > > import mymodule
>
> > > > > > and it will look in your application's /modules folder before 
> > > > > > checking
> > > > > > sys.path.
> > > > > > Anthony
>
> > > > > > On Friday, September 23, 2011 3:11:08 AM UTC-4, Necati Demir wrote:
>
> > > > > > > Hello,
>
> > > > > > > local_import function randomly does not import my modules from 
> > > > > > > modules
> > > > > > > directory.
> > > > > > > I have this problem when i use web2py with apache (with wsgi).
>
> > > > > > > Any suggestion?

Reply via email to