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
Make source code links less prominent #55067
Comments
Reading library source code will only be enlightening to expert users, since most modules are not academic but real-world implementations, with all the complications it entails. Therefore, putting a link at the top of module sections is only confusing for most people. I would like to shift these links to the bottom of doc pages, where we already have "see also" links to RFCs and the like. |
+1 |
Please leave these alone for the time being. I put them high on the page so that people would have a consistent and easy to find view-source link. It is an experiment and time will tell whether it was a good choice. For the time being, I don't want it buried. The goal is to reacquaint people with the source as an adjunct to the docs. The phrase use-the-source-luke used to be common in the python community but now many devs don't seem to be able to readily access the source (with it tucked away in a library directory). |
I don't think someone "not able to readily access the source" from a While I understand the motivation to encourage reading of the source |
As Raymond explained, he added these links as a kind of social experiment and this issue itself shows that it works. :-) I have a few suggestions on how to make these links more useful:
|
The question is not how they could be more useful, but *whether* they I agree that visual appearance of the ViewVC pages could be better but |
1: I hope this will just be a matter of using the same Pygments theme in Sphinx and hgweb. 2: I don’t think hgweb can do that. Mercurial being extensible, this addition may be a fun project. 3: Not all modules are good examples (see threading for some unelegant code), so I support ad-hoc selection. I also support the real fix of improving the quality of every module, but that’s longer-term. :) 4: “Show Source” is a link that is easily overlooked IMO, a seealso section makes me think people will actually see the link. There is also the minor concern of breaking expectations of people accustomed to Sphinx. |
On Fri, Jan 7, 2011 at 4:32 PM, Éric Araujo <report@bugs.python.org> wrote:
The problem with ad-hoc selection is that it adds maintenance burden
Having the sources on "public display" may help achieving this goal.
A side-bar link may be in addition to the more prominent but less |
I'm curious as to how the experiment is being carried out and how conclusions will be drawn. |
Removed the wordy and bright yellow boxes. See r87898. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: