<?xml version="1.0"?>
<statsTarget><link>http://cia.vc/stats/author/michael.foord</link><counters><counter name="forever" lastEventTime="1336663087" firstEventTime="1238610401">870</counter><counter name="lastMonth" lastEventTime="1335816750" firstEventTime="1333942663">19</counter><counter name="thisMonth" lastEventTime="1336663087" firstEventTime="1336663087">1</counter></counters><metadata></metadata><recentMessages><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14770</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Minor documentation fixes</file></files>     <log>[new] A bunch of minor fixes for the documentation suggested by Kurt Robinson to the webmaster email address:
 
 
 Below, you will find 15 snippet ...</log>     <url>http://bugs.python.org/issue14770</url>   </commit> </body> <timestamp>1336663087</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14558</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Documentation for unittest.main does not describe some keyword arguments.</file></files>     <log>A good change - thanks Ezio.</log>     <url>http://bugs.python.org/issue14558</url>   </commit> </body> <timestamp>1335816749</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14664</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Skipping a test mixin gives metaclass error</file></files>     <log>Thanks Antoine - much appreciated.</log>     <url>http://bugs.python.org/issue14664</url>   </commit> </body> <timestamp>1335383291</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14664</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Skipping a test mixin gives metaclass error</file></files>     <log>This could go into 2.7 too.</log>     <url>http://bugs.python.org/issue14664</url>   </commit> </body> <timestamp>1335376149</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14664</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Skipping a test mixin gives metaclass error</file></files>     <log>Patch looks good - thanks.</log>     <url>http://bugs.python.org/issue14664</url>   </commit> </body> <timestamp>1335318428</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14634</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Mock cannot autospec functions with keyword-only arguments.</file></files>     <log>Hmmm... looks like formatargspec does support these features but they aren't documented. If it works out I'll update the docs for inspect.formatar ...</log>     <url>http://bugs.python.org/issue14634</url>   </commit> </body> <timestamp>1335043016</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14634</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Mock cannot autospec functions with keyword-only arguments.</file></files>     <log>This is non-trivial to fix. Although inspect.getfullargspec can be used, which does support keyword only arguments, inspect.formatargspec *doesn't ...</log>     <url>http://bugs.python.org/issue14634</url>   </commit> </body> <timestamp>1335041750</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#7559</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>TestLoader.loadTestsFromName swallows import errors</file></files>     <log>My favoured fix is to catch the exception and generate a failing test that re-raises the *original exception* (with traceback) when run. That way  ...</log>     <url>http://bugs.python.org/issue7559</url>   </commit> </body> <timestamp>1335032704</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14636</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Mock could check for exceptions in side effect list</file></files>     <log>Seems like a good change.</log>     <url>http://bugs.python.org/issue14636</url>   </commit> </body> <timestamp>1334976220</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14613</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>time.time can return None or NaN</file></files>     <log>So NaN is a possible result from time.time()? Perhaps that should be mentioned in the docs. Is returning NaN preferable to failing with an exception?</log>     <url>http://bugs.python.org/issue14613</url>   </commit> </body> <timestamp>1334769398</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14613</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>time.time can return None or NaN</file></files>     <log>[new] time.time() can return None, or sometimes NaN. If it can't get a &quot;proper&quot; value from the OS then I would expect it to throw an exception. Th ...</log>     <url>http://bugs.python.org/issue14613</url>   </commit> </body> <timestamp>1334766637</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14577</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>pickling uses __class__ so you can't pickle proxy/mock objects that pretend to be other objects</file></files>     <log>Nick - in general proxy objects have a *reference* to their target (weakref being somewhat of a special case), and pickle can already handle multi ...</log>     <url>http://bugs.python.org/issue14577</url>   </commit> </body> <timestamp>1334418889</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14577</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>pickling uses __class__ so you can't pickle proxy/mock objects that pretend to be other objects</file></files>     <log>test_pickle still passes with only copyreg.py modified. 
 
 With one additional change in pickle.py (line 405 to use type(obj) instead of obj.__cl ...</log>     <url>http://bugs.python.org/issue14577</url>   </commit> </body> <timestamp>1334418118</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14577</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>pickling uses __class__ so you can't pickle proxy/mock objects that pretend to be other objects</file></files>     <log>So, changing copyreg.py to use type(self) instead of self.__class__ isn't sufficient. _pickle accesses __class__ as well it seems. However I'm run ...</log>     <url>http://bugs.python.org/issue14577</url>   </commit> </body> <timestamp>1334417417</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14577</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>pickling uses __class__ so you can't pickle proxy/mock objects that pretend to be other objects</file></files>     <log>[new] Pickling uses __class__ instead of type(obj) to determine the type to pickle. This means that objects which pretend to be other objects (lik ...</log>     <url>http://bugs.python.org/issue14577</url>   </commit> </body> <timestamp>1334416723</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#11218</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>pattern=None when following documentation for load_tests and unittest.main()</file></files>     <log>Also the patch to allow the pattern to be None (and revert to the default pattern in this case) looks good.</log>     <url>http://bugs.python.org/issue11218</url>   </commit> </body> <timestamp>1334365662</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#11218</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>pattern=None when following documentation for load_tests and unittest.main()</file></files>     <log>So the logic of the &quot;pattern&quot; argument to &quot;load_tests&quot; is that it should not be None when test discovery is loading the __init__.py module of a te ...</log>     <url>http://bugs.python.org/issue11218</url>   </commit> </body> <timestamp>1334365603</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14534</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Add method to mark unittest.TestCases as &quot;do not run&quot;.</file></files>     <log>Here are my objections to the standard (but not widely used outside our own tests) mixin pattern for base testcases (copied and pasted from issue  ...</log>     <url>http://bugs.python.org/issue14534</url>   </commit> </body> <timestamp>1334018706</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14534</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Add method to mark unittest.TestCases as &quot;do not run&quot;.</file></files>     <log>So the technique I suggested is that the TestLoader checks classes for the &quot;testbase&quot; (or whatever we call it) *in the class dict*. So inheritance ...</log>     <url>http://bugs.python.org/issue14534</url>   </commit> </body> <timestamp>1334018480</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#14533</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>michael.foord</author>     <files><file>Modify regrtest to make test_main optional</file></files>     <log>Looks good to me. Note that if module level setup and teardown is needed for running tests then it should be possible to do this with setUpModule  ...</log>     <url>http://bugs.python.org/issue14533</url>   </commit> </body> <timestamp>1333942663</timestamp></message></recentMessages></statsTarget>
