Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
timhoffm merged 1 commit intomatplotlib:mainfromstory645:dep-headings
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

@story645story645 added the Documentation: devdocsfiles in doc/devel labelOct 11, 2023
@story645story645force-pushed thedep-headings branch 2 times, most recently from63a9257 toa1a9e37CompareOctober 11, 2023 03:23
@story645
Copy link
MemberAuthor

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
MemberAuthor

story645 commentedOct 11, 2023
edited
Loading

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.

@story645story645 changed the titleDOC: made dependency section headings conciseDOC: concise dependency heading + small clarificationsOct 11, 2023
Copy link
Member

@timhoffmtimhoffm 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
MemberAuthor

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
MemberAuthor

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
MemberAuthor

@story645story645Oct 17, 2023
edited
Loading

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.

timhoffm reacted with thumbs up emoji
Copy link
MemberAuthor

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
MemberAuthor

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

@story645story645force-pushed thedep-headings branch 2 times, most recently from99e3d53 to2b7439eCompareOctober 17, 2023 00:25
@story645
Copy link
MemberAuthor

@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

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 reacted with thumbs up emoji

@story645
Copy link
MemberAuthor

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

@QuLogic
Copy link
Member

@story645
Copy link
MemberAuthor

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
MemberAuthor

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 versionCo-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
@timhoffmtimhoffm added this to thev3.8-doc milestoneOct 20, 2023
@timhoffmtimhoffm merged commitb1857a1 intomatplotlib:mainOct 20, 2023
@lumberbot-app
Copy link

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.xgit 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 theStill Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free tosuggest an improvement.

@lumberbot-app
Copy link

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-docgit 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 theStill Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free tosuggest an improvement.

@timhoffm
Copy link
Member

IMHO not worth a manual backport.

@story645story645 deleted the dep-headings branchOctober 20, 2023 13:18
@story645
Copy link
MemberAuthor

IMHO not worth a manual backport

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

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@QuLogicQuLogicQuLogic left review comments

@jklymakjklymakjklymak left review comments

@rcomerrcomerrcomer left review comments

@timhoffmtimhoffmtimhoffm approved these changes

Assignees
No one assigned
Labels
Documentation: devdocsfiles in doc/devel
Projects
None yet
Milestone
v3.9.0
Development

Successfully merging this pull request may close these issues.

5 participants
@story645@timhoffm@QuLogic@jklymak@rcomer

[8]ページ先頭

©2009-2025 Movatter.jp