Skip to content

Conversation

@ewu63
Copy link
Collaborator

@ewu63 ewu63 commented Jan 29, 2026

Purpose

Update docs following #433, bump version and prep for release.

Expected time until merged

A few days

Type of change

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (non-backwards-compatible fix or feature)
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Documentation update
  • Maintenance update
  • Other (please describe)

Testing

Checklist

  • I have run ruff check and ruff format to make sure the Python code adheres to PEP-8 and is consistently formatted
  • I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
  • I have run unit and regression tests which pass locally with my changes
  • I have added new tests that prove my fix is effective or that my feature works
  • I have added necessary documentation

@ewu63 ewu63 requested a review from marcomangano as a code owner January 29, 2026 05:46
@codecov
Copy link

codecov bot commented Jan 29, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.70%. Comparing base (6d7b957) to head (507795b).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #475   +/-   ##
=======================================
  Coverage   86.70%   86.70%           
=======================================
  Files          24       24           
  Lines        3468     3468           
=======================================
  Hits         3007     3007           
  Misses        461      461           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

eirikurj
eirikurj previously approved these changes Jan 29, 2026
#. Remove the ``meson_build`` directory if present.
#. Run ``pip install`` again and test the installation.

#. Run ``pip install .`` again and test the installation.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Just double checking that deleting meson_build is not necessary anymore. Does mesonpy not have a _build folder or just handles the rebuilds better?
I believe I instinctively deleted the folder before each rebuild while testing

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The build directory is now a temporary directory so it gets cleaned automatically, unless you are building in editable mode in which case it is by default build. I've added a note on this.

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.

4 participants