Message333253
| 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 | <1546982599.3.0.685202188228.issue35596@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> 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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-01-08 21:23:20 | vstinner | set | recipients: + 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:19 | vstinner | set | messageid: <1546982599.3.0.685202188228.issue35596@roundup.psfhosted.org> |
| 2019-01-08 21:23:19 | vstinner | link | issue35596 messages |
| 2019-01-08 21:23:19 | vstinner | create | |