On 24 August 2017 at 08:20, Neil Girdhar wrote:
> On Wed, Aug 23, 2017 at 3:31 AM Nick Coghlan wrote:
>> However, PEP 550's execution contexts may provide a way to track the
>> test state reliably that's independent of being a method on a test
>> case instance, in which case it would become feasi
On 24 August 2017 at 05:04, John Torakis wrote:
> Dark times...
>
> So is it a "case closed", or is there any improvement that will make it
> worth it to be an stdlib module?
Not really, as even aside from the security concerns, there are simply
too many ways that it can fail that are outside of
Makes sense. Thanks!
On Thu, Aug 24, 2017 at 5:20 AM Nick Coghlan wrote:
> On 24 August 2017 at 08:20, Neil Girdhar wrote:
> > On Wed, Aug 23, 2017 at 3:31 AM Nick Coghlan wrote:
> >> However, PEP 550's execution contexts may provide a way to track the
> >> test state reliably that's independe
Jim J. Jewett wrote:
> I know I'm not the only one who is confused by at least some of the
> alternative terminology choices. I suspect I'm not the only one who
> sometimes missed part of the argument because I was distracted
> figuring out what the objects were, and forgot to verify what was
> be
On Thu, Aug 24, 2017 at 10:04:58AM -0400, Barry Warsaw wrote:
> Jim J. Jewett wrote:
> > I know I'm not the only one who is confused by at least some of the
> > alternative terminology choices. I suspect I'm not the only one who
> > sometimes missed part of the argument because I was distracted
>
So (wearing my maintainer hat for unittest) - very happy to consider
proposals and patches; I'd very much like to fix some structural APIs
in unittest, but I don't have the bandwidth to do so myself at this
point. And what you're asking about is largely a structural issue
because of the interaction
