Use `pyproject.toml` for PEP 517 / PEP 518 metadata

[AA-Turner]

Currently this project generates a setup.py for each of its ~400 packages.

Please consider migrating to the standardardised pyproject.toml, as installing by running ./setup.py has been deprecated for several years.

The minimum required is generating a pyproject.toml file that contains the below:

[build-system]
requires = ["setuptools>=42"]
build-backend = "setuptools.build_meta"

This is all that's required to move to standardised build metadata, away from the legacy setup.py approach.

---

If you want to explore migrating to standard metadata, it would look similar to the below:

# Setup script for mypy-boto3-appconfig.

# Copyright 2025 Vlad Emelianov

[build-system]
requires = ["setuptools>=42"]
build-backend = "setuptools.build_meta"

[project]
name = "mypy-boto3-appconfig"
version = "1.38.0"
urls.Homepage = "https://github.com/youtype/mypy_boto3_builder"
urls.Documentation = "https://youtype.github.io/boto3_stubs_docs/mypy_boto3_appconfig/"
urls.Source = "https://github.com/youtype/mypy_boto3_builder"
urls.Tracker = "https://github.com/youtype/mypy_boto3_builder/issues"
license = "MIT"
authors = [{ name = "Vlad Emelianov", email = "vlad.emelianov.nz@gmail.com" }]
description = "Type annotations for boto3 AppConfig 1.38.0 service generated with mypy-boto3-builder 8.10.1"
readme = "README.md"
classifiers=[
    "Development Status :: 5 - Production/Stable",
    "Intended Audience :: Developers",
    "Environment :: Console",
    "License :: OSI Approved :: MIT License",
    "Natural Language :: English",
    "Operating System :: OS Independent",
    "Programming Language :: Python :: 3",
    "Programming Language :: Python :: 3.8",
    "Programming Language :: Python :: 3.9",
    "Programming Language :: Python :: 3.10",
    "Programming Language :: Python :: 3.11",
    "Programming Language :: Python :: 3.12",
    "Programming Language :: Python :: 3.13",
    "Programming Language :: Python :: 3.14",
    "Programming Language :: Python :: 3 :: Only",
    "Programming Language :: Python :: Implementation :: CPython",
    "Typing :: Stubs Only",
]
keywords=["boto3", "appconfig", "boto3-stubs", "type-annotations", "mypy", "typeshed", "autocomplete"]
requires-python = ">=3.8"
dependencies = [
    "typing-extensions; python_version<'3.12'",
]

You could also explore a different build backend, such as flit-core, which is smaller and a little faster.

A

[vemel]

Hello.

THank you for your seggestion. I considered switching to a proper pyproject setup, but thisalso includes updating build scripts for conda-forge.

[AA-Turner]

Thanks!

I also package projects for conda-forge, and the pyproject-based approach is definitely supported. Do you recall what previously didn't work? I'd be happy to try and have a look, if useful.

A

[vemel]

As I remember correctly, dependecny on setuptools should be explicitly set:

https://github.com/conda-forge/mypy_boto3_builder-feedstock/blob/main/recipe/meta.yaml
https://github.com/conda-forge/boto3-stubs-feedstock/blob/main/recipe/meta.yaml

Should I change these meta files in order to use PEP 517 metadata?

[AA-Turner]

Those conda recipes should work with pyproject metadata with no changes!

There's already a dependency on setuptools declared under the requirements.host table (build-time requirements). For example, https://github.com/conda-forge/distlib-feedstock/blob/main/recipe/meta.yaml is the recipe for distlib, which has a similarly minimal pyproject.toml to the one I suggested above.

A