-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Inconsistent requirements in Rasa 1.6.0 #5040
Labels
type:bug 🐛
Inconsistencies or issues which will cause an issue or problem for users or implementors.
Comments
staticdev
added
the
type:bug 🐛
Inconsistencies or issues which will cause an issue or problem for users or implementors.
label
Jan 5, 2020
Pull request #5041. |
Thanks for raising this issue, @JustinaPetr will get back to you about it soon✨ Please also check out the docs and the forum in case your issue was raised there too 🤗 |
@JustinaPetr I had a problem with my first fork but I recreated the pull request (#5071). Can you get a reviewer for that? Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
type:bug 🐛
Inconsistencies or issues which will cause an issue or problem for users or implementors.
Rasa version: 1.6.0
Rasa SDK version (if used & relevant):
Rasa X version (if used & relevant):
Python version: Python 3.7.5
Operating system (windows, osx, ...): Ubuntu 19.10
Issue: When I try to train my models I was getting a warning:
/usr/lib/python3/dist-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.7) or chardet (3.0.4) doesn't match a supported version!
I tried to solve that installing the newer version o requests 2.22.0 (which is in rasa's requirements.txt). When I do that I get:
ERROR: rasa 1.6.0 has requirement networkx~=2.3.0, but you'll have networkx 2.4 which is incompatible.
. That is odd, since rasa needs requests 2.22.0 which needs networkx 2.4. I think a quickfix would be just upgrading the requirements.txt from rasa to networkx 2.4.Logs:
The text was updated successfully, but these errors were encountered: