<?xml version="1.0"?>
<statsTarget><link>http://cia.vc/stats/author/foom</link><counters><counter name="forever" lastEventTime="1313770956" firstEventTime="1280434647">11</counter></counters><metadata></metadata><recentMessages><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#12326</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>Linux 3: code should avoid using sys.platform == 'linux2'</file></files>     <log>&gt; configure_linux2.python3.2.patch
 
 It would probably be more future-proof to use &quot;linux*)&quot;, not &quot;linux3)&quot; in the case expression.</log>     <url>http://bugs.python.org/issue12326</url>   </commit> </body> <timestamp>1313770956</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#12326</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>Linux 3: code should avoid using sys.platform == 'linux2'</file></files>     <log>YAGNI. Nobody has needed sys.build_platform yet. (And no, sys.platform isn't it, since that's been fixed at linux2 approximately forever). Why do  ...</log>     <url>http://bugs.python.org/issue12326</url>   </commit> </body> <timestamp>1313767761</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#12326</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>Linux 3: code should avoid using sys.platform == 'linux2'</file></files>     <log>&gt; Sure, you can compile and run Python on both versions of Linux, but
 &gt; what if your application uses features that are only present in Linux
 &gt;  ...</log>     <url>http://bugs.python.org/issue12326</url>   </commit> </body> <timestamp>1313721384</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#12326</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>Linux 3: code should avoid using sys.platform == 'linux2'</file></files>     <log>M.A., your comments do not make sense in the context of Linux. It does not actually require porting -- Linux 2.6.39 to Linux 3.0 is no more disrup ...</log>     <url>http://bugs.python.org/issue12326</url>   </commit> </body> <timestamp>1313713956</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#12326</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>Linux 3: code should avoid using sys.platform == 'linux2'</file></files>     <log>&gt; Well, except maybe if you plan to write applications working only on Python &gt;= 2.7.3? ... this version is not released yet.
 
 No, of course I d ...</log>     <url>http://bugs.python.org/issue12326</url>   </commit> </body> <timestamp>1313695924</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#12326</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>Linux 3: code should avoid using sys.platform == 'linux2'</file></files>     <log>&gt; I will backport the fix to 2.7 and 3.2.
 
 Uh, wait, so does that mean you're *not* going to do the compatibility-preserving thing and force sys ...</log>     <url>http://bugs.python.org/issue12326</url>   </commit> </body> <timestamp>1313636718</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#12326</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>Linux 3: code should avoid using sys.platform == 'linux2'</file></files>     <log>Oh wow, so it depends on the *build* time major version? That's really not useful at all for linux 2.x and 3.x; there is nothing useful anyone can ...</log>     <url>http://bugs.python.org/issue12326</url>   </commit> </body> <timestamp>1312558980</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#2650</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>re.escape should not escape underscore</file></files>     <log>Right you are, it seems that python's regexp implementation is terribly slow when doing replacements with a substitution in them. (fixing the brok ...</log>     <url>http://bugs.python.org/issue2650</url>   </commit> </body> <timestamp>1294938723</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#2650</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>re.escape should not escape underscore</file></files>     <log>Show your speed test? Looks 2.5x faster to me. But I'm running this on python 2.6, so I guess it's possible that the re module's speed was decimat ...</log>     <url>http://bugs.python.org/issue2650</url>   </commit> </body> <timestamp>1294934943</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#2650</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>re.escape should not escape underscore</file></files>     <log>I just ran into the impl of escape after being surprised that '/' was being escaped, and then was completely amazed that it wasn't just implemente ...</log>     <url>http://bugs.python.org/issue2650</url>   </commit> </body> <timestamp>1294457140</timestamp></message><message> <generator>   <name>Roundup Reactor for CIA</name>   <version>69784</version> </generator> <source>   <project>Python</project>   <module>#5154</module>   <branch>roundup</branch> </source> <body>   <commit>     <author>foom</author>     <files><file>OSX broken poll testing doesn't work</file></files>     <log>The reason it's a problem is because a &quot;device&quot; is everything other than a socket, pipe, slave-side of tty, or file. That is, /dev/null, /dev/zero ...</log>     <url>http://bugs.python.org/issue5154</url>   </commit> </body> <timestamp>1280434647</timestamp></message></recentMessages></statsTarget>
