Skip to content

Conversation

@sfc-gh-bnisco
Copy link
Contributor

@sfc-gh-bnisco sfc-gh-bnisco commented Nov 20, 2025

TL;DR

Migrated from setup.py to pyproject.toml for modern Python packaging.

What changed?

  • Replaced setup.py with pyproject.toml for package configuration
  • Updated GitHub workflows to use pyproject.toml instead of setup.py for caching
  • Changed build process to use python -m build instead of python setup.py sdist bdist_wheel
  • Removed MANIFEST.in as package data is now defined in pyproject.toml

Copy link
Contributor Author

sfc-gh-bnisco commented Nov 20, 2025

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR modernizes the package configuration by migrating from the legacy setup.py to the standardized pyproject.toml format following PEP 621. The migration updates build processes, removes deprecated files, and ensures GitHub workflows are compatible with the new configuration approach.

Key Changes:

  • Replaced setup.py with pyproject.toml for package metadata and build configuration
  • Updated GitHub workflows to use modern build tools (python -m build instead of setup.py sdist bdist_wheel)
  • Removed MANIFEST.in as package data is now explicitly declared in pyproject.toml

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
setup.py Removed legacy setup.py file containing package configuration
pyproject.toml Added modern PEP 621 compliant configuration with project metadata, dependencies, and build settings
MANIFEST.in Removed as package data is now defined in pyproject.toml's tool.setuptools.package-data section
.github/workflows/release.yml Updated cache keys and build commands to use pyproject.toml and python -m build
.github/workflows/playwright.yml Updated cache keys and build commands to use pyproject.toml and python -m build

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link

@sfc-gh-nbellante sfc-gh-nbellante left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@sfc-gh-bnisco sfc-gh-bnisco force-pushed the feat-ccv2-dual-pyproject branch 2 times, most recently from 110cebf to c9690c7 Compare November 20, 2025 19:44
@sfc-gh-bnisco sfc-gh-bnisco marked this pull request as ready for review November 21, 2025 19:43
@sfc-gh-bnisco sfc-gh-bnisco force-pushed the feat-ccv2-dual-pyproject branch from c9690c7 to bca5022 Compare November 21, 2025 21:23
Copy link
Contributor Author

sfc-gh-bnisco commented Nov 24, 2025

Merge activity

  • Nov 24, 9:44 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Nov 24, 9:44 PM UTC: @sfc-gh-bnisco merged this pull request with Graphite.

@sfc-gh-bnisco sfc-gh-bnisco merged commit 5a2c3ad into main Nov 24, 2025
4 checks passed
@sfc-gh-bnisco sfc-gh-bnisco deleted the feat-ccv2-dual-pyproject branch November 25, 2025 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants