Updated Python's references to be the official docs instead of Dive Into Python.

[The-Amoghavarsha]

Hey there, recently I came across an outdated (old) resource link in the Django documentation, and I had a little discussion about it on the mailing list and the Discord server to replace it with the Python documentation. And I got a positive response from both places.

Kindly check the discussion here - https://groups.google.com/g/django-developers/c/j28iN_WdTRA

As you can see from the image, I've used ripgrep to locate the resource that I wanted to replace, i.e, Dive Into Python. From docs/intro/index.txt, I've replaced Dive Into Python with Python Documentation and from docs/intro/contributing.txt, I've removed Dive Into Python resource, followed by a few words.

I've tested the changes locally using Sphinx, and everything seems to be working fine.

[nessita]

Looks good, I added some suggestions.

Thanks for your contribution!

[nessita]

Suggested change

	Python quickly, we recommend `Python documentation`_. If that's not quite your
	style, there are many other `books about Python`_.
	Python quickly, we recommend referring to the official `Python
	documentation`_, which provides comprehensive and authoritative information
	about the language, as well as links to other resources such as a list of
	`books about Python`_.

[The-Amoghavarsha]

I have accepted the suggestion (omitting /3/), thank you :)

[nessita]

Hey @The-Amoghavarsha, I don't see my suggestion applied, would you know what happened? Thanks!

[The-Amoghavarsha]

Oops, I'm extremely sorry! I thought it was edited already. It seems like it has been edited outside the commit. I think I have to update my branch.

I was also working on few changes which @ngnpope mentioned below.

[nessita]

@The-Amoghavarsha I still don't see the changes I suggested, do you think you could incorporate those? Thanks!

[ngnpope]

There are a number of other broken links to Dive Into Python 3 that we could also fix here:

AUTHORS:    Mark Pilgrim for "Dive Into Python" (https://www.diveinto.org/python3/).
docs/intro/contributing.txt:__ https://diveinto.org/python3/table-of-contents.html
docs/intro/contributing.txt:__ https://diveinto.org/python3/unit-testing.html
docs/intro/index.txt:    .. _Dive Into Python: https://diveinto.org/python3/table-of-contents.html
docs/ref/django-admin.txt:.. _import search path: https://diveinto.org/python3/your-first-python-program.html#importsearchpath
docs/ref/templates/builtins.txt:https://diveinto.org/python3/native-datatypes.html#slicinglists for an
docs/topics/settings.txt:.. _import search path: https://diveinto.org/python3/your-first-python-program.html#importsearchpath

Fortunately, it looks as though we can replace https://diveinto.prg/python3/ with https://diveintopython3.net/.

Try using Sphinx's linkcheck to verify that the replacements work, e.g.

$ cd docs/
$ make linkcheck

(It may make sense to just do a check of all the links again as I did in #14325. Ideally we'd have added this as an scheduled check via GitHub Actions, but there are some cases which are not handled as we wish, so it requires manual checking.)

[The-Amoghavarsha]

There are a number of other broken links to Dive Into Python 3 that we could also fix here:

AUTHORS:    Mark Pilgrim for "Dive Into Python" (https://www.diveinto.org/python3/).
docs/intro/contributing.txt:__ https://diveinto.org/python3/table-of-contents.html
docs/intro/contributing.txt:__ https://diveinto.org/python3/unit-testing.html
docs/intro/index.txt:    .. _Dive Into Python: https://diveinto.org/python3/table-of-contents.html
docs/ref/django-admin.txt:.. _import search path: https://diveinto.org/python3/your-first-python-program.html#importsearchpath
docs/ref/templates/builtins.txt:https://diveinto.org/python3/native-datatypes.html#slicinglists for an
docs/topics/settings.txt:.. _import search path: https://diveinto.org/python3/your-first-python-program.html#importsearchpath

Fortunately, it looks as though we can replace https://diveinto.prg/python3/ with https://diveintopython3.net/.

Try using Sphinx's linkcheck to verify that the replacements work, e.g.

$ cd docs/
$ make linkcheck

(It may make sense to just do a check of all the links again as I did in #14325. Ideally we'd have added this as an scheduled check via GitHub Actions, but there are some cases which are not handled as we wish, so it requires manual checking.)

Thanks for the suggestion. I'll look into it. It makes more sense if the book (I've not read the book) is somewhat easy or straight forward for beginners, especially for learning topics mentioned (such as unit testing). Or should we make Python Docs ubiquitous? One good reason to prefer Docs is that it solves the problem of “getting outdated”.

And also, there are some other links which point to the list of Python books (wiki).

[felixxm]

This is an incorrect anchor. Also, links to Python's documentation should use :py: directive.

[felixxm]

@The-Amoghavarsha Do you have time to keep working on this?

[The-Amoghavarsha]

@The-Amoghavarsha Do you have time to keep working on this?

Yes.

[felixxm]

Closing due to inactivity.