-
-
Notifications
You must be signed in to change notification settings - Fork 409
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
Re-applied Black formatting to tardis after excluding undesired directories #1213
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1213 +/- ##
=======================================
Coverage 77.71% 77.71%
=======================================
Files 91 91
Lines 5727 5727
=======================================
Hits 4451 4451
Misses 1276 1276
Continue to review full report at Codecov.
|
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.
@wkerzendorf On reviewing each file, these are the changes I think we'll require - otherwise everything looks good to me! Please if you can, take a moment to see anything else you may find!
And if these changes seem fine by you, let me know - I'll do a batch commit.
11d62b8
to
a2de4c4
Compare
Excluded |
…tories (tardis-sn#1213) * Added directories to exclude in black configuration file * Added black to tardis environment file * Excluded setup related files from black configuration * Applied black formatting to remaining files
This PR aims to exclude undesired directories from black formatting. When running black, there are still 10 files which were formatted blacked (which were not covered earlier run, because it was run not on root of project but inside
tardis/
).A brief summary of changes in each file are:
pyproject.toml
- Added directories to exclude from black (includingastropy_helpers
which was being formatted by black)tardis_env3.yml
- Added black as a code quality dependency, so that it is already installed in a new tardis environmenttardis/plasma/
- 2 files - they are actually one line changes, made by us @wkerzendorf when editing strings - those strings were quite long, so black line-breaked them as expected ✅docs/
- There are 4 python files inside itasv/
- 1 fileah_bootstrap.py
,setup.py
,ez_setup.py
are remaining 3 at root directory.Motivation and Context
Related #1201
How Has This Been Tested?
They're only formatting changes so ideally they shouldn't break the code. And if test pipeline pass, they are good to merge.