Skip to content
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

Release 0.2.0 #60

Merged
merged 3 commits into from
Apr 12, 2016
Merged

Release 0.2.0 #60

merged 3 commits into from
Apr 12, 2016

Conversation

opalmer
Copy link
Owner

@opalmer opalmer commented Feb 7, 2016

No description provided.

@opalmer opalmer self-assigned this Feb 7, 2016
@opalmer opalmer added this to the 0.2.0 milestone Feb 7, 2016
@codecov-io
Copy link

Current coverage is 96.67%

Merging #60 into master will not affect coverage as of a0ab112

Powered by Codecov. Updated on successful CI builds.

@opalmer
Copy link
Owner Author

opalmer commented Apr 12, 2016

@exvito, take a look. Once this build finishes this PR can merge and I'll make a release with your code tomorrow (it will take a while for AppyVeyor to finish). Thanks again!

@opalmer opalmer merged commit e860c78 into master Apr 12, 2016
@exvito
Copy link
Contributor

exvito commented Apr 12, 2016

That's great. Thanks.
I will continue contributing but very busy this week. Expect feedback soon.

@exvito
Copy link
Contributor

exvito commented Apr 15, 2016

Quick question (pardon my ignorance): shouldn't this merge lead to a release on PyPI?

@opalmer opalmer deleted the release_0_2_0 branch April 15, 2016 22:12
@opalmer
Copy link
Owner Author

opalmer commented Apr 15, 2016

Yes and no. I make releases by running tools\release.py which then downloads the wheels from AppVeyor, uploads them to PyPi and creates the release on GitHub too. However, for one of the wheels PyPi responded with an internal server error so I ended uploading the rest by hand except for the source zip (forgot about it since we have wheels).

0.2.0 has been up on PyPi for four but after looking at it again today, pip itself didn't see it. Looks like pip will ignore any release that does not contain a source zip file even if there are wheels available and previous releases are hidden.

Sorry about that....

@exvito
Copy link
Contributor

exvito commented Apr 16, 2016

Thanks for the clarification. I looks fine now: I just pip installed and it brought in 0.2.0. :)

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

Successfully merging this pull request may close these issues.

3 participants