-
-
Notifications
You must be signed in to change notification settings - Fork 164
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? #89
Comments
Yes, good idea. I thought we had released 0.7.0 a few months ago, but apparently not. IIRC we need to resolve the duplicate sections issue still. I can make some time to do this release. |
Great, thanks!
…On 13 March 2017 at 19:08, Ralf Gommers ***@***.***> wrote:
Yes, good idea. I thought we had released 0.7.0 a few months ago, but
apparently not. IIRC we need to resolve the duplicate sections issue still.
I can make some time to do this release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#89 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAEz67PLXLTfuEh5xeHEMdg-P2taos1Iks5rlPmCgaJpZM4MauJI>
.
|
I guess scipy docs don't build with the current master --- would need to check if the issue is here or elsewhere. |
Also, about the release, latest numpydoc release 0.6 cannot be used with sphinx git anymore as they removed some compatibility module in master last week, so I guess the next sphinx release will need a numpydoc release too. |
Also: the current github master identifies itself as 0.6.0, which is not ideal. |
Current numpydoc master + scipy master builds fine. |
I have some weird issues in scikit-learn that I don't understand. Any help with that would be much appreciated: sphinx-doc/sphinx#3768 (comment) |
For future reference: this was fixed by gh-93. |
Also, now I'd be very happy with a release of the current state, because scikit-learn builds fine! Which doesn't sound like a big thing, but making numpydoc master work for us actually was a bit tricky ;) |
I think I'll work on that right now, before life interferes again:) gh-67 has a merge conflict and an un-addressed review comment, so we can always cut another release later (not too much work). |
Okay, done: https://pypi.python.org/pypi/numpydoc/0.7.0 Somehow the readme went missing, looked into that but no luck - opened pypi/legacy#653 |
Pypi doesn't look inside the tarball or any readme files.
.
The description is whathever is in the longdescription="" parameter for
setup.py. Here, we don't have anything there.
|
The description could previously be edited on the Pypi web interface.
That's probably no longer the case.
|
Thanks @pv. Can't remember doing that last time around, but that's probably old age. Fixed now. |
Amazing!
Thank you!
Sent from phone. Please excuse spelling and brevity.
…On Jun 20, 2017 07:18, "Ralf Gommers" ***@***.***> wrote:
Thanks @pv <https://github.com/pv>. Can't remember doing that last time
around, but that's probably old age. Fixed now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#89 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAbcFj6A6YcB2yl4SQ-imMKEMZP9f1lQks5sF6qcgaJpZM4MauJI>
.
|
Amazing!
Thank you!
Sent from phone. Please excuse spelling and brevity.
On Jun 20, 2017 07:18, "Ralf Gommers" <[email protected]> wrote:
Thanks @pv <https://github.com/pv>. Can't remember doing that last time
around, but that's probably old age. Fixed now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#89 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAbcFj6A6YcB2yl4SQ-imMKEMZP9f1lQks5sF6qcgaJpZM4MauJI>
.
|
It's been over a year since the last release. I would like to use recent changes in scikit-learn, and it looks like numpy too is being built on the latest release, not on master. Could we more generally plan half-yearly releases or something, even if they're quite small?
The text was updated successfully, but these errors were encountered: