1.) It seems PyPI updated their SSL config and the certs can't be verified by the version of pip included with 3.5. I've implemented a workaround to explicitly trust the necessary domains, only for 3.5 and only when installing Python. I thought about just pulling 3.5 instead, but I think we can wait until the next time something breaks. We're at 1173 downloads for 3.5 from PyPI in the last 6 months, 74 in the last 30 days (likely accelerated by this issue)
2.) Pylint recently introduced possibly-used-before-assignment, which mostly flagged cases where we import a library like termios that doesn't exist on Windows. All the cases are guarded, but not always directly, so Pylint can't figure it out. Mostly I just disabled these in-line.
This fixes two issues causing the tests to fail:
1.) It seems PyPI updated their SSL config and the certs can't be verified by the version of pip included with 3.5. I've implemented a workaround to explicitly trust the necessary domains, only for 3.5 and only when installing Python. I thought about just pulling 3.5 instead, but I think we can wait until the next time something breaks. We're at 1173 downloads for 3.5 from PyPI in the last 6 months, 74 in the last 30 days (likely accelerated by this issue)
2.) Pylint recently introduced
possibly-used-before-assignment, which mostly flagged cases where we import a library like termios that doesn't exist on Windows. All the cases are guarded, but not always directly, so Pylint can't figure it out. Mostly I just disabled these in-line.