On 3/19/07, Bill Baxter <[EMAIL PROTECTED]> wrote:
> I wrote a little python module to go fetch the Numpy examples from the
> scipy wiki page, parse them, and print out entries.
>
> Is there a good place on the wiki for this?
> It didn't really seem right in the cookbook, and it doesn't quite fit
>
On 3/20/07, Pierre GM <[EMAIL PROTECTED]> wrote:
On Tuesday 20 March 2007 15:29:01 Charles R Harris wrote:
> but I want
> to suggest that we run pychecker, and maybe pylint, over the python code
to
> look for errors.
I'm using Pydev w/ Eclipse that supports pylint. I usually don't have any
warn
Pierre GM wrote:
> On Tuesday 20 March 2007 18:13:09 Robert Kern wrote:
>> Pierre GM wrote:
>> Hmm. Okay, put the FORTRAN files into a library instead.
>
> Robert, Pearu, great ! Creating a library did the trick. I eventually come
> with that:
>
> def configuration(parent
On Tuesday 20 March 2007 18:13:09 Robert Kern wrote:
> Pierre GM wrote:
> Hmm. Okay, put the FORTRAN files into a library instead.
Robert, Pearu, great ! Creating a library did the trick. I eventually come
with that:
def configuration(parent_package='',top_path=None):
Pierre GM wrote:
> On Tuesday 20 March 2007 17:46:28 Robert Kern wrote:
>
>> The first file in the sources list should be the one that actually
>> implements the module, i.e. the C file generated by Pyrex. FORTRAN files
>> specified after the first one won't be processed by f2py.
>
> Mmh. I had t
> On Tuesday 20 March 2007 17:46:28 Robert Kern wrote:
>
>> The first file in the sources list should be the one that actually
>> implements the module, i.e. the C file generated by Pyrex. FORTRAN files
>> specified after the first one won't be processed by f2py.
>
> Mmh. I had to get rid of the '*
On Tuesday 20 March 2007 17:46:28 Robert Kern wrote:
> The first file in the sources list should be the one that actually
> implements the module, i.e. the C file generated by Pyrex. FORTRAN files
> specified after the first one won't be processed by f2py.
Mmh. I had to get rid of the '*.pyx' and
Pierre GM wrote:
> All,
> I'm trying to write a numpy.distutils setup.py for a pyrex module that
> involves both external C and fortran sources, and where the fortran sources
> need to be linked w/ blas and lapack. Here's what I have so far:
>
> ##
> def configura
All,
I'm trying to write a numpy.distutils setup.py for a pyrex module that
involves both external C and fortran sources, and where the fortran sources
need to be linked w/ blas and lapack. Here's what I have so far:
##
def configuration(parent_package='',top_path
On Tuesday 20 March 2007 15:29:01 Charles R Harris wrote:
> but I want
> to suggest that we run pychecker, and maybe pylint, over the python code to
> look for errors.
I'm using Pydev w/ Eclipse that supports pylint. I usually don't have any
warning from pylint about numpy. Could you be more spec
All,
I've run pychecker on some of my programs that import numpy and it issues
many warnings about numpy. Many (most?) of the warnings look bogus, but some
also look valid. I will try to work through some of these, but I want to
suggest that we run pychecker, and maybe pylint, over the python cod
On Tue, Mar 20, 2007 at 12:57:45PM -0500, Jeff Strunk wrote:
> On Tuesday 20 March 2007 11:54 am, David M. Cooke wrote:
> > On Mon, Mar 19, 2007 at 12:54:51PM -0500, Jeff Strunk wrote:
> > > Good afternoon,
> > >
> > > By request, I have installed the TracReSTMacro on the numpy, scipy, and
> > > sc
On Tuesday 20 March 2007 11:54 am, David M. Cooke wrote:
> On Mon, Mar 19, 2007 at 12:54:51PM -0500, Jeff Strunk wrote:
> > Good afternoon,
> >
> > By request, I have installed the TracReSTMacro on the numpy, scipy, and
> > scikits tracs. This plugin allows you to display ReST formatted text
> > di
Shane Holloway wrote:
> To the vector-processing masters of numpy!
>
> I'm wanting to optimize calling a list (or array) of callable
> objects. Consider the following:
>
> vCallables = numpy.array([ classes, builtin functions>])
> vParam1 = numpy.array([])
> vParam2 = numpy.array([])
> vParam3
To the vector-processing masters of numpy!
I'm wanting to optimize calling a list (or array) of callable
objects. Consider the following:
vCallables = numpy.array([])
vParam1 = numpy.array([])
vParam2 = numpy.array([])
vParam3 = numpy.array([])
vResults = numpy.array([None for e in vCallables]
On Mon, Mar 19, 2007 at 12:54:51PM -0500, Jeff Strunk wrote:
> Good afternoon,
>
> By request, I have installed the TracReSTMacro on the numpy, scipy, and
> scikits tracs. This plugin allows you to display ReST formatted text directly
> from svn.
>
> For example, http://projects.scipy.org/neuro
Hi,
I implemented an algorithm in NumPy which assumes that the input is of type
ndarray, so elementwise multiplication is done as dot(x,y), equation solving
using linalg.solve etc. I now want to modify the whole thing to accept
scipy.sparse matrices (which for instance has linsolve.spsolve instea
On 3/20/07, David Koch <[EMAIL PROTECTED]> wrote:
> And by the way - whenever I do a .__doc__ all newline characters
> are printed as "\n" in the python console ... how do I change that?
The easiest way to access the doc strings is to type help()
in the python interpreter, or ? in ipython
().
The
I will consider it Sven, I thought it was a good idea to collect everything
which had to do with Matlab -> Python in one thread.
Anyway,
Specifically, I was looking for an equivalent to Matlab's "sprand" which
allows one to create sparse normally distributed matrices. The function also
accepts
David Koch schrieb:
> Hi,
>
> naive question - how do I get an overview over everything to do with
> "sparse functionality" in SciPy 0.5.2 ... I can't find any documentation
> anywhere.
>
First of all I would recommend to start a new and properly named thread
for that
good luck,
sven
__
Hi,
naive question - how do I get an overview over everything to do with "sparse
functionality" in SciPy 0.5.2 ... I can't find any documentation anywhere.
/David
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/ma
21 matches
Mail list logo
