STINNER Victor <vstin...@redhat.com> added the comment:
> This is now resolved, and only through modifying the build scripts. Which > means I can take the existing build and republish a fixed embeddable package > without needing a new release. Since Python itself doesn't make, I'm ok to not change the Python release. But for pratical issues, would it be possible to use a different *filename*? For example, Python website rely a lot on CDN caching. It can be surprising to have two files with the same name but different content. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35596> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
