Sustainably depending on the aifc module?

I have a tool that uses the stdlib aifc module, but this module is scheduled for removal from the stdlib.

Is there a version of the module on pypi that I can depend on instead?

New packages on PyPI, since 2017, are not allowed to use the names of existing standard library modules; anything you could find called aifc is legacy stuff or was never really intended to be there.

I think I saw some discussion in another section about plans for supplying packages that shim standard library content when it gets deprecated and removed. However, rather than wait: assuming you can accept the license on the standard library itself, might I suggest just copying it?

Jon does not have to use the PSF license for his code. I am pretty sure that acknowledging the PSF and its disclaimer for the copied module would be sufficient. But you are right that anyone doing so should read the PSF license.

1 Like

Thanks everyone for the answers. I’ve vendored in the module, and that seems like a reasonable solution. I also had to vendor in the chunks module, which I just appeneded to the file. I added some text to the docstring to reference the original code and license, https://github.com/Erotemic/sm64-random-assets/blob/main/sm64_random_assets/vendor/aifc.py which I think should be sufficient.

If there is any other courtesy I should perform let me know. I just want my software to be robust.