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

Spin off plasma calculator into separate affiliated package #2655

Open
namurphy opened this issue May 1, 2024 · 0 comments
Open

Spin off plasma calculator into separate affiliated package #2655

namurphy opened this issue May 1, 2024 · 0 comments
Labels
effort: high Requiring perhaps ∼1–2 weeks. Can this be split up into multiple smaller/focused issues? packaging Related to packaging or distribution Python Lv3 | Proficient Issues that require proficiency in Python revisit in 2025 Issues that we should revisit in ∼2025 status: on hold Issues & PRs that are being intentionally delayed

Comments

@namurphy
Copy link
Member

namurphy commented May 1, 2024

Description of improvement

Right now the plasma calculator is installed as part of PlasmaPy. One possibility in the future would be to split off the plasma calculator into a standalone package.

Motivation

In the lead-up to the Python in Heliophysics Community Summer School, work is ongoing to create a heliocloud Python environment that contains all PyHC core packages. A problem that arose was that PlasmaPy's dependency on voila (and consequently tornado) for the plasma calculator ended up conflicting with requirements for other packages that needed web servers. In a sense, this would let us separate the plasma calculator front-end from the plasmapy back-end. Separating the plasma calculator would decrease the dependency footprint of PlasmaPy. In particular, we may be able to drop PlasmaPy's dependency on the Jupyter ecosystem, as well as dependencies dealing with web server stuff like voila and tornado.

Alternatives

In the short term, we can loosen the requirements for voila and other packages.

Implementation

This would probably be a fair bit of work, and thus I'd place it at low priority.

@namurphy namurphy added status: on hold Issues & PRs that are being intentionally delayed Python Lv3 | Proficient Issues that require proficiency in Python effort: high Requiring perhaps ∼1–2 weeks. Can this be split up into multiple smaller/focused issues? packaging Related to packaging or distribution revisit in 2026 Issues that we should revisit in ∼2026 labels May 1, 2024
@namurphy namurphy added revisit in 2025 Issues that we should revisit in ∼2025 and removed revisit in 2026 Issues that we should revisit in ∼2026 labels May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: high Requiring perhaps ∼1–2 weeks. Can this be split up into multiple smaller/focused issues? packaging Related to packaging or distribution Python Lv3 | Proficient Issues that require proficiency in Python revisit in 2025 Issues that we should revisit in ∼2025 status: on hold Issues & PRs that are being intentionally delayed
Projects
None yet
Development

No branches or pull requests

1 participant