> On Dec 1, 2014, at 7:40 PM, Ben Finney <[email protected]> wrote: > > Donald Stufft <[email protected]> writes: > >> Can you go into some detail about what the use case is for having >> something other than the latest version be the default version shown? > > Not much detail needed: The package version was released before it was > realised that it breaks many people's systems on upgrade. > > To address this, without re-writing history, it is desirable that the > default version be an earlier, known-working version. > > I didn't realise that package fetch-and-install tools fail to honour > that setting. So now I don't have a good solution.
You can always remove a version from PyPI if it’s breaking things for people. That’ll stop *new* people from being broken. You can also of course revert whatever changes people are being broken by and upload that as a new version. Generally it’s hard to go “backwards” and once you release a bit of software assume that it’s released and just increment versions again. --- 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
