FYI, this was discussed recently here too: https://github.com/pypa/packaging-problems/issues/74

On Wed, Oct 14, 2015 at 1:39 PM, Wes Turner <wes.turner@gmail.com> wrote:


On Oct 14, 2015 12:05 PM, "Ionel Cristian Mărieș" <contact@ionelmc.ro> wrote:
>
>
> On Wed, Oct 14, 2015 at 7:43 PM, Chris Barker <chris.barker@noaa.gov> wrote:
>>
>> some packages were unable to work with the postN suffix.
>
>
> ​Can you elaborate a bit more here?​

AFAIU, the community best practice here is to issue a new release with a bumped version number/pre/post/releasecode.

* https://www.python.org/dev/peps/pep-0440/#version-scheme
  * https://github.com/peritus/bumpversion
  * http://docs.openstack.org/developer/pbr/semver.html#changes-vs-semver-2-0

    MAJOR.MINOR.PATCH

The reasons for this are many:
* HTTP caches
* local pip/buildout pkg caches
* it is actually a different resource, with a different URI (repo,pkg,version,[pkgtype,platform,buildtags]) because it contains different files

>
>
>
> Thanks,
> -- Ionel Cristian Mărieș, http://blog.ionelmc.ro
>
> _______________________________________________
> Distutils-SIG maillist  -  Distutils-SIG@python.org
> https://mail.python.org/mailman/listinfo/distutils-sig
>


_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig