PEP-594: add legacycrypt (#1091)

pep-0594.rst

@@ -175,7 +175,7 @@ audio processing.
     cgi,3.8 (2.0\*\*),3.10,1995,no,\-
     cgitb,3.8 (2.0\*\*),3.10,1995,no,\-
     chunk,3.8,3.10,1999,no,\-
-    crypt,3.8,3.10,1994,**yes (inactive)**,"bcrypt, argon2cffi, hashlib, passlib"
+    crypt,3.8,3.10,1994,**yes (inactive)**,"legacycrypt, bcrypt, argon2cffi, hashlib, passlib"
     email.message.Message,3.3,3.10,2001,yes,email.message.EmailMessage
     email.mime,3.3,3.10,2001,yes,email.contentmanager
     email.policy.Compat32,3.3,3.10,2011,yes,email.policy.EmailPolicy
@@ -663,6 +663,7 @@ To be removed in
 Has a designated expert
    yes, but expert is currently inactive.
 Substitute
+  `legacycrypt <https://pypi.org/project/legacycrypt/>`_ (ctypes wrapper),
   `bcrypt <https://pypi.org/project/bcrypt/>`_,
   `passlib <https://pypi.org/project/passlib/>`_,
   `argon2cffi <https://pypi.org/project/argon2-cffi/>`_,
@@ -1030,8 +1031,10 @@ Most of the modules are in pure Python and can be easily packaged. Some
 depend on a simple C module, e.g. `audioop`_ and `crypt`_. Since `audioop`_
 does not depend on any external libraries, it can be shipped in as binary
 wheels with some effort. Other C modules can be replaced with ctypes or cffi.
-For example I created `legacycrypt <https://github.com/tiran/legacycrypt>`_
-with ``_crypt`` extension reimplemented with a few lines of ctypes code.
+For example I created `legacycrypt`_, which provides a full implementation of
+``crypt``. It is implemented on top of a ctypes wrapper around ``libxcrypt``
+and ``libcrypt`` instead of a C extension like the original ``_crypt``
+module.
 
 
 Discussions