Skip to content

ci(client-python): single source of truth for the python version (if doable) #354

Description

@guzmud

Use case

Follow-up to #353 , investigate (and act upon) whether a single source of truth can be used to set the python version in the CI jobs (avoiding the multiple statement of the python version that need to be synchronized over time).

Current workaround

Remember to update the python version in the different relevant files each time the version is bumped.

Proposed solution

It seems uv has mechanisms linked to using the requires-python provided by the pyproject.toml, this could be a lead maybe.

Additional information

If the feature request is approved, would you be willing to submit a PR?

Yes / No (help can be provided if you need assistance submitting a PR)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureType: new feature or capability (feat:).needs triageNeeds triage from the Filigran product team.tech foundationLinked to tech foundation.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions