On Wed, Sep 30, 2009 at 4:37 PM, David Goldsmith <d.l.goldsmith@gmail.com>wrote:
So, Ralf (or anyone), how, if at all, should we modify the status of the existing chararray objects/methods in the wiki?
Nothing has to be done until *after* Mike has committed his changes to svn. Please see my previous email for what has to happen at that point. Since Mike wrote the new docstrings it would be best if he updated the status of the wiki pages then.
Assuming you have no problem sharing them with me, Michael, I could add those docstrings you created for the existing methods,
They will show up in the wiki when they get committed to svn (presumably within a few days), so this is needless effort for the most part. If there are different changes in the wiki and svn, that will show up in the "merge" page. The ony thing that requires manual effort is if there are changes in the wiki and the object got moved in svn. Cheers, Ralf
DG
On Wed, Sep 30, 2009 at 7:20 AM, Michael Droettboom <mdroe@stsci.edu>wrote:
Ralf Gommers wrote:
On Wed, Sep 30, 2009 at 9:03 AM, Michael Droettboom <mdroe@stsci.edu <mailto:mdroe@stsci.edu>> wrote:
In the source in my working copy. Is that going to cause problems?
I
wasn't sure if it was possible to document methods that didn't yet exist in the code in the wiki.
That is fine. New functions will automatically show up in the wiki. It would be helpful though if you could mark them ready for review in the wiki (if they are) after they show up. Could take up to 24 hours for svn changes to propagate.
Thanks. Will do.
Only if you moved functions around it would be useful if you pinged Pauli after you committed them. This is a temporary problem, right now the wiki creates a new page for a moved object, and the old content (if any) has to be copied over to the new page.
All of the functions that were moved were previously without docstrings in SVN, though some had docstrings (that I just now discovered) in the wiki. This may cause some hiccups, I suppose, so I'll be sure to announce when these things get committed to SVN so I know how to help straighten these things out.
Mike
Cheers, Ralf
Mike
David Goldsmith wrote: > On Tue, Sep 29, 2009 at 10:55 AM, Michael Droettboom <mdroe@stsci.edu <mailto:mdroe@stsci.edu> > <mailto:mdroe@stsci.edu <mailto:mdroe@stsci.edu>>> wrote: > > 2) Improve documentation > > Every method now has a docstring, and a new page of routines has been > added to the Sphinx tree. > > > Um, where did you do this, 'cause it's not showing up in the doc wiki. > > DG >
------------------------------------------------------------------------
> > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org <mailto:NumPy-Discussion@scipy.org> > http://mail.scipy.org/mailman/listinfo/numpy-discussion >
-- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org <mailto:NumPy-Discussion@scipy.org> http://mail.scipy.org/mailman/listinfo/numpy-discussion
------------------------------------------------------------------------
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
-- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion