-
Notifications
You must be signed in to change notification settings - Fork 244
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
Would this be compatible with Django 3? #120
Comments
@stephenmcd Good question. This projects does not look healthy. Please tell us the truth about the state of the project. It is 100% ok if you have no time. Please talk about this, this helps to find a simple solution. |
I have the same question also |
The real question is: why was this project abandoned? @stephenmcd There are a lot of people who would like this repository, not everyone has the time to implement socket.io in django, especially if it's a small project. |
also django channels sucks and nodejs socketio is good. if we can get the same socket io in django that would be gold! |
It's sad to see this repository go; this seems like the perfect websocket implementation out there since Django channels is confusing and hard to use. However, I found an alternative called Python-EngineIO. It's not as good as this repo, but it's the easiest solution out there. |
@thomcatmeow can we maybe somehow maintain it and bring in more developers? if we can contribute we can keep it and all and more can use it |
@nh916 Yes that would be even better than finding an alternative. With more developers, we can keep this amazing repository working for everyone. |
I think it is better to move to django channel. |
Hi I am wondering if this would be compatible with Django 3?
The text was updated successfully, but these errors were encountered: