<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 23, 2010, at 7:54 PM, Lennart Regebro wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Sun, May 23, 2010 at 11:39, Brian Quinlan <<a href="mailto:brian@sweetapp.com">brian@sweetapp.com</a>> wrote:<br><blockquote type="cite">This package eliminates the need to construct the boilerplate present in<br></blockquote><blockquote type="cite">many Python applications i.e. a thread or process pool, a work queue and<br></blockquote><blockquote type="cite">result queue. It also makes it easy to take an existing Python application<br></blockquote><blockquote type="cite">that executes (e.g. IO operations) in sequence and execute them in parallel.<br></blockquote><blockquote type="cite">It package provides common idioms for two existing modules i.e.<br></blockquote><blockquote type="cite">multiprocessing offers map functionality while threading doesn't. Those<br></blockquote><blockquote type="cite">idioms are well understood and already present in Java and C++.<br></blockquote><br>It can do that as a separate package as well.</div></blockquote><div><br></div><div><div>You could make the same argument about any module in the stdlib. </div></div><br><blockquote type="cite"><div>And not only that, it<br>could then be available on PyPI for earlier versions of Python as<br>well, making it much more likely to gain widespread acceptance.<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><div><br></div><div>I doubt it. Simple modules are unlikely to develop a following because it is too easy to partially replicate their functionality. urlparse and os.path are very useful modules but I doubt that they would have been successful on PyPI.</div></div><div><br></div><div><blockquote type="cite"><div><blockquote type="cite">Could you be a little more specific about Guido's argument at PyCon?<br></blockquote><br>A module in stdlib has to be "dead". After it's included in the stdlib<br>it can not go through any major changes since that would mean loss of<br>backwards incompatibility.</div></blockquote><div><br></div>The good news in this case is that the same API has been used successfully in Java and C++ for years so it is unlikely that any major changes will need to be made.</div><div><br><blockquote type="cite"><div>Also, you can't fix bugs except by<br>releasing new versions of Python. Therefore the API must be completely<br>stable, and the product virtually bugfree before it should be in<br>stdlib. The best way of ensuring that is to release it as a separate<br>module on PyPI, and let it stabilize for a couple of years.<br></div></blockquote></div><div><br></div><div>Yeah but that model isn't likely to work with this package.</div><div><br><div>Cheers,</div><div>Brian</div></div></body></html>