[Django] #35907: python manage.py runserver exits with ‘Watching for file changes with StatReloader Performing system checks’

[Django]

#35907: python manage.py runserver exits with ‘Watching for file changes with
StatReloader Performing system checks’
-------------------------------------+-------------------------------------
Reporter: maricafumagalli | Type: Bug
Status: new | Component:
| Uncategorized
Version: 5.1 | Severity: Normal
Keywords: Watching for file | Triage Stage:
changes with StatReloader | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Hello,
I have a django app on Windows 10 (django 5.0 and python 3.10).
I installed Anaconda to create the specific environment, I managed to
install all required libraries and I copied the related db on my computer.
When I run "python manage.py runserver" or "python manage.py runserver
localhost:8080", it returns this message and quit without giving me error:
''Watching for file changes with StatReloader
Performing system checks...''

If I run "python manage.py check" it doesn't return any error.
I tried also "python manage.py runserver --noreload" but it exited again.
I tried to uninstall and reinstall Anaconda.
I made the same installation on Linux and everything works fine.
Can you help me?
--
Ticket URL: <https://code.djangoproject.com/ticket/35907>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#35907: python manage.py runserver exits with ‘Watching for file changes with
StatReloader Performing system checks’
-------------------------------------+-------------------------------------

Reporter: Marica Fumagalli | Owner: (none)
Type: Bug | Status: closed
Component: Uncategorized | Version: 5.1
Severity: Normal | Resolution: invalid

Keywords: Watching for file | Triage Stage:
changes with StatReloader | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Tim Graham):

* resolution: => invalid
* status: new => closed

Comment:

This ticket tracker is used to report bugs in Django. See
TicketClosingReasons/UseSupportChannels for ways to get help with usage
problems. However, I'm not sure you've provided enough information for
someone to determine what's wrong. Maybe if you do a web search, you'd
find someone else who encountered the same issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/35907#comment:1>

[Django]

#35907: python manage.py runserver exits with ‘Watching for file changes with
StatReloader Performing system checks’
-------------------------------------+-------------------------------------
Reporter: Marica Fumagalli | Owner: (none)
Type: Bug | Status: closed
Component: Uncategorized | Version: 5.1
Severity: Normal | Resolution: invalid
Keywords: Watching for file | Triage Stage:
changes with StatReloader | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Marica Fumagalli):

Why did you close it? I have searched a lot on the web but I can't find
any solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/35907#comment:2>

[Django]

#35907: python manage.py runserver exits with ‘Watching for file changes with
StatReloader Performing system checks’
-------------------------------------+-------------------------------------
Reporter: Marica Fumagalli | Owner: (none)
Type: Bug | Status: closed
Component: Uncategorized | Version: 5.1
Severity: Normal | Resolution: invalid
Keywords: Watching for file | Triage Stage:
changes with StatReloader | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Tim Graham):

This isn't a confirmed bug in Django, and we have no way to reproduce the
issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/35907#comment:3>