-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Move metadata to pyproject.toml #9951
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #9951 +/- ##
=======================================
Coverage 98.73% 98.73%
=======================================
Files 121 121
Lines 36728 36728
Branches 4384 4384
=======================================
Hits 36262 36262
Misses 314 314
Partials 152 152
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
CodSpeed Performance ReportMerging #9951 will not alter performanceComparing Summary
|
bba81fd
to
f718fa1
Compare
Let's not rush this. Keeping a dedicated config is a conscious choice. Also, PRs must not reformat half a project along with changing the packaging configs. FWIW I'd rather keep it as is for now. Especially, since I was going to sync the configs across the projects and this is going to cause a lot of headache since it conflicts with how things are now. I'm 👎 on this migration right now. It'd be interesting to gather the current dependency limitations in the downstreams to make an informed choice. Additionally, the move would have to happen in the dependencies first. |
That's actually a bug with the current black config. Since it can't detect the lowest supported version, it assumes
I'm probably missing something here. This PR doesn't affect any downstream projects. The project metadata change is minimal and spec compliant. Tbh I just thought it might be a good time to move the static metadata after I learned that it can work fine with There is no strict need to do that now, so if you're opposed feel free to close the PR. |
0d487cf
to
92f533f
Compare
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.
I personally don't care where the project metadata sits until it works and I personally shouldn't spend additional time on the infrastructure maintenance.
@cdce8p could you please extract a fix for this particular problem into a separate PR? A small patch has a great chance to be reviewed and approved quickly. |
Ooh, sorry. I've pushed the wrong button and closed the PR. Please accept my apologizes. |
92f533f
to
51bb1d2
Compare
Thanks, @cdce8p |
What do these changes do?
The metadata changes:
Open questions