-
-
Notifications
You must be signed in to change notification settings - Fork 32k
Fixing links in documentation #70098
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
Comments
I've run 'make linkcheck' on Doc and it highlighted a number of faulty links in documentation. I've tried fixing some of them and here is the resulting patch. It's a bit too long and touches many files, so to summarise:
I'm going to attach output.txt that is produced after running linkcheck with this patch applied, it is about three time smaller than the original one and has this types of issues:
|
New changeset ce5ef48b5140 by Georg Brandl in branch '3.5': |
Reopening, for fixing the rest of the broken ones. |
BTW it looks like the suspicious.csv file needs updating to compensate for this change: http://buildbot.python.org/all/builders/Docs%203.5/builds/654/steps/suspicious/logs/stdio WARNING: [using/unix:31] ":Packaging" found in "https://en.opensuse.org/Portal:Packaging" |
Perhaps, I'm misreading the log output, but it seems to me that it's Doc/tools/susp-ignored.csv that needs updating. Here is the attached patch. |
New changeset 8f8e86ea3abb by Georg Brandl in branch '3.5': |
New changeset ce721df212cf by Serhiy Storchaka in branch '3.5': New changeset 14e00e7e4d51 by Georg Brandl in branch '2.7': New changeset 00addbb47c5c by Serhiy Storchaka in branch '2.7': New changeset 15c4557af8e0 by Serhiy Storchaka in branch 'default': |
Licence text shouldn't be touched, I think. http://www.openssl.org/docs/apps/ciphers.html#CIPHER_LIST_FORMAT became https://www.openssl.org/docs/manmaster/apps/ciphers.html#CIPHER-LIST-FORMAT If Martin still have the importer code somewhere, he probably could provide an up to date link. |
The bug tracker importer still exists if you know what revision to look it up in: <http://svn.python.org/view/tracker/importer/?pathrev=88980\> |
New changeset bb10867ffe28 by Serhiy Storchaka in branch '3.5': New changeset 61c7deea9e6a by Serhiy Storchaka in branch '2.7': New changeset e3c9a47a83fb by Serhiy Storchaka in branch 'default': |
Serhiy, the OpenSSL links are now https |
Fixed links to "A Byte of Python" and OpenSSL. Not fixed dead links: http://www.zope.com/ |
They works with http. Some links (including python.org) are now redirected from http to https. It may be worth to add https explicitly. |
For XML-RPC extensions we can use a web archive: https://web.archive.org/web/20130120074804/http://ontosys.com/xml-rpc/extensions.php. There are precedences of using it for other dead links. Opened separate bpo-26736 for https-zation. |
New changeset 4b65bee79dab by Georg Brandl in branch '2.7': |
XML-RPC link was fixed in bpo-26889 (using the a web archive). Left links are http://www.zope.com/, http://www.pythonlabs.com/logos.html, and links to dead projects. What can we do with Zope and PythonLabs links? |
zope should be http://www.zope.org/ |
Does it not matter that the link to pythonlabs is a part of the official license text? Besides, it's not an actual html a tag, but rather a verbatim text, surely the only correction here is to make sure that the linkcheck doesn't check links within pre, code and similar tags. |
Isn't this is a different legal entity? |
On Mon, May 16, 2016 at 08:40:51PM +0000, Serhiy Storchaka wrote:
Is it? I don't know. I can find no references to zope.com being |
maybe we can continue on this issue and close it asap. what do you think ? |
Adding Jim Fulton (for Zope) and Guido (for Pythonlabs). I don't know who owns the former, but I'm fairly sure Guido owns the pythonlabs domain. |
www.pythonlabs.com still exists. (The www. is mandatory.) And zope.org also On Jun 3, 2017 7:52 AM, "Barry A. Warsaw" <[email protected]> wrote:
|
Zope Corporation no longer exists. Any references to it should be in the past tense and without a link. (The http://www.zope.org is for the Zope Foundation, which is a different thing.) |
But http://www.pythonlabs.com/logos.html doesn't. And since this link is a part of the BeOpen.com license, changing it changes the license. I don't know whether this part of the license is valid if the referred resource no longer available. |
I can make the logos.html page appear. Just keep the link in the license as On Jun 3, 2017 1:05 PM, "Sanyam Khurana" <[email protected]> wrote:
|
I've done what I can for the logos: http://www.pythonlabs.com/logos.html |
Thank you! What is left:
|
I suggest the following replacement for that paragraph in Doc/license.txt, as well as in LICENSE: In May 2000, Guido and the Python core development team moved to |
+1 |
Can we now close this old issue? |
Who is Basti5611 (Schmehl Bastian), why do they have permission to change issue titles, and why did they change this issue title? |
Victor, there is just one last thing to do in here. All the links pointing to Github (that are build automatically) are permanently redirected from https://github.com/python/cpython/tree/master/* to https://github.com/python/cpython/blob/master/* I will issue a separate PR for it, and then we're good to close this issue. PS: Guido, I'm not sure about the title change either. |
"I will issue a separate PR for it, and then we're good to close this Ok. |
@guido: in roundup, by default anyone can change the issue title. I imagine he is a new user who just didn't understand that he was doing so. (And indeed, the account was created on 1/19). |
A number of PRs have been merged since this issue opened in 2015. After Victor's merge of #46227 in January 2018, this looks ready to close. I'm going to close it. If there are further links that need fixing as they sometimes fall out of date, please open a new issue with specific links needing updating. Thanks. |
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: