[Numpy-discussion] Docstring standards for NumPy and SciPy

There was a lively discussion on the SciPy List before Christmas regarding establishing a standard for documentation strings for NumPy / SciPy. I am very interested in establishing such a standard. A hearty thanks goes to William Stein for encouraging the discussion. I hope it is very clear

[Numpy-discussion] Python EM Project

Hi all, I'm not sure if I am slightly out of topic, but I can't find information anywhere else. Can someone tell me where the Python EM Project has gone? The website www.pythonemproject.com that used to host it is now a bunch of ads, property of DomainDrop. Also Robert Lytle, who seemed to be "res

Re: [Numpy-discussion] Python EM Project

lorenzo bolla wrote: > Hi all, I'm not sure if I am slightly out of topic, but I can't find > information anywhere else. > Can someone tell me where the Python EM Project has gone? The website > > www.pythonemproject.com that used to host it > is now a bunch of ad

Re: [Numpy-discussion] Need help for implementing a fast clip in numpy (was slow clip)

El dt 09 de 01 del 2007 a les 23:19 +0900, en/na David Cournapeau va escriure: > Hi, > > I am finally implementing a C function to replace the current slow > implementation of clip in python as promised a few weeks ago. The idea > is to implement it as the following: > > def clip(input, min

Re: [Numpy-discussion] Exported symbols and code reorganization.

On Jan 7, 2007, at 00:16 , Charles R Harris wrote: > > That brings up the main question I have about how to break up the C > files. I note that most of the functions in multiarraymodule.c, for > instance, are part of the C-API, and are tagged as belonging to > either the MULTIARRAY_API or the

Re: [Numpy-discussion] Need help for implementing a fast clip in numpy (was slow clip)

On Wed, Jan 10, 2007 at 08:28:14PM +0100, Francesc Altet wrote: > El dt 09 de 01 del 2007 a les 23:19 +0900, en/na David Cournapeau va > escriure: > > Hi, > > > > I am finally implementing a C function to replace the current slow > > implementation of clip in python as promised a few weeks ag

Re: [Numpy-discussion] Exported symbols and code reorganization.

On 1/10/07, David M. Cooke <[EMAIL PROTECTED]> wrote: On Jan 7, 2007, at 00:16 , Charles R Harris wrote: > > That brings up the main question I have about how to break up the C > files. I note that most of the functions in multiarraymodule.c, for > instance, are part of the C-API, and are tagged

Re: [Numpy-discussion] Need help for implementing a fast clip in numpy (was slow clip)

On 10/01/07, Stefan van der Walt <[EMAIL PROTECTED]> wrote: > On Wed, Jan 10, 2007 at 08:28:14PM +0100, Francesc Altet wrote: > > El dt 09 de 01 del 2007 a les 23:19 +0900, en/na David Cournapeau va > > escriure: > > > Hi, > > > > > > I am finally implementing a C function to replace the curren

Re: [Numpy-discussion] Exported symbols and code reorganization.

On Jan 10, 2007, at 13:52 , Charles R Harris wrote: > On 1/10/07, David M. Cooke <[EMAIL PROTECTED]> wrote: On > Jan 7, 2007, at 00:16 , Charles R Harris wrote: > > > > That brings up the main question I have about how to break up the C > > files. I note that most of the functions in multiarraymo

Re: [Numpy-discussion] Need help for implementing a fast clip in numpy (was slow clip)

A. M. Archibald wrote: Why not write the algorithm in C? I did just that a while back, for Numeric. I've enclosed the code for reference. Unfortunately, I never did figure out an efficient way to write this sort of thing for all types, so it only does doubles. Also, it does a bunch of s

Re: [Numpy-discussion] Exported symbols and code reorganization.

On 1/10/07, David M. Cooke <[EMAIL PROTECTED]> wrote: On Jan 10, 2007, at 13:52 , Charles R Harris wrote: > On 1/10/07, David M. Cooke <[EMAIL PROTECTED]> wrote: On > Jan 7, 2007, at 00:16 , Charles R Harris wrote: > > > > That brings up the main question I have about how to break up the C > > f

Re: [Numpy-discussion] Exported symbols and code reorganization.

Charles R Harris wrote: > Is there a reason that the pointer PyArray_API remains valid if the > imported numpy module is garbage collected? Or is the imported module > persistent even though the returned object goes away? I assume that > python did a dlopen somewhere. There is no provision in Pyt

Re: [Numpy-discussion] Exported symbols and code reorganization.

On 1/10/07, Robert Kern <[EMAIL PROTECTED]> wrote: Charles R Harris wrote: > Is there a reason that the pointer PyArray_API remains valid if the > imported numpy module is garbage collected? Or is the imported module > persistent even though the returned object goes away? I assume that > python

Re: [Numpy-discussion] Docstring standards for NumPy and SciPy

Very nice! > """ > one-line summary not using variable names or the function name I would personally prefer that the first name contains the function (but nor arguments) - that way, when you are scrolling back in your terminal, or have a version printed out, you know what function/method the doc

Re: [Numpy-discussion] Docstring standards for NumPy and SciPy

Christian Marquardt wrote: >Very nice! > > > >>""" >>one-line summary not using variable names or the function name >> >> > >I would personally prefer that the first name contains the function (but >nor arguments) - that way, when you are scrolling back in your terminal, >or have a version

Re: [Numpy-discussion] Docstring standards for NumPy and SciPy

Christian Marquardt wrote: > Very nice! > >> """ >> one-line summary not using variable names or the function name > > I would personally prefer that the first name contains the function (but > nor arguments) - that way, when you are scrolling back in your terminal, > or have a version printed o

Re: [Numpy-discussion] Docstring standards for NumPy and SciPy

On Wed, 2007-01-10 at 17:53 -0600, Robert Kern wrote: > How are you viewing the docstrings that wouldn't associate the docstring with > the function? print .__doc__ Like so: Python 2.4 (#1, Mar 22 2005, 21:42:42) [GCC 3.3.5 20050117 (prerelease) (SUSE Linux)] on linux2 Type "help", "co

Re: [Numpy-discussion] Fwd: Advanced selection, duplicate indices, and augmented assignment

On 1/8/07, Timothy Hochberg <[EMAIL PROTECTED] > wrote: On 1/7/07, Sean R. Lynch < [EMAIL PROTECTED]> wrote: > > Travis Oliphant wrote: > > > I don't think we could make it work as he expects (and not radically > > change NumPy itself so that other operations are very different) > because > >

[Numpy-discussion] Scipy - Numpy incompatiblility when calling upon Old Numeric

Matplotlib ver 0.87.4. was the problem. An update to matplotlib-0.87.7 was all that was necessary. ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Fwd: Advanced selection, duplicate indices, and augmented assignment

On 1/10/07, Timothy Hochberg <[EMAIL PROTECTED]> wrote: On 1/8/07, Timothy Hochberg <[EMAIL PROTECTED] > wrote: > > > > On 1/7/07, Sean R. Lynch < [EMAIL PROTECTED]> wrote: > > > > Travis Oliphant wrote: > > > > > I don't think we could make it work as he expects (and not radically > > > chang

Re: [Numpy-discussion] Fwd: Advanced selection, duplicate indices, and augmented assignment

On 10/01/07, Charles R Harris <[EMAIL PROTECTED]> wrote: > You're the second or third person to recently come up with a useful application for using inplace ops with repeated indices only to be stymied by that fact that they don't actually work that way. I've been wondering if we should try to c

Re: [Numpy-discussion] Latest Array-Interface PEP

On 1/4/07, Travis Oliphant <[EMAIL PROTECTED]> wrote: > > still be used to describe a complicated block of memory to another user. Thinking of the scope "seamless data exchange between modules" my concern with this PEP is that is might be too much focused on "block of memory" rather than "access t

Re: [Numpy-discussion] Need help for implementing a fast clip in numpy (was slow clip)

Stefan van der Walt wrote: > On Wed, Jan 10, 2007 at 08:28:14PM +0100, Francesc Altet wrote: >> El dt 09 de 01 del 2007 a les 23:19 +0900, en/na David Cournapeau va >> escriure: >>> Hi, >>> >>> I am finally implementing a C function to replace the current slow >>> implementation of clip in pyt

Re: [Numpy-discussion] Docstring standards for NumPy and SciPy

Hi, Overall I like your train of thought. If we're going use a modified take on the structured text: > Use *italics*, **bold**, and `courier` if needed in any explanations > (but not for variable names and doctest code or multi-line code) I've always been a fan of using /'s for italics, and si

Re: [Numpy-discussion] Need help for implementing a fast clip in numpy (was slow clip)

Christopher Barker wrote: > > > A. M. Archibald wrote: > >> Why not write the algorithm in C? > > I did just that a while back, for Numeric. I've enclosed the code for > reference. > > Unfortunately, I never did figure out an efficient way to write this > sort of thing for all types, so it only

Re: [Numpy-discussion] installing numpy, matplotlib, scipy from source on a Mac

I am posting this message to both numpy and matplotlib mailing lists because the thread relates to both. First, Robert Kern kindly provided step-by-step instructions for Macs (PPCs and Intels) regarding how to install FROM SOURCE the packages needed to allow Python to become a viable alterna

Re: [Numpy-discussion] [Matplotlib-users] installing numpy, matplotlib, scipy from source on a Mac

Hi Chris, Robert, ...?, I'm glad you reminded me to make sure the path was right, b/c this time, I had forgotten to run the "Update Shell" command that came w/ MacPython2.4. This gave me: lrwxr-xr-x 1 root wheel 67 Jan 7 14:29 /usr/local/bin/pydoc@ - > ../../../Library/Frameworks/Python.fram