target_versions are out of date

Open
#63 1 comment 0 reactions 0 assignees View on GitHub

@stevenh is already working on this.

Since Jun 24, 2025.

  • #64 by @stevenh — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing

Research direction

Start by locating the target_version flag definition and its validation, then inspect the plugin tests covering accepted Python versions. Update the behavior so newer version values such as py311, py312, and py313 do not require a package release, and add or adjust tests showing the accepted format.

Written by the indexing model from the issue text.

Description

The target_version flag uses a fixed set of python versions with the latest being py310, no py311, py312 or py313.

It's nice it enforces the format, but might be better to accept a string so its not a maintenance burden when new releases come out, requiring users to update the this package when otherwise it wouldnt be needed.

Dominant language
Python
Stars
181
Forks
29
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 pydantic/pytest-examples

All issues in pydantic/pytest-examples

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.