Commit by michael.foord on roundup :: #14003/__self__ on built-in functions is not as documented: (link)

It's nicer for introspection if __self__ is None on builtin functions. But fixing the docs is easier (and more backwards compatible).

Commit by michael.foord on roundup :: #13932/If some test module fails to import another module unittest reports a very misleading message: (link)

[closed] This is a duplicate of issue 7559. See the discussion there.

Commit by michael.foord on roundup :: #13827/Unexecuted import changes namespace: (link)

[closed] hippmr: the problem is that by importing SOMETHING inside that function you're creating a *local variable* called SOMETHING. If the overr ...

Commit by michael.foord on roundup :: #12600/Support parameterized TestCases in unittest: (link)

Why not create a simple TestCase factory in load_tests?

 Before a patch can be produced a clean api that offers a clear benefit over the TestCas ...

Commit by michael.foord on roundup :: #13675/IDLE won't open if it can't read recent-files.lst: (link)

[closed] Thanks

Commit by michael.foord on roundup :: #13675/IDLE won't open if it can't read recent-files.lst: (link)

[new] Reported by a user. Reported on Windows but probably not Windows specific.

 If IDLE doesn't have permission to read the recent-files.lst f ...

Commit by michael.foord on roundup :: #8313/<unprintable AssertionError object> message in unittest tracebacks: (link)

traceback patch looks good. Thanks for the unittest2 patch as well.

Commit by michael.foord on roundup :: #11829/inspect.getattr_static code execution with meta-metaclasses: (link)

Andreas, is this still needed and valid?

Commit by michael.foord on roundup :: #11178/Running tests inside a package by module name fails: (link)

[closed] No longer reproducable on CPython. Unfortunately still an issue with unittest2.

Commit by michael.foord on roundup :: #13561/os.listdir documentation should mention surrogateescape: (link)

[new] Where os.listdir encounters undecodable bytes from the filesystem it uses the surrogateescape handler. As the resulting strings are invalid ...

Commit by michael.foord on roundup :: #13241/llvm-gcc-4.2 miscompiles Python (XCode 4.1 on Mac OS 10.7): (link)

Note that this works for me on a Macbook Air that has never had Snow Leopard, nor XCode 3 installed.

 As far as I can tell non-llvm gcc *is* in ...

Commit by michael.foord on roundup :: #13387/add exact_type argument to assertIsInstance: (link)

I think your proposed workaround is good enough and no extra effort to type than the suggested change to assertIsInstance.

 -1 on a new method
  ...

Commit by michael.foord on roundup :: #13241/llvm-gcc-4.2 miscompiles Python (XCode 4.1 on Mac OS 10.7): (link)

Ah, it seems I have XCode 3.2.6 installed alongside XCode 4.2.

Commit by michael.foord on roundup :: #13241/llvm-gcc-4.2 miscompiles Python (XCode 4.1 on Mac OS 10.7): (link)

On OS X Lion, with XCode 4.2 installed, I find the following works (no need to install macports):

 ./configure CC=gcc-4.2 --prefix=/dev/null --w ...

Commit by michael.foord on roundup :: #12681/unittest expectedFailure could take a message argument like skip does: (link)

Well, it would be nice for the Python test suite, maybe not so useful for external users of the api. Something for regrtest rather than unittest I ...

Commit by michael.foord on roundup :: #10548/Error in setUp not reported as expectedFailure (unittest): (link)

I think Twisted uses the tearDown to fail tests as well. As we have two use cases perhaps we should allow expectedFailure to work with failues in ...

Commit by michael.foord on roundup :: #12958/test_socket failures on Mac OS X: (link)

See issue 10548. There is some resistance to expectedFailure masking errors in setUp/tearDown as these aren't the place where you would normally e ...

Commit by michael.foord on roundup :: #12681/unittest expectedFailure could take a message argument like skip does: (link)

Well, expectedFailure could dispatch on the type of the argument, with different behaviour for strings and anything else (presumed to be a functio ...

Commit by michael.foord on roundup :: #8639/Allow callable objects in inspect.getfullargspec: (link)

Right. For a callable object (instance with __call__ method), it's unambiguous which signature you want. For a class it's ambiguous.

Commit by michael.foord on roundup :: #12626/run test cases based on a glob filter: (link)

I agree with Antoine, as test.support is not a public api adding new features to assist with debugging is fine.