[TIP] Does anyone *need* mock update from cPython in Python 2.6?
robertc at robertcollins.net
Wed Jul 8 00:58:56 PDT 2015
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
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.
Robert Collins <rbtcollins at hp.com>
HP Converged Cloud
More information about the testing-in-python