Well, that would explain it. For directories the execute bit has to do
with directory traversal, rather than the execution of anything. No
adjustment to your wsgi config can get around that.
I can't advise you about mappings between windows permissions and *nix
permissions, not what sshclient
OK, I found a fix but not the cause.
The entire project is copied from W7 using sshclient. The directories I'm
having trouble with are not executable, when I changed that it all works.
Now I wonder if there is something in my wsgi.conf that could be changed to
all access to them since I don't
Re: Cannot import mypackage with code in the __init__.py file
On Wed, Jun 19, 2013 at 7:51 PM, fred <fred.se...@adventistcare.org> wrote:
> I'm upgrading to django 1.5.1 on CentOs 6.4 with python 2.6.6
> although I'm developing on a W7 with the django debug server.
>
> I am
On Wed, Jun 19, 2013 at 7:51 PM, fred wrote:
> I'm upgrading to django 1.5.1 on CentOs 6.4 with python 2.6.6 although I'm
> developing on a W7 with the django debug server.
>
> I am getting executing my view.py and most of the modules it uses. But in
> one
Thanks Bill, I've tried all but the __future__ option. I'll give it a try.
From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On
Behalf Of Bill Freeman
Sent: Wednesday, June 19, 2013 3:03 PM
To: django-users
Subject: Re: Cannot import mypackage with code in the __init__
a quick update, if I use >python manage.py shell everything works as I
would expect, no problems.
also I tried removing all code from my __init__.py (yes I'm grasping at
straws) and that did not help.
--
You received this message because you are subscribed to the Google Groups
"Django
Have you tried
import app.mypackage
or
from app import mypackage
Or, from within views.py or mymodule.py, if you have done
from __future__ import absolute_imports
then try
import .mypackage
(There is a period before "mypackage" on that line.)
On Wed, Jun 19, 2013 at 2:51 PM,
7 matches
Mail list logo