PR: Update setup.py description, metadata, links, and more #7582
Conversation
|
Hello @CAM-Gerlach! Thanks for updating the PR.
Comment last updated on July 30, 2018 at 21:38 Hours UTC |
setup.py
Outdated
| scientific packages, including NumPy, SciPy, Pandas, IPython, QtConsole, | ||
| Matplotlib, SymPy, and more. | ||
| Beyond its many built-in features, Spyder's abilities can be extended even | ||
| further via its plugin system and API. |
There was a problem hiding this comment.
This
Beyond its many built-in features, Spyder's abilities can be extended even
further via its plugin system and API.
is not quite true in Spyder 3. It'll be in Spyder 4, but not right now, so please remove it
There was a problem hiding this comment.
Removed and API and changed to via third-party plugins. to imply the "system" isn't quite so developed at the moment.
Do note that the verbatim phrase you cited currently appears in our website main page, Docs main page, Readme introduction, OpenCollective About section, (IIRC) that brochure I helped you with, various documents/proposals we've produced, etc. and others I don't remember at the moment since its part of our standard 4/5-line blurb that we use everywhere.
setup.py
Outdated
| """), | ||
| download_url=__website_url__ + "#fh5co-download", | ||
| author="The Spyder Project Contributors", | ||
| author_email="ccordoba12@gmail.com", |
There was a problem hiding this comment.
Please remove this. I don't want people to write me personal emails about Spyder.
There was a problem hiding this comment.
Yeah, good point. Removed as requested.
There was a problem hiding this comment.
we could use
admin@spyder-ide.org ? I can set forwarding to your account @ccordoba12 ?
or info@spyder-ide.org (which will arrive to admin anyway (with a label))
There was a problem hiding this comment.
It does seem most other big projects do have something there. Another alternative if you think we'll get a lot of people asking for help is our Google Group email spyderlib@googlegroups.com
If we get a high percentage of help, development, etc queries through that email it would direct them to a better place where they can be resolved publicly; on the other hand there is a chance people might send private inquiries to it (although being a Google Groups email it should be obvious that its public, and people who really care about confidentiality can easily just look you up on Github since your email is published right on your page).
There's also the fact that they would have to join the group before being able to email to it, but we could try @goanpeca 's solution to start and if you get a substantial amount of emails that could just go on the Group instead, we redirect it to the Google Groups email going forward.
There was a problem hiding this comment.
admin@spyder-ide.org ? I can set forwarding to your account @ccordoba12 ?
But that's my point: people should understand that the best way to reach us is to open an issue on Github or start a conversation on Google Groups, not to write an email.
There was a problem hiding this comment.
Another alternative if you think we'll get a lot of people asking for help is our Google Group email spyderlib@googlegroups.com
I agree with this one. @CAM-Gerlach, please use it.
There was a problem hiding this comment.
I agree with this one. @CAM-Gerlach, please use it.
Done as requested.
|
@ccordoba12 Thanks, changed as requested. |
|
Segfault on CircleCI; seems unrelated. However to my unending annoyance I can't re-run builds on CircleCI due to how the permissions are set. Is there any way you can fix the permissions to allow triggering a re-run of a failed build with normal member-level access (i.e. not direct write access) like on every other CI? |
|
@ccordoba12 Added back author email, with Google Groups as requested. |
Pull Request Checklist
modified the
spyder/defaultsdirectory, or added new icons/assetsDescription of Changes
Updates and expands our description, metadata and links in
setup.pyto make our page more compelling, easy to find, conformant and informative on PyPI (and anything else that uses the same). In particular:Hopefully this can be merged in time for 3.3.1 to greatly improve our PyPI presentation (and anything else that pulls the same data), and also since as discussed in winpython/winpython#654 WinPython will be shortly using this information to populate its own packages listings various places so we don't want it to be out of date.
Part of the broader effort coordinated in spyder-ide/spyder-docs#39
Issue(s) Resolved
Fixes #7581