This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients ncoghlan
Date 2017-10-30.05:23:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1509340997.49.0.213398074469.issue31899@psf.upfronthosting.co.za>
In-reply-to
Content
This is a potential follow-up to issue 31898, whereby the recommended packages list could be taken into account as part of CPython's own testing regime. The gist of the idea would be to:

1. Update the recommended-packages list to nominate particular *versions* of those dependencies (the latest available version as of each CPython maintenance release)
2. Add a new "-uthird-party" resource definition to the regression test suite
3. Add a new regression test that installed the recommended packages into a virtual environment and ran their tests when that resource was enabled


It's a separate issue, since this would be more work to maintain than the simple "we recommend these packages" list proposed in issue 31898.
History
Date User Action Args
2017-10-30 05:23:17ncoghlansetrecipients: + ncoghlan
2017-10-30 05:23:17ncoghlansetmessageid: <1509340997.49.0.213398074469.issue31899@psf.upfronthosting.co.za>
2017-10-30 05:23:17ncoghlanlinkissue31899 messages
2017-10-30 05:23:16ncoghlancreate