René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add Python 3.15 to the test workflow","articleBody":"Python 3.15.0 final is scheduled for **2026-10-01** (PEP 790; rc1 2026-08-04). `actions/setup-python` already carries pre-release builds (`3.15.0-beta.3` as of July 2026), so the workflow can start testing it any time.\n\nTwo-step plan, whichever release picks this up:\n\n1. **Now-ish (any release):** add a non-blocking pre-release job to `python-package.yml` so interpreter breakage surfaces early:\n\n   ```yaml\n   - uses: actions/setup-python@v5\n     with:\n       python-version: \"3.15\"\n       allow-prereleases: true\n   ```\n\n   with `continue-on-error: true` on the matrix entry so a beta-only failure warns without blocking merges.\n\n2. **After 3.15.0 final (October 2026):** promote it to a regular blocking matrix entry, add the `Programming Language :: Python :: 3.15` classifier, and drop `continue-on-error`.\n\nTiming note: 3.15 final and Python 3.10 EOL land the same month, so if this coincides with 2.0, step 2 and the #257 floor bump (`\u003e=3.11`) are one release-prep item — the supported window becomes exactly 3.11–3.15.\n\nNo milestone yet — undecided which release takes it.\n","author":{"url":"https://github.com/derek73","@type":"Person","name":"derek73"},"datePublished":"2026-07-06T07:53:38.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/259/python-nameparser/issues/259"}