Re: Impending silent breakage of pip / macOS likely to cause severe confusion

On 04/09/2018 02:43 PM, Donald Stufft wrote: > >> On Apr 6, 2018, at 5:06 PM, Matthew Brett wrote: >> >> OK - so our hard deadline is the planned Warehouse launch on April >> 16th? I would argue for going straight to the SSL error at that >> point, and turning off the

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

On Mon, Apr 9, 2018 at 11:28 AM Donald Stufft wrote: > > > On Apr 9, 2018, at 1:33 PM, Erik Bray wrote: > > > > On Fri, Apr 6, 2018 at 11:36 PM, Chris Jerdonek > > wrote: > >> > >> On Fri, Apr 6, 2018 at 11:21 AM Donald Stufft

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

> On Apr 6, 2018, at 5:06 PM, Matthew Brett wrote: > > OK - so our hard deadline is the planned Warehouse launch on April > 16th? I would argue for going straight to the SSL error at that > point, and turning off the current brownout and April 8th TLS 1.0 shut > down.

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

On Fri, Apr 6, 2018 at 11:21 AM Donald Stufft wrote: > No, there’s not. pip makes HTTP requests and there’s no place for extra > metadata attached those requests except in the HTTP status code (which as > you noted, pip swallows by default because historically we didn’t know if

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

On Fri, Apr 6, 2018 at 9:55 PM, Donald Stufft wrote: > >> On Apr 6, 2018, at 4:28 PM, Matthew Brett wrote: >> >> >> Ouch - it does look like we're in a very difficult situation, which >> might apply to a significant number of users. >> >> I think the

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

> On Apr 6, 2018, at 4:28 PM, Matthew Brett wrote: > > > Ouch - it does look like we're in a very difficult situation, which > might apply to a significant number of users. > > I think the worst option is what we have ramping up in the brownout, > which is the silent

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

Hi again, On Fri, Apr 6, 2018 at 7:21 PM, Donald Stufft wrote: > > > On Apr 6, 2018, at 12:30 PM, Matthew Brett wrote: > > Hi, > > On Fri, Apr 6, 2018 at 4:49 PM, Donald Stufft wrote: > > > On Apr 6, 2018, at 11:25 AM, Matthew Brett

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

> On Apr 6, 2018, at 12:30 PM, Matthew Brett wrote: > > Hi, > > On Fri, Apr 6, 2018 at 4:49 PM, Donald Stufft > wrote: >> >> On Apr 6, 2018, at 11:25 AM, Matthew Brett wrote: >> >> >> As of 8th

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

Hi, On Fri, Apr 6, 2018 at 4:49 PM, Donald Stufft wrote: > > On Apr 6, 2018, at 11:25 AM, Matthew Brett wrote: > > > As of 8th April, pip will break, largely in silence. As used with > default command line options, pip will stop seeing anything on

Re: Impending silent breakage of pip / macOS likely to cause severe confusion

> On Apr 6, 2018, at 11:25 AM, Matthew Brett wrote: > > > As of 8th April, pip will break, largely in silence. As used with > default command line options, pip will stop seeing anything on pypi. > It will tell the user that it can't find packages that do exist on >

Impending silent breakage of pip / macOS likely to cause severe confusion

Hi, Please do let me know if this is not the right place to discuss this, but I think we're about to cause a storm of user distress on macOS, and I am wondering if there is anything we can do to reduce it. The situation for users of macOS < 10.13 is the following: Until recently, pip, used with