I’m not familiar with Docker, but I did have to add the path to Python 3.6 DLLs
in my WSGI configuration in my Apache configuration file.
WSGIPythonPath ${project_path};${virtualenv};C:/Python36/DLLs;
From: [email protected] [mailto:[email protected]] On
Behalf Of PASCUAL Eric
Sent: Wednesday, February 14, 2018 8:52 AM
To: Django users
Subject: Re: AttributeError: 'module' object has no attribute 'lru_cache' with
python 3.6.4 and Django 2.0.2
Hi,
Normally you shouldn't have to add site-packages in the PYTHONPATH since it is
supposed to be already. If not, packages installed via "sudo pip install" would
not be found.
I've packaged a lot of applications in Docker containers, and never had to
modify PYTHONPATH.
Your problem is maybe be lurking elsewhere than PYTHONPATH, and this change has
just created a new one which is hiding the original one, but not solving it at
all.
Best
Eric
________________________________
From: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> on behalf
of Greng Fortezza <[email protected]<mailto:[email protected]>>
Sent: Wednesday, February 14, 2018 3:02:28 PM
To: Django users
Subject: AttributeError: 'module' object has no attribute 'lru_cache' with
python 3.6.4 and Django 2.0.2
Hi,
I'm trying to set up the following configuration in Docker
python: 3.6.4
Django: 2.0.2
Apache/2.4.10 (Debian)
First, I was getting the error
ImportError: No module named django.core.wsgi
Then I added Django to PYTHONPATH
export PYTHONPATH="/usr/local/lib/python3.6/site-packages"
the previous problem has gone away but now there is another one
AttributeError: 'module' object has no attribute 'lru_cache'
Apache configs contains the following line
WSGIScriptAlias / /www/settings/wsgi.py
where /www/settings/wsgi.py is actual path to wsgi.py file.
What could be wrong?
Thanks,
Greng
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
[email protected]<mailto:[email protected]>.
To post to this group, send email to
[email protected]<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/02803efb-92a9-4958-9a52-f77bee7de89b%40googlegroups.com<https://groups.google.com/d/msgid/django-users/02803efb-92a9-4958-9a52-f77bee7de89b%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
[email protected]<mailto:[email protected]>.
To post to this group, send email to
[email protected]<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/AM5P193MB008328E4760DBF0DA724D2238CF50%40AM5P193MB0083.EURP193.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/django-users/AM5P193MB008328E4760DBF0DA724D2238CF50%40AM5P193MB0083.EURP193.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/f0cabae1fd6544528668a9494f6dfe03%40ISS1.ISS.LOCAL.
For more options, visit https://groups.google.com/d/optout.
