You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to me that it would be better to not test on many platforms with poetry install, but rather to generate a wheel on a single one and pip install it, in order to have the same dependency resolution as my users.
The idea would be to have the test workflow in the actual repositories with four jobs:
analysis:
description: | basic checks if this does not pass, no need to do anything elsewheels:
description: | package wheels for all the platforms upload them as an artifacttest:
requires: [analysis, wheels]description: | download wheels, install with pip, and run the actual tests publish coveragedeploy:
requires: testif: releasedescription: | download all the wheels and upload to PyPI
After designing it, a template will be provided in the docs.
alecandido
changed the title
Avoid Poetry for testing
Comprehensive test/deploy caller
Feb 29, 2024
python-poetry/poetry#7746 (comment)
The text was updated successfully, but these errors were encountered: