Skip to content

Add to the overview of the software stack? #220

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

Closed
DamienIrving opened this issue Jan 25, 2022 · 4 comments
Closed

Add to the overview of the software stack? #220

DamienIrving opened this issue Jan 25, 2022 · 4 comments
Labels
content Content related issue good second issue Clearly described, educational, but less trivial than "good first issue".

Comments

@DamienIrving
Copy link
Contributor

At the moment the Overview section of the "Core Scientific Python Packages" part of the book provides links to more information about numpy, matplotlib, cartopy, pandas, xarray, etc. I was wondering whether it would be worth adding some text to that overview section to explain how the core libraries relate to one another?

Not all of the content on the PyAOS stack page is relevant, but it gives a sense of what I mean by a description of how the core libraries relate to one another:
https://pyaos.github.io/stack/

If this sounds like a good idea, I'd be happy to submit a PR with some proposed text for others to consider.

@DamienIrving DamienIrving added the content Content related issue label Jan 25, 2022
@brian-rose
Copy link
Member

I think it sounds like a great idea and will improve the readability of this section, particularly for new users who are working linearly through the book. I think the current Overview page is more of a placeholder than anything else.

@jukent jukent added the good second issue Clearly described, educational, but less trivial than "good first issue". label May 9, 2022
@r-ford r-ford added this to the hackathon milestone Jun 24, 2022
@r-ford r-ford removed this from the hackathon milestone Aug 22, 2022
@clyne
Copy link
Contributor

clyne commented Apr 24, 2023

Hi @DamienIrving , we're just doing some housekeeping. Is this a topic that you still think is of interest and would have value? Would you have a few cycles for this perhaps? Thanks!

@DamienIrving
Copy link
Contributor Author

Hi, @clyne. This issue was actually resolved in by #265, so already done 😄

@clyne
Copy link
Contributor

clyne commented Apr 25, 2023

Awesome. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Content related issue good second issue Clearly described, educational, but less trivial than "good first issue".
Projects
Status: Done
Development

No branches or pull requests

5 participants