[issue31899] Ensure backwards compatibility with recommended packages

[Nick Coghlan]

Nick Coghlan  added the comment:

Removing the issue assignment, as I'm not actively working on this (although I 
still think it's a reasonable idea).

--
assignee: ncoghlan -> 

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31899] Ensure backwards compatibility with recommended packages

[Nick Coghlan]

New submission from Nick Coghlan :

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.

--
assignee: ncoghlan
components: Tests
messages: 305211
nosy: ncoghlan
priority: low
severity: normal
stage: test needed
status: open
title: Ensure backwards compatibility with recommended packages
type: enhancement
versions: Python 3.7, Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com