Jonathan Crall writes: > But perhaps a subset of it (pytest lite?) might be isolated and > considered for inclusion down the line?
*Anything* might be considered for inclusion, although Guido might dispose of it with a simple "please, no". That is not going to happen to your suggestion! :-) But somebody's got to do the work of identifying the subset, and coordinating with PyTest on whether they would use the subset in their more extended framework, and (one hopes) volunteer to maintain the module in the stdlib. There's also the issue of how mature PyTest is. If it's still gaining features at some pace, it probably doesn't want to be part of the stdlib yet. A final comment: I wonder if you're being too conservative. It's true that generally we prefer small targeted modules in the stdlib, but everybody needs tests (even if they don't know it ;-), and there might be quite large audiences for the great majority of PyTest. So maybe we could get all of PyTest in (perhaps in a slimmed-down form without some of the redundant/deprecated functionality). As I mentioned, I'm not a PyTest user (yet! :-), so I wouldn't be a good proponent for this. But I find the proposal exciting. Steve _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/YAKG44LYL6BEVWHAWULZTOLZUOIWATBQ/ Code of Conduct: http://python.org/psf/codeofconduct/
