Outdated version of cryptography?
zefoo opened this issue · 5 comments
I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:
Howdy. I'm migrating off flask-ask ... I think this is the answer. However, cryptography 2.9.2 is used. Whereas we previously had cryptography 36.0.1. That's a huge discrepancy. Is there a reason for this? I'm not sure what to do here.
Expected Behavior
I'm expecting a modern, up-to-date package that uses the latest packages... but this seems very outdated. Perhaps my expectations are too high from an official Amazon repo.
Possible Solution
Supporting a more modern version of cryptography?
Steps to Reproduce (for bugs)
Python 3.10.2, brand new virtualenv, I install `flask-ask-sdk` and it installs. cryptography-2.9.2. Latest is 36.0.1... https://github.com/pyca/cryptography
Context
I was trying to get off flask-ask because it's outdated and old. But I'm not sure if this is better.
Your Environment
- ASK SDK for Python used: 3.10.2
- Operating System and version: Ubuntu 18.04
Thank you thank you!
Hitting the same issue also.
I'm surprised an official library is so outdated... perhaps priorities lie elsewhere or the focus is to get people on Lambda?
In either case, FWIW, I solved this by siloing our Alexa skill in its own environment and talking to our primary systems via an API we built... solved it in a few hours. Happy about it. I actually left things in Flask-Ask because I was able to do that (we built the skill there)... I'd still like to use this library, though, to take advantage of a few other things (namely, the Alexa device notifications)
I'm surprised an official library is so outdated... perhaps priorities lie elsewhere or the focus is to get people on Lambda?
In either case, FWIW, I solved this by siloing our Alexa skill in its own environment and talking to our primary systems via an API we built... solved it in a few hours. Happy about it. I actually left things in Flask-Ask because I was able to do that (we built the skill there)... I'd still like to use this library, though, to take advantage of a few other things (namely, the Alexa device notifications)
Thanks and I agree! Specifically, the use case for me is that I would really like to integrate this into our Django application, but the Twilio module requires a newer version of the Cryptology module, and the ask-sdk requires an older version. I have also solved it for now by deploying an independent skill to Lambda, but as you mentioned, I would prefer this to be deeply integration with our Django platform to take advantage of the many other features. Hopefully it can be updated soon!
seems like this is already fixed
fa0cbe0
however it doesn't seem to have been released to PyPi. Looking into releasing the package
released the fix mentioned above