On 29 Sep 2014 21:04, "Donald Stufft" <[email protected]> wrote: > > >> On Sep 29, 2014, at 6:01 AM, Nick Coghlan <[email protected]> wrote: >> >> One caveat on this: it would potentially be convenient to have a "release" field in the wheel naming scheme, and adopt a similar approach for other binary formats like Windows installers, specifically to allow those to be updated without needing to do a full source version update. >> >> It's the silent substitution of file contents I have a fundamental problem with, not the notion of being able to publish an updated platform specific build artefact without having to bump the source release version. > > Wheel files already include the idea of a build number baked into the filename. That would be > a different filename and thus would be allowed to be uploaded even if you deleted the original > Wheel. Is there something about that which wouldn’t work or did it just slip your mind?
Slipped my mind - we generally leave it out of examples, so I managed to forget the capability was already part of the spec. That means this case should already be fully covered then, even if it requires a pre-upload file renaming. It does suggest that a short section on "Dealing with release errors" might need to find a home somewhere in PyPUG, though. Cheers, Nick. > > --- > Donald Stufft > PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA >
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
