On Sat, Feb 25, 2012 at 1:32 PM, Matt Joiner <anacro...@gmail.com> wrote:
> Evidently some modules have to ship with core if they are required (sys),or
> expose internals (os, gc). Others are clearly extras, (async{ore,hat},
> subprocess, unittest, select).There's a whole raft of additional dependencies introduced by the build process and the regression test suite. The fact that your "others are clearly extras" was only right for 2 out of 5 examples doesn't fill me with confidence that you have any idea of the scale of what you're suggesting. But the real reason this isn't going to happen? It's an absolute ton of work that *won't make Python better at the end*. Anyone that feels otherwise is free to fork CPython and try it for themselves, but I predict they will be thoroughly disappointed with the outcome. (We moved to a DVCS in large part to make it easier for other people to experiment with things - they don't have to ask python-dev's permission, they can just fork, try it for themselves, and see if it works out. If they instead want to *pay* somebody to try it on their behalf, then they can just offer some contract work and see if they get any takers). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
