Skip to content

Migrate to pyproject toml #441

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 5, 2025
Merged

Migrate to pyproject toml #441

merged 4 commits into from
Aug 5, 2025

Conversation

popescu-v
Copy link
Collaborator

@popescu-v popescu-v commented Jul 29, 2025

closes #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

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 force-pushed the migrate-to-pyproject-toml-v11 branch 7 times, most recently from 0845b4f to 87b8197 Compare July 30, 2025 11:27
@popescu-v popescu-v mentioned this pull request Jul 30, 2025
6 tasks
@popescu-v popescu-v force-pushed the migrate-to-pyproject-toml-v11 branch 6 times, most recently from 854f1e2 to d578542 Compare July 30, 2025 16:39
Notes:
- the version is hard-coded in the khiops/__init__.py file and not in
  pyproject.toml, because pyproject.toml is not accessible at runtime
  for an installed package
- conda-build does not support pyproject.toml-style dynamic versions,
  hence the version has to be hard-coded in conda/meta.yaml as well
- when moving to conda-forge, the version would have to be hard-coded
  anyway
- the khiops/__init__.py vs conda/meta.yaml version coherence is checked
  in the conda package building and testing workflow.
@popescu-v popescu-v force-pushed the migrate-to-pyproject-toml-v11 branch from d578542 to f052165 Compare July 30, 2025 17:05
@popescu-v popescu-v requested a review from tramora July 30, 2025 17:23
@tramora
Copy link
Collaborator

tramora commented Jul 31, 2025

Except a few questions I do not have any blocking remark

@tramora tramora self-requested a review August 2, 2025 23:49
@popescu-v popescu-v force-pushed the migrate-to-pyproject-toml-v11 branch 2 times, most recently from a60685b to 67ea814 Compare August 4, 2025 16:05
@popescu-v popescu-v force-pushed the migrate-to-pyproject-toml-v11 branch from 67ea814 to f87b040 Compare August 4, 2025 16:33
@popescu-v popescu-v requested a review from tramora August 4, 2025 17:04
Copy link
Collaborator

@tramora tramora left a comment

Choose a reason for hiding this comment

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

Looks good

@popescu-v popescu-v merged commit f568e5f into dev Aug 5, 2025
95 checks passed
@popescu-v popescu-v deleted the migrate-to-pyproject-toml-v11 branch August 5, 2025 10: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.

Migrate from setup.py to pyproject.toml
2 participants