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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Pypi with new README.rst #62

Closed
gijzelaerr opened this Issue Mar 31, 2016 · 6 comments

Comments

Projects
None yet
3 participants
@gijzelaerr
Member

gijzelaerr commented Mar 31, 2016

since it looks like 馃挬 at the moment on pypi

https://pypi.python.org/pypi/python-casacore/2.1.2

@gijzelaerr gijzelaerr self-assigned this Mar 31, 2016

@gijzelaerr gijzelaerr removed their assignment Mar 13, 2017

@shibasisp

This comment has been minimized.

Contributor

shibasisp commented Apr 11, 2017

How this can be done? I think it's already written in rst.

@tammojan

This comment has been minimized.

Contributor

tammojan commented Apr 11, 2017

It is indeed currently already in RST. I changed the ticket name to reflect that somehow we need to update pip.

@tammojan tammojan changed the title from rewrite readme in rst to Update Pypi with new README.rst Apr 11, 2017

@shibasisp

This comment has been minimized.

Contributor

shibasisp commented May 7, 2017

Looks like there was a small indentation error in the README.rst, because of which PyPI wasn't able to render the rST into HTML. I have pushed a commit to my fork. But I don't know how can I modify the README.rst of tag v2.1.2

@tammojan

This comment has been minimized.

Contributor

tammojan commented May 7, 2017

You cannot change anything in a tag, because it has been released. We should look at releasing another version soon. Or create a test tag just for this.

@shibasisp

This comment has been minimized.

Contributor

shibasisp commented May 7, 2017

should I send a PR so that it will render correctly in the next release?

@tammojan

This comment has been minimized.

Contributor

tammojan commented May 7, 2017

Yes please.

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