autoreload lines filling Debug console of django app

I must have switch some setting because I am getting thousands of lines (3303 last time)  that look like this when I open the debug console.  This AFTER the normal "Quit the server with CONTROL-C." prompt.

For example, 

 

DEBUG 2019-06-07 09:47:15,927 autoreload Watching dir /Users/phoebe/venv/skorie3/lib/python3.6/site-packages/import_export/locale with glob **/*.mo.
DEBUG 2019-06-07 09:47:15,939 autoreload Watching dir /Users/phoebe/venv/skorie3/lib/python3.6/site-packages/imagekit/locale with glob **/*.mo.
DEBUG 2019-06-07 09:47:15,945 autoreload Watching dir /Users/phoebe/venv/skorie3/lib/python3.6/site-packages/django_social_share/locale with glob **/*.mo.
DEBUG 2019-06-07 09:47:15,953 autoreload Watching dir /Users/phoebe/Development/skorie/obstacles/locale with glob **/*.mo.
System check identified no issues (0 silenced).
June 07, 2019 - 09:47:18
Django version 2.2.2, using settings 'config.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
DEBUG 2019-06-07 09:47:18,990 autoreload File /Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/lib-dynload/_decimal.cpython-36m-darwin.so first seen with mtime 1545635091.0
DEBUG 2019-06-07 09:47:18,996 autoreload File /Users/phoebe/venv/skorie3/lib/python3.6/site-packages/tablib/packages/__init__.py first seen with mtime 1559667881.475002
DEBUG 2019-06-07 09:47:18,996 autoreload File /Users/phoebe/venv/skorie3/lib/python3.6/site-packages/reportlab/pdfbase/ttfonts.py first seen with mtime 1559667875.595854
DEBUG 2019-06-07 09:47:18,996 autoreload File /Users/phoebe/venv/skorie3/lib/python3.6/site-packages/stripe/api_resources/sku.py first seen with mtime 1559667881.135201

....

I havn't change the LOGGING setting and it is just one project, so must be something I have done.  

Is there a setting I changed?

 

 

 

 

 

2 comments
Comment actions Permalink

Please check if you have `PYCHARM_DEBUG = True` environment variable in your run/debug configuration (or any other suspicious env variables).

If no, try to run your Django server outside of IDE, from the system terminal, to determine if the issue is IDE-related.

0
Comment actions Permalink

You would be correct in suspecting this is a django issue.  If I do runserver from the command line I get the same issue.

It is related to the environmental variable DJANGO_AUTORELOAD_ENV, but this is set in djangos autoreload.py so can't be overridden (as far as I can see).  Downgrading to 2.2.1 from 2.2.2 made no difference but going down to 2.2 removed the logging.  Did the same test on another project in Pycharm and found the same pattern.  Excessive logging in v. 2.2.1 and 2.2.2.

Will investigate further on django site.  Thanks for your help.

0

Please sign in to leave a comment.