Mailman 3 June 2009 - SciPy-Dev

stats confusion
by Neal Becker June 17, 2009

June 17, 2009

I'm still finding stats usage confusing. The doc (http://docs.scipy.org:80/doc/scipy/reference/generated/scipy.stats.chi2.htm…) says: chi2.cdf(x,df,loc=0,scale=1) : And even has an example: prb = chi2.cdf(x,df) But if df is given as keyword: scipy.stats.chi2.cdf(1, df=2) ERROR: An unexpected error occurred while tokenizing input The following traceback may be corrupted or invalid The error message is: ('EOF in multi-line statement', (1331, 0)) --------------------------------------------------------------------------- TypeError Traceback (most recent call last) /home/nbecker/globalstar/<ipython console> in <module>() /usr/lib64/python2.6/site-packages/scipy/stats/distributions.pyc in cdf(self, x, *args, **kwds) 623 if any(cond): #call only if at least 1 entry 624 goodargs = argsreduce(cond, *((x,)+args)) --> 625 place(output,cond,self._cdf(*goodargs)) 626 if output.ndim == 0: 627 return output[()] TypeError: _cdf() takes exactly 3 arguments (2 given) What's going on here? Do stats not accept keyword args as per normal python usage?

3 5

Reminder: weekly NumPy Doc Sum. Mar. Skypecon
by David Goldsmith June 17, 2009

June 17, 2009

