-
Notifications
You must be signed in to change notification settings - Fork 164
Project Status? #85
Comments
@davidhariri Hi! This project is no longer maintained - the only reason I hadn't archived it already was in the hope that someone would fork it, and I could advertise that fork here before archiving (once archived no-one can comment). See: |
I might be interested in forking it. I have to think on the level of commitment. Would that re-link pypi or would I publish my own package separately? |
For security/least surprise reasons, I think it would be best to start a new package on PyPI. However, I can link to it and the repo from messaging in this repo before I archive it. |
I'm archiving this repo now - if someone ends up creating a fork that is actively maintained, at-mention me on an issue in the fork asking for a link to be added to this repo to the new repo, and I can make the edits then :-) |
For anyone looking for a replacement, I would check out this alternative :-) |
I noticed that the last commit is from May 2017 and that the description includes [DEPRECATED]. @edmorley is this project still being maintained? If not, is there an up to date fork? Or should we just use
WebSocket
more directly as described here. Thank you!The text was updated successfully, but these errors were encountered: