I guess I haven't considered restrictions on the machines where the modules are required. So there's definitely a reason for things making their way in to stdli

I guess I haven't considered restrictions on the machines where the modules are required. So there's definitely a reason for things making their way in to stdlib in those situations. (I wish the virtualenv stuff was packaged as part of core Python, to be honest...but that's a discussion for another time.) My concern is the frustration (which may not be the right term) of having to continually bring things out of core, implement improvements, and then feed them back in to core. All the while being concerned with impact your changes may have on the entire ecosystem. All-in-all, maybe it's just moot. This could probably just be chalked up to the ebb-and-flow of software development as a whole.