Hi, folks. Just a reminder that I will be hosting a Skype conference call this Thursday, June 18, at 10:30am EDT to "check-in" re: the NumPy Doc Summer Marathon. Though I should be able to add people at the last minute, it would help me out if you could let me know your Skype ID in advance, if you anticipate joining in. (Skype is free and easy to use, but if you don't Skype and don't want to and definitely want to participate, let me know the phone number you'll be calling in from, please.) Talk to you Thursday! David Goldsmith Technical Editor Olympia, WA

1 0

Guide to NumPy/SciPy Documentation and Sphinx
by Daniel Jensen June 15, 2009

June 15, 2009

I've noticed that a lot of code in SciPy is using the following format for different sections: :Parameters: func : callable func(x,*args) The objective function to be minimized. whereas the Style Guideline page at http://projects.scipy.org/numpy/wiki/CodingStyleGuidelines#docstring-standa… section titles like the following: Parameters ---------- x : array-like array to fourier transform. Without some custom sphinx extension to handle the second example, Sphinx spits out an "Unexpected section title" error message. Should people writing scikits or other code that may some day make it into NumPy/SciPy follow one convention over the other? If we should follow the first convention it may be useful to start a wiki page that explains how to get Sphinx setup correctly to process these docstrings. -Daniel Jensen

2 2

Re: [SciPy-dev] Guide to NumPy/SciPy Documentation and Sphinx
by David Goldsmith June 15, 2009

June 15, 2009

--- On Mon, 6/15/09, Daniel Jensen <danielsjensen1(a)gmail.com> wrote: > I've noticed that a lot of code in > SciPy is using the following format for different sections: > > :Parameters: > > func : callable func(x,*args) > The objective function to be minimized. > > whereas the Style Guideline page at http://projects.scipy.org/numpy/wiki/CodingStyleGuidelines#docstring-standa… > encourages section titles like the following: > > Parameters > ---------- > x : array-like > array to fourier transform. > > Without some custom sphinx extension to handle the second > example, Sphinx spits out an "Unexpected section > title" error message. Should people writing scikits > or other code that may some day make it into NumPy/SciPy > follow one convention over the other? If we should follow > the first convention it may be useful to start a wiki page > that explains how to get Sphinx setup correctly to process > these docstrings. First, thanks Daniel, for calling our attention to this. However, I'm confused - you state: "Without some custom sphinx extension to handle the _second_ example, Sphinx spits out an "Unexpected section title" error message...If we should follow the _first_ convention it may be useful to start a wiki page that explains how to get Sphinx setup correctly to process these docstrings." Are you saying that presently, Sphinx (or at least the way we have it configured) is not completely compatible with _either_ of these conventions (albeit with the nature of the incompatibility differing between the two)? Is there not a third option we could adopt which would be Sphinx-compatible "off the shelf"? Thanks again, DG > > > -Daniel Jensen > > > -----Inline Attachment Follows----- > > _______________________________________________ > Scipy-dev mailing list > Scipy-dev(a)scipy.org > http://mail.scipy.org/mailman/listinfo/scipy-dev >

2 1

Sorry, disregard "Are the rst's intended to be "definitive"?"
by David Goldsmith June 14, 2009

June 14, 2009

Sorry, I realized the proper place for this is ndarray's doc string. Sorry for the noise. DG --- On Sun, 6/14/09, David Goldsmith <d_l_goldsmith(a)yahoo.com> wrote: > From: David Goldsmith <d_l_goldsmith(a)yahoo.com> > Subject: [SciPy-dev] Are the rst's intended to be "definitive"? > To: scipy-dev(a)scipy.org > Date: Sunday, June 14, 2009, 12:50 PM > > For example, should numpy-docs/reference/arrays.ndarray.rst > clearly state, w/ an example, that the ndarray constructor > does type-check its input and enforce the data type > uniformity? > > DG > > > > _______________________________________________ > Scipy-dev mailing list > Scipy-dev(a)scipy.org > http://mail.scipy.org/mailman/listinfo/scipy-dev >

1 0

Are the rst's intended to be "definitive"?
by David Goldsmith June 14, 2009

June 14, 2009

For example, should numpy-docs/reference/arrays.ndarray.rst clearly state, w/ an example, that the ndarray constructor does type-check its input and enforce the data type uniformity? DG

1 0

Re: [SciPy-dev] Created Doc Marathon Project at code.google
by David Goldsmith June 11, 2009

June 11, 2009

--- On Thu, 6/11/09, Pauli Virtanen <pav(a)iki.fi> wrote: > Wed, 10 Jun 2009 22:47:16 -0700, David Goldsmith > kirjoitti: > > Hi, folks. So, you may recall I expressed want > of a "ticketing system," > > primarily for myself, for NumPy Doc Wiki tasks. > It was suggested I just > > piggy-back on the pydocweb Project @ code.google, but > after a > > false-start there, > > Sorry, I'm unfortunately still a bit busy, so given the > time difference, > I didn't manage to reply to your previous post about this > in time. NP > > and I configured the issues > > tracker so that only owners and members can submit > issues (at least I > > hope so). > > But, I certainly want to make it available as a > resource for > > others to use in the advancement of the Marathon, so > if you want to be > > added as a member, just let me know. > > Is this a necessary restriction? The google system seems > fairly resilient > against spam, and it might be easier for people to > participate if > everyone could submit requests and suggestions. Actually, when I went back to change it, I noted that all I'd apparently done was restrict to the availability of my custom templates (which suggests that non-members still could have submitted issues, just not as "easily"), but I went ahead and eliminated even that restriction - go wild, everyone! DG

1 0

Created Doc Marathon Project at code.google
by David Goldsmith June 11, 2009

June 11, 2009

Hi, folks. So, you may recall I expressed want of a "ticketing system," primarily for myself, for NumPy Doc Wiki tasks. It was suggested I just piggy-back on the pydocweb Project @ code.google, but after a false-start there, I realized, why not just start a new Project expressly for the Marathon? So I did: http://code.google.com/p/numpydocmarathon09/. I - d.l.goldsmith(a)gmail.com - am the owner, and I configured the issues tracker so that only owners and members can submit issues (at least I hope so). But, I certainly want to make it available as a resource for others to use in the advancement of the Marathon, so if you want to be added as a member, just let me know. (Pauli or anyone: to be added as a Project member, does one need a gmail, i.e., Google, account? If yes, does any one find this prohibitively restrictive?) DG

3 2

Re: [SciPy-dev] tanh(j*pi/2)
by David Goldsmith June 11, 2009

June 11, 2009

No, this is what I meant: >>> N.allclose([N.tanh(N.pi*1j/2)],[N.inf]) False >>> N.allclose([1/N.tanh(N.pi*1j/2)],[0.]) True So in this case, one does need to reciprocate first (or am I using N.allclose wrong in the first example?) I should probably 'Note' this tanh's doc (and other transcendentals that may exhibit this behavior). DG --- On Tue, 6/9/09, Robert Kern <robert.kern(a)gmail.com> wrote: > From: Robert Kern <robert.kern(a)gmail.com> > Subject: Re: [SciPy-dev] tanh(j*pi/2) > To: "SciPy Developers List" <scipy-dev(a)scipy.org> > Date: Tuesday, June 9, 2009, 10:10 PM > On Wed, Jun 10, 2009 at 00:06, David > Goldsmith<d_l_goldsmith(a)yahoo.com> > wrote: > > > > Understood, thanks. Just curious: can N.allclose be > used w/ N.inf, or does one need to reciprocate first? > > In [1]: allclose([inf], [inf]) > Out[1]: True > > The infs are handled specially. > > -- > Robert Kern > > "I have come to believe that the whole world is an enigma, > a harmless > enigma that is made terrible by our own mad attempt to > interpret it as > though it had an underlying truth." > -- Umberto Eco > _______________________________________________ > Scipy-dev mailing list > Scipy-dev(a)scipy.org > http://mail.scipy.org/mailman/listinfo/scipy-dev >

5 4

Reminder: Doc Marathon Skypecon at 4:30 pm EDT
by David Goldsmith June 10, 2009

June 10, 2009

Skype d.l.goldsmith at that time to join. Oh, and it's 1:09 pm EDT now.

1 0