Skip to content

REL: Bump version to fix pypi upload #275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 14, 2017

Conversation

davidastephens
Copy link
Member

No description provided.

@davidastephens davidastephens merged commit a5026db into pydata:master Jan 14, 2017
@bashtage
Copy link
Contributor

Is this PEP-compliant versioning? FWIW I think it is possible to delete releases through the PyPi website and then to repost (even though PyPI makes it hard).

@davidastephens
Copy link
Member Author

pypi changed it to 0.3.1, I'll update the docs/release tag. I've tried to find a way to delete them and repost and it doesn't seem possible. My bad, I forgot to fetch upstream and missed a commit.

@davidastephens
Copy link
Member Author

Never mind, I think I found a way to remove and re-upload. What do you think, delete 0.3.0 and re-upload or just go straight to 0.3.1?

@bashtage
Copy link
Contributor

I would use 0.3.0 since there has been virtually no time since initial release. 0.3.1 is safer though in case someone somewhere installed 0.3.0.

@davidastephens
Copy link
Member Author

Pypi won't let me upload a file with the same name as the previous one, so we have to name it differently. I'm thinking v0.3.0.post, per PEP 440:

Some projects use post-releases to address minor errors in a final release that do not affect the distributed software (for example, correcting an error in the release notes).

If used as part of a project's development cycle, these post-releases are indicated by including a post-release segment in the version identifier

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants