enh(policy): Scientific application language. #359
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lwasser
approved these changes
Dec 4, 2025
Member
lwasser
left a comment
lwasser
left a comment
There was a problem hiding this comment.
I'm happy with this as is. Let's see if anyone else has issues with it and try to merge it by next friday dec 12!!
coatless
reviewed
Dec 4, 2025
| Diagram showing the tiers of software in the Python ecosystem starting with Python itself and as you move out, packages become more domain specific. In this image, packages such as xarray and numpy are considered core to scientific Python. Packages and distributions like Astropy, SunPy, and MetPy are considered domain specific. pyOpenSci's review | ||
| process focuses on domain-specific packages and tools that support scientific workflows rather than core infrastructure packages, as | ||
| these packages tend to have more variability in long-term maintenance and | ||
| package infrastructure and quality compared with established core packages. Examples of pyOpenSci-reviewed packages include MovingPandas (geospatial data), Pandera (data validation), PyGMT (geophysical mapping), and xclim (climate data analysis). **Source: ["Jupyter meets earth" project](https://jupytearth.org/jupyter-resources/introduction/ecosystem.html)** |
Contributor
There was a problem hiding this comment.
Maybe add great-tables for table creation?
coatless
reviewed
Dec 4, 2025
| services. For example, a general client for Amazon Web Services data storage would not | ||
| be in scope, but a package that retrieves specific scientific datasets from AWS would be. | ||
|
|
||
| - Examples: [OpenOmics](https://github.com/pyOpenSci/software-submission/issues/31), [pyDov](https://github.com/pyOpenSci/software-submission/issues/19), [Physcraper](https://github.com/pyOpenSci/software-review/issues/26) |
Contributor
There was a problem hiding this comment.
Is there a way we can make these example sections more up to date? Maybe a page on the pyopensci website filtering by category?
Contributor
Author
There was a problem hiding this comment.
@coatless should we go ahead and make an issue for this? I think this is a good idea but a separate page is large enough to warrant a separate PR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Was very little discussion after two weeks, so I had AI take a crack at updating the language around this policy. Closes #350. Has some style changes but should still be appropraite to review. Should continue to discuss and can incorporate further changes.