URL for tutorial urlopen example ~is dead~ doesn't want to go on the cart

[bkline]

Documentation

The first endpoint used by the tutorial to demonstrate urlopen() is dead. Attempts to connect to it raise a ConnectionResetError exception.

I can imagine at least three reasonable replacements.

1. Connect to https://example.org and print the decoded response.
2. Connect to https://httpbin.org/get and print the decoded response.
3. Connect to https://www.python.org and print the first 300 characters of the decoded response.

If I get any indication that it would be considered (ideally with an indication of which of these options would be preferred), I'd be happy to put together a PR.

Linked PRs

• gh-141412: Use reliable target URL for urllib example #141428
• [3.14] gh-141412: Use reliable target URL for urllib example (GH-141428) #141474
• [3.13] gh-141412: Use reliable target URL for urllib example (GH-141428) #141475

[bkline]

Not quite dead, as it turns out, but pretty close.

$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
utc_offset: +00:00
day_of_week: 2
day_of_year: 315
datetime: 2025-11-11T15:50:41.037437+00:00
utc_datetime: 2025-11-11T15:50:41.037437+00:00
timezone: Etc/UTC
week_number: 46
unixtime: 1762876241
raw_offset: 0
dst_until: 
dst_offset: 0
dst_from: 
dst: false
client_ip: 108.28.14.13
abbreviation: UTC
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
$ curl http://worldtimeapi.org/api/timezone/etc/UTC.txt
curl: (56) Recv failure: Connection reset by peer
# ... gave up

[StanFromIreland]

See also a previous report on Discourse: https://discuss.python.org/t/worldtimeapi-org-is-down/76815/3 where there are more suggestions for what to replace it with.

[zware]

I agree that we should make a change here. As a color for the bikeshed, what about a request to https://docs.python.org/3/ and a search for "updated"?

As a longer term solution, it might be nice to do something like add a generated file to the documentation for this purpose, where we can include anything we want, like a note of encouragement to tutorial readers, or an easter egg, etc.

[bkline]

I'm trying to log into the discussion page, but my (longstanding) credentials for python.org are being rejected. Has there been some housekeeping cleanup of older accounts? I tried the "I forgot my password" and "email me a login link" options, but neither resulted in any email messages.

[StanFromIreland]

credentials for python.org

The discourse requires a separate account.

[bkline]

Ah, good to know. It would have been helpful for the interface to tell me that there are multiple account sets for python.org, instead of leading me to expect an email message. I've created the separate account.

[bkline]

Uptime for worldtimeapi.org has dropped to under 3% for the past month.

[bkline]

Took me a while, but I finally got the joke in the issue's title change. 🤣

[bkline]

@zware I'm on board for either of your solutions. If we go with the longer-term solution (which I think is appealing enough to tackle), I'm thinking there would need to be two separate PRs: one to get the target of the new URL into production, and then a followup to modify the tutorial to use it. That way we'll be able to test. Do you agree? If so, what would you like the "note of encouragement" to say? If you think it would take too long to get that solution rolled out, let me know, and I'll start in on the simpler approach you suggested.