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 db3l
Recipients db3l, jeremy.kloth, jkloth, miss-islington, pablogsal, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-12-10.23:47:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544485644.22.0.788709270274.issue35433@psf.upfronthosting.co.za>
In-reply-to
Content
Oh, since my reading comprehension must be low today, it appears like Jeremy actually had a closer situation previously as I'm in now, with a later (not older) version of the SDK that wasn't in the list.

Which is interesting, since he got an error about the SDK whereas my workers weren't having an issue at that point.

But I guess it still comes down to what to do if the hardcoded list doesn't match what's on the system, but the SDK on the system will actually work.  Complain or let the default get used anyway?
History
Date User Action Args
2018-12-10 23:47:24db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, jkloth, jeremy.kloth, zach.ware, steve.dower, pablogsal, miss-islington
2018-12-10 23:47:24db3lsetmessageid: <1544485644.22.0.788709270274.issue35433@psf.upfronthosting.co.za>
2018-12-10 23:47:24db3llinkissue35433 messages
2018-12-10 23:47:24db3lcreate