-
Notifications
You must be signed in to change notification settings - Fork 59
MNT: Migrate project to flit-scm #597
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
Conversation
abaa60c
to
2138207
Compare
Codecov ReportBase: 76.77% // Head: 76.81% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #597 +/- ##
==========================================
+ Coverage 76.77% 76.81% +0.04%
==========================================
Files 19 19
Lines 4349 4357 +8
Branches 1193 1194 +1
==========================================
+ Hits 3339 3347 +8
Misses 821 821
Partials 189 189
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
67246ef
to
4837825
Compare
Flake8 does not support pyproject.toml yet (if ever?). Rename setup.cfg to .flake8 to make it more explicit that the only concern left is flake8 configuration.
4837825
to
36bb2de
Compare
can this allow for installing with |
Yes, and also optional extras like |
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.
Looks great! Thanks so much for taking the time.
A couple suggestions to restore some dropped "extras".
Co-authored-by: Chris Markiewicz <effigies@gmail.com>
Co-authored-by: Chris Markiewicz <effigies@gmail.com>
Types of changes
Summary
With
setup.py
soon to become legacy in favour of the more declarativepyproject.toml
, this PR proposes to migrate the project to Flit and perform dynamic versioning withflit-scm
instead ofversioneer
.The very same migration has been successfully experimented with in pydra-nipype1, which makes me confident the same can be achieved in the main Pydra repository. The main benefit is to future-proof project management –
setup.py
is going away sooner or later, better be safe than sorry when it happens.Checklist
pyproject.toml
flit-scm