This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients brett.cannon, eric.snow, hyu, miss-islington, ncoghlan, ned.deily, paul.moore, schlamar, serhiy.storchaka, steve.dower, tim.golden, vstinner, wwqgtxx, zach.ware
Date 2019-01-08.21:23:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> 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.
Date User Action Args
2019-01-08 21:23:20vstinnersetrecipients: + vstinner, brett.cannon, paul.moore, ncoghlan, tim.golden, ned.deily, schlamar, eric.snow, zach.ware, serhiy.storchaka, steve.dower, wwqgtxx, miss-islington, hyu
2019-01-08 21:23:19vstinnersetmessageid: <>
2019-01-08 21:23:19vstinnerlinkissue35596 messages
2019-01-08 21:23:19vstinnercreate