➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author chris.jerdonek
Recipients chris.jerdonek, evan.jones@bluecore.com, ned.deily, ronaldoussoren
Date 2016-08-23.08:53:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471942396.85.0.70855954199.issue27126@psf.upfronthosting.co.za>
In-reply-to
Content 
> We can't solve that problem; only Apple can;

> So, if we don't change _scproxy or urllib*'s use of it, only Apple can fix the problem.

In the Django ticket I mentioned in my comment above, one of the commenters said, "Just ran the tests at the mentioned commit on my macOS Sierra public beta with a fresh 3.5.2 python environment. No problems there."

(https://code.djangoproject.com/ticket/27086#comment:4 )

In other words, the issue that affected me on Mac OS X El Capitan (whose root cause is this issue I believe) wasn't present in Sierra.

Do you think this means Apple has addressed the issue in the next version of its OS?
History
Date User Action Args
2016-08-23 08:53:16chris.jerdoneksetrecipients: + chris.jerdonek, ronaldoussoren, ned.deily, evan.jones@bluecore.com
2016-08-23 08:53:16chris.jerdoneksetmessageid: <1471942396.85.0.70855954199.issue27126@psf.upfronthosting.co.za>
2016-08-23 08:53:16chris.jerdoneklinkissue27126 messages
2016-08-23 08:53:16chris.jerdonekcreate