Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

python manage.py runserver not working #508

Closed
IMOWWW opened this issue Apr 10, 2024 · 5 comments
Closed

python manage.py runserver not working #508

IMOWWW opened this issue Apr 10, 2024 · 5 comments

Comments

@IMOWWW
Copy link

IMOWWW commented Apr 10, 2024

I have everything set up correctly, but the project does not run as async

System check identified no issues (0 silenced).
April 10, 2024 - 18:56:40
Django version 4.2.8, using settings 'ChatProject.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

@IMOWWW
Copy link
Author

IMOWWW commented Apr 10, 2024

I solved this problem by changing the version from daphne==4.1.1 to daphne==4.0.0

@IMOWWW IMOWWW closed this as completed Apr 10, 2024
@carltongibson
Copy link
Member

OK, this works for me with 4.1.0, but not 4.1.1.

Let's reopen: it's not fixed by you reverting to an earlier version.

@carltongibson carltongibson reopened this Apr 10, 2024
1One0 added a commit to 1One0/daphne that referenced this issue Apr 11, 2024
@1One0
Copy link

1One0 commented Apr 11, 2024

I met the same problem when i update daphne version, 4.1.1 package missing management/commands/runserver.py so runserver wont work with daphne.

@carltongibson
Copy link
Member

@1One0 Thanks for confirming.

4.1.1 fixed one packaging issue in 4.1.0, only to introduce another. (Never change the packaging 🤦)

Fix coming later today.

@joseseb91
Copy link

would be helpful if it was mentioned in changelog of 4.1.2 that runserver doesnt work with daphne 4.1.1, spent two days rewriting django channels setup to figure out why websockets were not working,

was working with docker base images and my dev server build from last week was using 4.1.1 😢
our staging server base img had 4.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants