summaryrefslogtreecommitdiffstats
path: root/Modules/gc_weakref.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Modules/gc_weakref.txt')
-rw-r--r--Modules/gc_weakref.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Modules/gc_weakref.txt b/Modules/gc_weakref.txt
index 2f18402..b5b9f7b 100644
--- a/Modules/gc_weakref.txt
+++ b/Modules/gc_weakref.txt
@@ -47,7 +47,7 @@ soon as we execute Python code, threads other than the gc thread can run
too, and they can do ordinary things with weakrefs that end up resurrecting
CT while gc is running.
- http://www.python.org/sf/1055820
+ https://www.python.org/sf/1055820
shows how innocent it can be, and also how nasty. Variants of the three
focussed test cases attached to that bug report are now part of Python's