Skip to content

Migrate to pyproject toml#416

Closed
popescu-v wants to merge 4 commits intodevfrom
migrate-to-pyproject-toml
Closed

Migrate to pyproject toml#416
popescu-v wants to merge 4 commits intodevfrom
migrate-to-pyproject-toml

Conversation

@popescu-v
Copy link
Copy Markdown
Collaborator

@popescu-v popescu-v commented Jun 6, 2025

related to #411


TODO Before Asking for a Review

  • Rebase your branch to the latest version of dev (or main for release PRs)
  • Make sure all CI workflows are green
  • When adding a public feature/fix: Update the Unreleased section of CHANGELOG.md (no date)
  • Self-Review: Review "Files Changed" tab and fix any problems you find
  • API Docs (only if there are changes in docstrings, rst files or samples):
    • Check the docs build without warning: see the log of the API Docs workflow
    • Check that your changes render well in HTML: download the API Docs artifact and open index.html
    • If there are any problems it is faster to iterate by building locally the API Docs

popescu-v added 2 commits June 6, 2025 18:35
Notes:
- setup.py is still needed for versioneer support.
- versioneer.py vendoring is needed for Conda packaging (so that the
  version can be available to meta.yaml before the building itself).

related_to #411
@popescu-v popescu-v self-assigned this Jun 6, 2025
@popescu-v popescu-v force-pushed the migrate-to-pyproject-toml branch from 49cd60a to 670beb2 Compare June 10, 2025 12:07
@popescu-v popescu-v force-pushed the migrate-to-pyproject-toml branch from 670beb2 to a4fb124 Compare June 10, 2025 12:22
@popescu-v
Copy link
Copy Markdown
Collaborator Author

Superseded by PR #441.

@popescu-v popescu-v closed this Jul 30, 2025
@popescu-v popescu-v deleted the migrate-to-pyproject-toml branch August 5, 2025 09:05
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.

1 participant