[issue24273] _scproxy.so causes EXC_BAD_ACCESS (SIGSEGV)

2015-05-24 Thread Jacob
Jacob added the comment: Thanks! That does work. I'm concerned there may be unintended or undesired consequences of this. Hope the bug gets fixed, but will use the workaround for now. -- ___ Python tracker rep...@bugs.python.org

[issue24273] _scproxy.so causes EXC_BAD_ACCESS (SIGSEGV)

2015-05-24 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- resolution: - duplicate stage: - resolved status: open - closed superseder: - exception error in _scproxy.so ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24273

[issue24273] _scproxy.so causes EXC_BAD_ACCESS (SIGSEGV)

2015-05-23 Thread Jacob
New submission from Jacob: This looks very related to: http://bugs.python.org/issue13829 I have very simple test code that looks like this: import requests r = requests.get('http://www.google.com') print('requests.get() succeeded') The above code works fine. However, when:

[issue24273] _scproxy.so causes EXC_BAD_ACCESS (SIGSEGV)

2015-05-23 Thread Ned Deily
Ned Deily added the comment: One workaround should be to disable network proxy lookups by defining the environment variable 'no_proxy' with value '*' in the Python process, for example: env no_proxy='*' python3.4 ... -- ___ Python tracker