-
Notifications
You must be signed in to change notification settings - Fork 74
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
Can I use SwampDragon in Production #168
Comments
That's kind of an impossible question to answer. Could you be more specific? |
I wanted clarity specifically regarding these -
I have read your reply to Issue #161 and that was helpful. I just wanted to ensure that the new version should be adaptable with minimal overhead and the current version is stable for production with Django 1.7 and Django 1.8 |
The plan is to try to keep the changes under the hood, so implementation vise there should be as few changes as possible. If changes will be required before upgrading they should (ideally) be minimal. |
That would be good :) I understand removing dependency and bringing support for other python frameworks will take time. Till then can I use this with Django 1.7 and Django 1.8 ? |
Yes it shouldn't be an issue using it with Django 1.7 or 1.8 (if you run into any issues you should be able to install it from Github, latest master) |
Yeah that's possible. Thanks @jonashagstedt ! All the best! Hope to see the new SwampDragon in few months :) |
Any updates regarding issue #135 ? Feeling Stuck |
Hi, Is it safe to use the existing SwampDragon in production. I am aware of the fact that its dependent on tornado-redis which is no longer maintained and @jonashagstedt is working on removing this as well as django's dependency.
The text was updated successfully, but these errors were encountered: