-
Notifications
You must be signed in to change notification settings - Fork 295
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
Replace setup with pyproject.toml #2763
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2763 +/- ##
==========================================
- Coverage 95.92% 95.89% -0.03%
==========================================
Files 377 377
Lines 53489 53488 -1
==========================================
- Hits 51310 51293 -17
- Misses 2179 2195 +16
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Pull Request Test Coverage Report for Build 8357659803Details
💛 - Coveralls |
It should also be noted this switches the build system to use hatchling instead of setuptools. If you haven't already, please review other uses throughout the repository of setuptools-scm. For example it is needed to install unstable dependencies here: satpy/.github/workflows/ci.yaml Line 71 in 8527311
But this isn't for satpy, but likely other pytroll packages that we depend on that use setuptools-scm during the build process. @mraspaud does hatch-vcs default to the same versioning for dev/dirty environments? Not that it matters much, just curious. |
Oh and is hatch defaulting to finding the |
Yes it does if my regex isn't too rusty https://github.com/pypa/setuptools_scm/blob/v6.4.0/src/setuptools_scm/config.py#L13 |
That's a setuptools scm file, not hatch, right? |
Yes, it is, but setuptools-scm is a dependency of hatch-vcs :) |
Yes, just for the unstable build, this seemed correct to me. There is another mention of setuptools_scm in the rtd_environment.yml file, but as far as I can see that yaml file isn't used anywhere, so my assumption was that we are good.
the version number looks very similar for dev situations indeed, except that the date is also appended. See the screen capture here. |
That RTD environment file is used by RTD and is configured here: Line 22 in 8527311
|
indeed! The rtd build seems to be working, so I suspect there is not need to add anything. |
@djhoese ok merging this? |
Yes I think so. Go for it. |
[coverage:run] | ||
relative_files = True | ||
omit = | ||
satpy/version.py |
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.
Darn it @mraspaud. This is why coveralls is broken. The coverage config never got transferred to pyproject.toml. Fixing now...
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.
Sorry
This PR removes setup.[py,cfg] and fills up pyproject.toml instead.