-
Notifications
You must be signed in to change notification settings - Fork 11
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 not launch after itsdangerous's new release #59
Comments
Thank you for your detailed bug report. I have replicated this issue and created a fix. This is solved in version '1.0.12'.
|
Hi again, Thanks for the very fast fix and reply. A short follow-up question: How long does it usually take before the updated version (1.0.12) is available through pip? All the best, |
It's usually updated quite soon after the pull request has been merged. Most likely tomorrow. Wilad |
Sounds great. Many thanks Wilad! Christoffer |
Hi again, I just tried it again, and even when the new Docnado 1.0.12 is being pulled during container build I see in the logs that it still pulls Flask 1.1.2 (instead of 1.1.4), which makes it fail. I found this line and wonder if this also needs to be manually updated: Line 29 in 8266929
I would make a PR, but since I am not sure about this I wanted to ask you here instead. Best regards, |
You're completley right. Thanks for your patience. I'll resolve this asap. |
New version 1.0.13 should have resolved this for you.
|
Glad to hear, and now it works perfectly. Thank you for your quick replies and fixes! Christoffer |
I'm running Docnado in a docker container, and as part of the building process I'm running
pip install docnado --upgrade && docnado --new
. However after itsdangerous's new release (released yesterday) this now results in the following error:If the issue is the same as pallets/itsdangerous#289 and pallets/itsdangerous#290 there seems to be an incompatibility with the Flask version used by Docnado. If so, could Flask be updated? That is if Flask actually is the issue here.
I haven't been able to test this with a native install (non-containerised) because my pip install of docnado fails. I don't think it's related, but I'm quite sure that native installs will have the same problem as described above.
Thank you for this great and easy to set up documentation tool!
Best regards,
Christoffer
The text was updated successfully, but these errors were encountered: