Skip to content
This repository was archived by the owner on Mar 12, 2025. It is now read-only.
This repository was archived by the owner on Mar 12, 2025. It is now read-only.

Update Python packaging approach to pyproject.toml #136

@jenstroeger

Description

@jenstroeger

Is your feature request related to a problem? Please describe.

After looking through .circleci/packaging/python, it seems to me that the Python package uses the somewhat dated setup.py approach. There’s much discussion to remove it from the documentation and to guide packages in migrating to myproject.toml (PEP 631). (Also note that according to this announcement the support for setup.py will be removed from Python 3.12 internal packages.)

Describe the solution you'd like

It shouldn’t be too difficult to migrate and to follow the updated packaging guidelines, and move the package forward to the new approach.

Describe alternatives you've considered

Nope.

Additional context

Looking at the current setup.py I don’t see a minimum Python version specified although the classifiers indicate that support for Python 2.7 is required (the classifiers are incomplete too). However, there’s a second repository googleapis/python-api-common-protos whose content is generated from this repository? There too, setup.py should be replaced.

I’m not sure which one of the repositories is the base…

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: p3Desirable enhancement or fix. May not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions