Skip to content

DOC: concise dependency heading + small clarifications #27058

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

Merged
merged 1 commit into from
Oct 20, 2023

Conversation

story645
Copy link
Member

PR summary

This PR simplifies the titles of a couple of sections on the dependency page, mostly by removing building and Matplotlib because I think those are a given cause it's the dependency page. It makes the right hand side more scannable.
-->

PR checklist

@story645 story645 added the Documentation: devdocs files in doc/devel label Oct 11, 2023
@story645 story645 force-pushed the dep-headings branch 2 times, most recently from 63a9257 to a1a9e37 Compare October 11, 2023 03:23
@story645
Copy link
Member Author

OK, based on @jklymak's comment I went and looked and there was only one ref I had to updated. Generally we either link to the whole page (which would remain dependencies) or use custom link text geared to the context of the paragraph. That being the case, I really prefer the short titles. Currently the page has longer titles for subheadings and "topic" titles for the subsubheadings:
image

@timhoffm
Copy link
Member

I agree that the right menu is more verbose than need be, e.g. we don't need "Matplotlib" in there. But the proposed version does not contain the word "dependencies" at all.

grafik

I suggest to keep it at least on the section titles:

  • On this page
    • Runtime dependencies
      • Mandatory
      • Optional
      • C libraries
      • ...
    • Build dependencies
    • Test dependencies
    • Documentation dependencies

@story645
Copy link
Member Author

story645 commented Oct 11, 2023

I suggest to keep it at least on the section titles:

that sounds like a reasonable compromise to me. Going roughly with that, I end up here: (+- tweaks to testing to make it like the others)

image

Also changed/cleaned up some language and uh I have no idea why that pip/many linux paragraph is in this doc.

@story645 story645 changed the title DOC: made dependency section headings concise DOC: concise dependency heading + small clarifications Oct 11, 2023
Copy link
Member

@timhoffm timhoffm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Take or leave my comments.


Manual Download
^^^^^^^^^^^^^^^
Install from source
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not quite sure whether "install" is the right term here. But I don't have an alternative either.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, it was more that Manual download reallly doesn't mean anything here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use source might be better?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't want to over-think this, but "source" is a quite generic term. IMHO good headings would be

  • C libraries
    • Automatic download (this section header is missing but should be added)
    • Use system libraries
    • From source files (or "Custom source files")

Copy link
Member Author

@story645 story645 Oct 17, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with you so I'll make the change.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also "Matplotlib vendored version" or the like is probably is better for "Auto download" so I'm going with that.

@story645
Copy link
Member Author

Made the changes, but probably would be good for @QuLogic to take a quick glance to make sure I didn't lose anything

@story645 story645 force-pushed the dep-headings branch 2 times, most recently from 99e3d53 to 2b7439e Compare October 17, 2023 00:25
@story645
Copy link
Member Author

@QuLogic does #26621 (comment) mean that I should remove the line about Aix being an exception in the section about MPL vendored freetype?

@QuLogic
Copy link
Member

QuLogic commented Oct 18, 2023

Yes, I noticed that here, which is why I asked them. Since it looks like we won't need to keep the special-casing, we can drop that from the docs.

@story645
Copy link
Member Author

Thanks! Also, is the section about pip/manylinux still applicable?

@QuLogic
Copy link
Member

QuLogic commented Oct 18, 2023

@story645
Copy link
Member Author

I think it just didn't feel like it fits w/ the other dependencies, but if it's alright than I don't think there's anything left to change.

Comment on lines 223 to 224
in the target environment manually.
:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why this colon is here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

accident, but also I went and unpacked the sentences above to try and make it very explicit that most folks should not need to install the build dependencies.

note required MinGW windows header version

Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
@timhoffm timhoffm added this to the v3.8-doc milestone Oct 20, 2023
@timhoffm timhoffm merged commit b1857a1 into matplotlib:main Oct 20, 2023
@lumberbot-app
Copy link

lumberbot-app bot commented Oct 20, 2023

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout v3.8.x
git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 b1857a13c04beab777f84e0f8810ecd8f5cfc512
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #27058: DOC: concise dependency heading + small clarifications'
  1. Push to a named branch:
git push YOURFORK v3.8.x:auto-backport-of-pr-27058-on-v3.8.x
  1. Create a PR against branch v3.8.x, I would have named this PR:

"Backport PR #27058 on branch v3.8.x (DOC: concise dependency heading + small clarifications)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

@lumberbot-app
Copy link

lumberbot-app bot commented Oct 20, 2023

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout v3.8.0-doc
git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 b1857a13c04beab777f84e0f8810ecd8f5cfc512
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #27058: DOC: concise dependency heading + small clarifications'
  1. Push to a named branch:
git push YOURFORK v3.8.0-doc:auto-backport-of-pr-27058-on-v3.8.0-doc
  1. Create a PR against branch v3.8.0-doc, I would have named this PR:

"Backport PR #27058 on branch v3.8.0-doc (DOC: concise dependency heading + small clarifications)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

@timhoffm
Copy link
Member

IMHO not worth a manual backport.

@story645 story645 deleted the dep-headings branch October 20, 2023 13:18
@story645
Copy link
Member Author

IMHO not worth a manual backport

Yeah this mentions meson and that's milestoned to 3.9.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation: devdocs files in doc/devel
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants