Skip to content
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

Nuke plasmapy.constants #651

Merged
merged 6 commits into from
Jun 29, 2019
Merged

Nuke plasmapy.constants #651

merged 6 commits into from
Jun 29, 2019

Conversation

StanczakDominik
Copy link
Member

I thought we had done that a while ago.

plasmapy.constants is purely a wrapper for astropy.constants. It provides no useful functionality of its own except introducing confusion.

Off with its HEAD, as they say.

Most plasmapy.constants imports were changed to astropy.constants

Electrons are weird so those were changed to astropy.constants.si where necessary

Astropy.constants lacks pi, so that was imported from NumPy
@StanczakDominik StanczakDominik force-pushed the StanczakDominik-patch-2 branch from 8ee1643 to 799cea4 Compare June 26, 2019 05:38
Also rename changelog entry to previous PR
@codecov
Copy link

codecov bot commented Jun 26, 2019

Codecov Report

Merging #651 into master will increase coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #651      +/-   ##
==========================================
+ Coverage   96.51%   96.51%   +<.01%     
==========================================
  Files          54       54              
  Lines        4558     4563       +5     
==========================================
+ Hits         4399     4404       +5     
  Misses        159      159
Impacted Files Coverage Δ
plasmapy/__init__.py 46.15% <ø> (ø) ⬆️
plasmapy/physics/quantum.py 100% <100%> (ø) ⬆️
plasmapy/physics/relativity.py 100% <100%> (ø) ⬆️
plasmapy/physics/dielectric.py 100% <100%> (ø) ⬆️
plasmapy/transport/braginskii.py 99.71% <100%> (ø) ⬆️
plasmapy/classes/sources/plasma3d.py 100% <100%> (ø) ⬆️
plasmapy/transport/collisions.py 99.07% <100%> (ø) ⬆️
plasmapy/diagnostics/langmuir.py 100% <100%> (ø) ⬆️
plasmapy/physics/parameters.py 100% <100%> (ø) ⬆️
plasmapy/utils/decorators/checks.py 99.16% <100%> (ø) ⬆️
... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8271af6...66ee1bc. Read the comment docs.

@StanczakDominik StanczakDominik force-pushed the StanczakDominik-patch-2 branch 2 times, most recently from 8ee1643 to b6944db Compare June 26, 2019 06:02
@namurphy namurphy added physical data Related to fundamental physical data, including atomic data breaking change For breaking changes, excluding deprecations and planned removals labels Jun 29, 2019
@namurphy namurphy added this to the v0.3.0 milestone Jun 29, 2019
Copy link
Member

@namurphy namurphy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thinking about this more, this does make sense as long as there are no constants that are specific to plasma physics that are not in astropy.constants. If there are some constants that we end up needing in the future, then probably the better thing to do would be to propose an upstream change to astropy.constants instead.

It would be helpful to include some documentation to remind users that they should go to astropy.constants for the physical constants that they need, which could be either in this PR or raised as an issue for the future.

@StanczakDominik
Copy link
Member Author

Good point on the docs!

If there are any constants that are irrelevant to astronomy (as per documentation to astropy.constants) and relevant to plasma physics, we can always keep them in physics if need be.

@StanczakDominik StanczakDominik merged commit 0ebc28e into master Jun 29, 2019
@StanczakDominik StanczakDominik deleted the StanczakDominik-patch-2 branch August 25, 2019 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change For breaking changes, excluding deprecations and planned removals physical data Related to fundamental physical data, including atomic data
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants