3 ms·

They're removing a lot more than crypt. Also, telnet, smtp, nntp, various file format support, xdr, and so on. Crypt is particularly painful, since removing i

• acdha 3y ago
  > Crypt is particularly painful, since removing it will effectively cryptoshred user password databases. What do you mean by that? Anyone interacting with passwords on Linux, macOS, etc. has needed to use PAM anyway for decades. If you are building some kind of network app and just tossing passwords through crypt() you are going to have a much worse time on a security audit than you will installing a single python module.
• fullspectrumdev 3y ago
  The loss of telnet and crypt is going to mean I have to version pin a lot of older code. I should look into which file formats are going away, I had some stuff that relied heavily on uuencode/decode (along with telnetlib) for bootstrapping file transfers into older systems…
  • viraptor 3y ago
    Or just use an external module from pypi. Python stdlib doesn't have a monopoly on the bits you're using.
    • fullspectrumdev 3y ago
      That adds extra steps, I prefer (where possible) sticking with just the standard library for portability when working with other people’s horrendously broken systems that may not have outbound internet access.
      • viraptor 3y ago
        You can vendor it in your app yourself. That skips the internet requirements.