[TIP] Does anyone *need* mock update from cPython in Python 2.6?
graffatcolmingov at gmail.com
Wed Jul 8 04:35:13 PDT 2015
On Jul 8, 2015 6:33 AM, "Donald Stufft" <donald at stufft.io> wrote:
> On July 8, 2015 at 4:00:48 AM, Robert Collins (robertc at robertcollins.net)
> > I'm backporting the changes in cPython to mock to the mock standalone
> > package. There's various cleanups, some of which would break compat
> > for 2.6. I've already thrown < 2.6 under the bus, but 2.6 is sitting
> > in a grey area.... its doable but its still got quite some ugly (in
> > particular 'nested' which only exists on 2.6 these days).
> > If noone jumps in with:
> > "I use mock, on 2.6, and I'm willing to do the work in a timely manner
> > to backport any future changes from cPython that are problematic on
> > 2.6"
> > then its going under the bus:) I'll do the initial backport, but I'm
> > looking for a time commitment from someone(s) to deal with future
> > ports on an as-needed basis. By which I mean, when I go to port, and
> > its gnarly, I want to be able to drop someone an email and have
> > turnaround time of oh, say, a week.
> pip uses mock and still cares about 2.6.
> Donald Stufft
> PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
I too use mock a lot on 2.6.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python