[issue17483] Can not tell urlopen not to check the hostname for https connections.
Alecz added the comment: Actually, because of issue 18543, urlopen will not use the custom opener if one was defined, instead, it will create a new opener with check_hostname = True. So it is impossible to skip hostname checking without overriding the urlopen method. I don't understand why can't we allow check_hostmane to be set to False in urlopen and also why we don't allow custom openers to be used by urlopen if specifying a ca*. Moreover this forced restriction is not documented. I had to go to the source code to figure out why it wasn't working. This issue being resolved makes it even more misleading. ------ nosy: +Alecz Added file: http://bugs.python.org/file36068/urlopen-explained.py ___ Python tracker <http://bugs.python.org/issue17483> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18543] urllib.parse.urlopen shouldn't ignore installed opener when called with any ca* argument
Alecz added the comment: I just want to point out that the documentation states that an opener can be used with urlopen: urllib.request.install_opener(opener) Install an OpenerDirector instance as the default global opener. Installing an opener is only necessary if you want urlopen to use that opener; Reference: https://docs.python.org/3/library/urllib.request.html?highlight=urllib.request#urllib.request.install_opener Issue 17483 was closed (rejected) because it was considered that a custom opener can be used when opening https links. -- nosy: +Alecz Added file: http://bugs.python.org/file36074/urlopen-explained.py ___ Python tracker <http://bugs.python.org/issue18543> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17483] Can not tell urlopen not to check the hostname for https connections.
Alecz added the comment: If this request was rejected shouldn't the Resolution be something such as "Rejected", "Not a Bug", or "Wont fix"? At the first glance, I believe it is very misleading to see this as fixed. I even installed the latest version and was surprised to see that "the fix" did not work as expected. -- ___ Python tracker <http://bugs.python.org/issue17483> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7936] sys.argv contains only scriptname
Alecz added the comment: I ran into this issue by doing the following steps, though I did not try to reproduce: 1 - install Python 3.4 2 - have windows Always Open .py files with Python 3 - install Python 2.7 Then I encountered issues where all .py scripts were opened with Python 2.7. After some unsuccessful attempts I decided to uninstall Python 2.7 4 - remove Python 2.7 At this point, I had to update the file associations because Windows could not find Python 2.7 anymore 5 - update file associations The issue is obviously that in at least a few places in the registry, the ..\shell\open\command has a value of ..\python.exe "%1" In my case it was under all roots: HKEY_CLASSES_ROOT\py_auto_file HKEY_LOCAL_MACHINE HKEY_USERS I corrected only the one under HKEY_USERS by adding %* and it resolved the issue. -- nosy: +Alecz versions: +Python 3.4 ___ Python tracker <http://bugs.python.org/issue7936> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
