-
Notifications
You must be signed in to change notification settings - Fork 122
Update docs and prep for 2.15 release #475
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
base: main
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 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. 🚀 New features to boost your workflow:
|
| #. Remove the ``meson_build`` directory if present. | ||
| #. Run ``pip install`` again and test the installation. | ||
|
|
||
| #. Run ``pip install .`` again and test the installation. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
Purpose
Update docs following #433, bump version and prep for release.
Expected time until merged
A few days
Type of change
Testing
Checklist
ruff checkandruff formatto make sure the Python code adheres to PEP-8 and is consistently formattedfprettifyor C/C++ code withclang-formatas applicable