Skip to content

Commit c23ae3a

Browse files
ByronByron
committedMar 8, 2017
chore(version): 2.1.3
Just because I messed up the previous one and ... pypi allows to delete files for releases, but doesn't allow to replace them with a similarly named one. WTF? Since when is a name important anyway?
·
3.1.442.1.3
1 parent f8c31c6 commit c23ae3a

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed
 

‎VERSION

+1-1
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
2.1.2
1+
2.1.3

‎doc/source/changes.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
Changelog
33
=========
44

5-
2.1.2 - Bugfixes
5+
2.1.3 - Bugfixes
66
====================================
77

88
All issues and PRs can be viewed in all detail when following this URL:

2 commit comments

Comments
 (2)

emonty commented on Mar 8, 2017

@emonty
emonty
on Mar 8, 2017

FWIW - the reason PyPI doesn't allow replacing releases is that folks have mirrors and also config management that installs things. If one of those people had gotten unlucky enough to have installed 2.1.2 and then PyPI had allowed replacing it, there would have been no way of that user getting upgraded to the working 2.1.3 other than a manual force reinstall. In this particular case, the change you needed to make is obviously innocuous, but there have been cases in the past of there being real legit breaking changes that sneak out in a release that folks have wanted to just replace and it has actually screwed folks.

Mostly just an FYI as to why PyPI doesn't allow replacement. Once a tag or release is out in the wild, it's out there. Rolling forward, as you did, is the safest and most effective way to ensure that people not only get the right thing but get it without being bizarrely broken in the process.

Byron commented on Apr 9, 2017

@Byron
Byron
on Apr 9, 2017
MemberAuthor

@emonty Thanks for pointing it out in such great detail - I see entirely why releases must be read-only after publishing them. However, in my case I was allowed to delete the file associated with a release nonetheless, which caused more trouble down the line as I was not allowed to replace the file (at least not via command-line tools). The system seems inconsistent, which is why I was upset :).

Please sign in to comment.