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.

classification
Title: Ensure backwards compatibility with recommended packages
Type: enhancement Stage: test needed
Components: Tests Versions: Python 3.8, Python 3.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: ncoghlan
Priority: low Keywords:

Created on 2017-10-30 05:23 by ncoghlan, last changed 2022-04-11 14:58 by admin.

Messages (2)
msg305211 - (view) Author: Nick Coghlan (ncoghlan) * (Python committer) Date: 2017-10-30 05:23
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.
msg372502 - (view) Author: Nick Coghlan (ncoghlan) * (Python committer) Date: 2020-06-28 07:17
Removing the issue assignment, as I'm not actively working on this (although I still think it's a reasonable idea).
History
Date User Action Args
2022-04-11 14:58:53adminsetgithub: 76080
2020-06-28 07:17:27ncoghlansetassignee: ncoghlan ->
messages: + msg372502
2017-10-30 05:23:17ncoghlancreate