DOC: Tighten ecosystem->data science per #242 #262
Conversation
|
After this PR:
Compared to before:
This PR is closer to the amount of content we should keep; it removes a bunch of duplication and sticks to "one figure per tab" that I think we agreed somewhere else. It does end a bit abruptly. I'd like to keep DVC and MLFlow I think, because those are quite important but less well-known, so it helps teach people. I'll try to tweak this in a follow-up PR to better capture how broad the data science space is. |
Follow up to numpygh-242, alternative to numpygh-262. The content rewrite and inclusion of more relevant libraries attempts to make this sound natural, sketch the breadth of the Python data science offerings, and keeps some of the tools like DVC and MLFlow that beginning to intermediate data scientists really need to learn about. It does shrink the amount of content to a more reasonable size.
There was a problem hiding this comment.
This did leave out too much in the end, while not addressing a few of the issues in the existing content that I still wanted to address. So I submitted gh-272 as an alternative.
Your comments on that PR would be appreciated @bjnath. I noticed I couldn't tag you as a reviewer - I'll invite you to a NumPy team so that becomes possible, and will allow you to add labels, close issues, etc.
Follow up to numpygh-242, alternative to numpygh-262. The content rewrite and inclusion of more relevant libraries attempts to make this sound natural, sketch the breadth of the Python data science offerings, and keeps some of the tools like DVC and MLFlow that beginning to intermediate data scientists really need to learn about. It does shrink the amount of content to a more reasonable size.
Proposed edit per @rgommers comment in #242:
"Still would like to make this tab a little more compact."