-
Notifications
You must be signed in to change notification settings - Fork 6
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
PLEP7: top level package structure #26
PLEP7: top level package structure #26
Conversation
…el packages, details are left to package focused PLEPs
I assumed you didn't actually want to change `plasmapy.simulation` to `plasmapy.simulations` plural, so I reverted that.
I went ahead and did a few initial comments, and oh dear, the tables broke them 😆 The Files Changed view will be a better choice for viewing them. |
… into PLEP7_top_level_package_structure
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.
LGTM bar a few minor comments 👍 Thanks for all your work on this @rocco8773 et al
PLEP-0007.rst
Outdated
|
||
If new code does NOT fall within the current framework, then this PLEP | ||
needs to be modified/updated accordingly before any new top-level | ||
sub-packages are created. |
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.
Or, presumably, the code should be ajusted to fit this framework?
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've reworded this a bit to indicate that amending the PLEP should be the last resort option. I assumed that would happen by default, since it will always be easier to conform code than to amend the PLEP and get it accepted.
This statement is here more so for the off chance that we overlooked something that should be a top-level package.
+-----------------+-------------------------------------------------------------+ | ||
| scope: | | A collection of tests for top-level modules (i.e. | | ||
| | functions and classes defined in top-level ``.py`` | | ||
| | files). | |
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.
Surely we also want to test functions and classes defined in subfolders of these modules?
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 thought folders of .py files were subpackages, and if that's the case, the current wording makes sense - there's no other place to put tests for .py files in the main plasmapy directory.
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.
In the python lingo, .py
files are modules and folders are sub-packages.
@SolarDrew Yes, sub-package tests should still be done within their respective directory.
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.
Think of this as a place for testing the interplay of various sub-packages. Will using dispersion capability in simulation break anything? Will using formulary inside analysis break anything?
Co-authored-by: Drew Leonard <[email protected]>
… the step to amend this PLEP
… into PLEP7_top_level_package_structure
**Contents** | ||
|
||
* `Abstract`_ | ||
* `Detailed Description`_ | ||
|
||
* `Why?`_ | ||
* `Top-Level Sub-Packages`_ | ||
|
||
* `Extensible Packages are Exempt`_ | ||
* `Implementation`_ | ||
* `Issues, Pull Requests, and Branches`_ | ||
* `Backward Compatibility`_ | ||
* `Decision Rationale`_ |
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.
As an aside, maybe we should add a table of contents to the PLEP template. That way, future PLEP writers would have a draft table of contents ready.
This PLEP is focused on:
The goal is to:
This PLEP was initially outlined by the PlasmaPy Coordinating Team at the 2019 61st APS-DPP Meeting.
P.S. I will remove the "draft" label when I'm satisfied with the PLEP and ready to merge it.
Still need to...
./README.rst
with DOIaccepted
when accepted