4 ms·
The only thing I worry about is the uu module. Even though 99.99% of people will never use it, there are also probably literally millions if not billions of pie
by Alex3917 7y ago
The only thing I worry about is the uu module. Even though 99.99% of people will never use it, there are also probably literally millions if not billions of pieces of content that are encoded using that standard. I realize it's only a few lines of code, but from an archival perspective it seems like there's something distasteful about making it harder for future generations to access content that may have historical value. At least send a quick note to the library of congress or the archivist community first to get an idea of to what extent this stuff is getting used.
- roblabla 7y agoThis module is pure python. It looks like if people rely on it, they could easily put the code in a pypi module, and maintain it there. It doesn't really make sense to keep it in the core if it has no dedicated maintainers.
- takeda 7y agoThat code doesn't need any maintainers, it is not like UU encoding is evolving or really complex.
- guitarbill 7y agoThat's a bit dramatic. Our knowledge of the encoding doesn't go away because Python removed support. Old versions will continue to work. The code is preserved in VCS. And finally, you/someone can release a 3rd party module to PyPI to fill the gap.
- naniwaduni 7y agoThe useful functionality (encoding/decoding) is covered by binascii, which uu in fact uses internally. What the uu module proper provides is a pair of awful file-to-file interfaces. Default to spitting the decoded file directly to disk at with the name in its header is, uh, questionable.
- owaislone 7y agoIsn't it just being removed from the standard library? It can still exist on pypi especially if it is as important as you suggest, someone will definitely host it on pypi.
- masklinn 7y agoAs noted in the PEP, the uu codec itself is in `binascii` and not moving anywhere. `uu` is just a (pretty awful) high-level interface.