Used libapache2-mod-wsgi-py3 instead of python 2 version
On Wednesday, 15 December 2021 at 10:03:27 UTC Kyle Paterson wrote:
> I am not using either of those, I think. The only place I explicitly load
> settings is in wsgi.py, with the line:
> os.environ[‘DJANGO_SETTINGS_MODULE’] = ‘travel data.
I am not using either of those, I think. The only place I explicitly load
settings is in wsgi.py, with the line:
os.environ[‘DJANGO_SETTINGS_MODULE’] = ‘travel data.settings'
On Thu, 9 Dec 2021 at 12:52, Jason wrote:
>
> with your settings usage, are you defining a property in settings and
> try
with your settings usage, are you defining a property in settings and
trying to use it anywhere?
furthermore, are you using settings via
from traveldata.traveldata import settings (example)
or via
from django.conf import settings
The latter is the recommended means because settings are lazy
Hi,
I think this is not related with apache
It seems like class object property is called as a method somehow.
Unfortunately the error does not reveal the property name.
Regards,
Sencer HAMARAT
On Wed, Dec 8, 2021 at 4:59 PM Kyle Paterson
wrote:
> Started a new project after not using Djang
Started a new project after not using Django for roughly two years, works
fine when running as a development server but throws TypeError:
SimpleLazyObject class: property object not callable.
>From apache error log:
[Wed Dec 08 10:11:53.023239 2021] [wsgi:error] [pid 10704:tid
140343150348032]
5 matches
Mail list logo