-
Notifications
You must be signed in to change notification settings - Fork 31
Refresh the development enviroment, care about missed "verify_ssl_cert=True" and stabilize/fix doctests in "https.txt" #397
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
Conversation
b353753 to
fbdfa0a
Compare
fbdfa0a to
757e950
Compare
c602082 to
4b6a70b
Compare
4b6a70b to
1081140
Compare
bf11e61 to
12c1b3e
Compare
|
It's a bit hard to review as this PR does several things. Any chance to break this up into multiple smaller ones? |
I can do it. But I will probably not be able to make CI succeed on individual chunks because currently, it is broken due to both the environment being outdated because of issues with |
fa670d0 to
700157d
Compare
|
Hi @mfussenegger and @seut, I removed some of the commits here in order to boil the patch down to the minimum required things to make CI succeed again. The other improvements have been submitted on behalf of #401 and #402. With kind regards, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good otherwise.
DEVELOP.rst
Outdated
| python3 -m venv .venv | ||
| source .venv/bin/activate | ||
|
|
||
| # Workaround for Python 3.9 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| # Workaround for Python 3.9 | |
| # Workaround for Python 3.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for spotting this.
When using Python 3.9, setting up the development environment croaked. Because "bootstrap.py" was a workaround in pre-pip times, this patch completely gets rid of it. At the same time, it modernizes some more dependency definitions and improves the developer guide.
Recently, this has been made a default on the CrateDB connection object, but apparently it has been missed to also flip the switch on this end. Also, adjust the respective doctests accordingly.
700157d to
9d309e1
Compare
Hi there,
when using Python 3.9, setting up the development environment croaked. Because
bootstrap.pywas a workaround in pre-piptimes [1], and to modernize this repository, this patch completely gets rid of it. On the other hand, it pins to appropriate package versions to still be compatible with Python 3.5 through Python 3.9, where the former setup didn't satisfy these requirements anymore.Along the lines, the patch fixes the doctests in
https.txtin order to improve the situation with #375. For doing this appropriately, it takes care about a missedverify_ssl_cert=Truesetting on the HTTP client as a followup to #385.We need this to be able to run #400 successfully on CI.
With kind regards,
Andreas.
[1] https://community.plone.org/t/not-using-bootstrap-py-as-default/620