-
Notifications
You must be signed in to change notification settings - Fork 15
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
Move WebbPSF docs to pythonhosted.org #20
Comments
I moved the poppy docs to the pythonhosted.org site that is integrated with PyPI. See https://pythonhosted.org/poppy/ . Whenever we make a new release of webbpsf we should certainly do the same with that. Do you know of any specific advantages of readthedocs over pythonhosted? |
I need to do some research, but the thing I liked about readthedocs is that you can have new commits on Do you know if that's possible with PyPI/pythonhosted? |
Pythonhosted is manual, whenever you upload a new package version to pypi. It doesn't automatically track master. I agree that readthedocs would be nice for the github tracking. I even started to create an account at one point to try to figure out how to set this up, but got distracted before I was able to carry through on that. There exist projects for both poppy and webbpsf projects on readthedocs but they're broken and not building right now. Let me see if I can grant you access - do you have an account for readthedocs yet? On Oct 31, 2014, at 1:43 PM, Joseph Long <notifications@github.commailto:notifications@github.com> I need to do some research, but the thing I liked about readthedocs is that you can have new commits on master trigger a build of the docs. That way if we have a development version, we can actually have docs online for that version AND the released version. Do you know if that's possible with PyPI/pythonhosted? — |
Just made one! Same username as here: josePhoenix |
OK, I've just added you to the two projects on readthedocs. |
Per our discussion (and me bugging the ReadTheDocs folks) it looks like the service isn't mature enough to handle scientific python packages. Let's do pythonhosted.org for WebbPSF when we make a new release. |
Uploaded the latest built from my docs_refresh branch. Will need to update when we actually release 0.3, but that's just a matter of uploading a new .zip file. |
I noticed that the current docs at http://www.stsci.edu/~mperrin/software/webbpsf/ are being served with incorrect encoding information. (Note the appearance of the paragraph links that appear when mousing over headings.)
While we could probably fix that with a
.htaccess
change, it might be worth moving the docs to a service like readthedocs.org (which AstroPy) uses. Then we can build docs from the development head automatically, as well as from the latest stable release.The text was updated successfully, but these errors were encountered: