-
Notifications
You must be signed in to change notification settings - Fork 108
Issues in _urllib2_fork.py under Python 3.12 and newer due to changes in HTTPSConnection #100
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
Comments
Mechanize hasnt used key_file in forever since python 3.5. If you are |
This is with mechanize 0.4.8 Traceback (most recent call last): |
Does not reproduce for me with current mechanize. Update. python -c 'import sys; from mechanize import Browser; print(sys.version); print(len(Browser().open("https://bing.com").read().decode()))' |
This is what I get with mechanize 0.4.10, which is what led me to trying 0.4.8 since it previously worked for me (under older Python): Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
This has nothing to do with mechanize, its python's ssl module failing |
I'm getting this error at the point I try to run a mechanize.Browser.open():
TypeError: HTTPSConnection.init() got an unexpected keyword argument 'key_file'
Error reporting I'm seeing around other packages/modules pointed me to changes with HTTPSConnection:
https://docs.python.org/3.12/library/http.client.html#http.client.HTTPSConnection
I was seeing other issues related to HTTPS under mechanize 0.4.10, but also seeing it under mechanize 0.4.8 which previously worked for my code under an earlier version of Python.
edit: apparently those parameters will deprecated in Python 3.6:
python/cpython#72209
The text was updated successfully, but these errors were encountered: