On Jul 05, 2016, at 10:38 AM, Steve Dower wrote: >My hope is that it would be essentially a "pip freeze"/"pip install -r ..." >(or equivalent with whatever tool is used/created for managing the >stdlib). Perhaps using VCS URIs rather than version numbers? > >That is, the test run would dump a list of exactly which stdlib versions it's >using, so that when you review the results it is possible to recreate it. I think you'd have to have vcs checkouts though, because you will often need to fix or change something in one of those other library pieces. The other complication of course is that now you'll have two dependent PRs with reviews in two different repos. >But the point is well taken. I'm very hesitant about splitting out packages >that are common dependencies of other parts of the stdlib, but there are >plenty of leaf nodes in there too. Creating a complex dependency graph would >be a disaster. Yeah. <shudder> Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <http://mail.python.org/pipermail/python-dev/attachments/20160705/943541f4/attachment-0001.sig>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4