Opt into https://endoflife.date/python based warnings / erroring out via a dedicated input

Open
#6 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, python
Domain
ci-cd, devops

Research direction

Start by tracing how the python-version request identifies the runtime and where the job's final step is defined. Review the endoflife.date Python API or feeds and determine how a dedicated input controls warnings at the beginning and optional errors at the end. Done means the workflow can apply the chosen Python support policy with the requested warning or failure behavior.

Written by the indexing model from the issue text.

Description

enhancement

We could probably figure out what the currently tested runtime Python is from the python-version request and based on some EOL/support strategy do something in a dedicated step at the end of the job. Maybe issue a warning at the beginning but optionally error out at the very end.

There's https://endoflife.date/api/v1/products/python/, https://endoflife.date/python.atom and webcal://endoflife.date/calendar/python.ics for programmatic access.

cc @sirosen FYI

Dominant language
No language data
Stars
6
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tox-dev/workflow

All issues in tox-dev/workflow

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.