Christopher Barker wrote:
David Cournapeau wrote:
Not exactly, although it prevents from building Atlas for 64 bits. The
main issue is gcc/VS interoperabilities, especially for gfortran.
I thought you didn't need fortran for numpy?
No, but you need it for Scipy. And we have always produced
changes will be the one to build scipy and
matplotlib against (I will then focus on releasing scipy 0.8.0).
1.4.0 would is then considered as a broken release (I am removing the
files from sourceforge).
cheers,
David
___
NumPy-Discussion mailing list
On Sat, Feb 6, 2010 at 10:29 PM, josef.p...@gmail.com wrote:
On Sat, Feb 6, 2010 at 8:07 AM, Francesc Alted fal...@pytables.org wrote:
A Saturday 06 February 2010 13:17:22 David Cournapeau escrigué:
On Sat, Feb 6, 2010 at 4:07 PM, Travis Oliphant oliph...@enthought.com
wrote:
I think
On Sat, Feb 6, 2010 at 10:36 PM, Darren Dale dsdal...@gmail.com wrote:
I don't understand why there is any debate about what to call a
release that breaks ABI compatibility.
Because it means datetime support will come late (in 2.0), and Travis
wanted to get it early in.
David
installers
for now on windows2,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
(but keeping the metadata structure), and by regenerating the
few cython files with Cython 0.12.1, the ABI is kept compatible (at
least as far as scipy constitutes a reasonable test).
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
and the dependency.
There are actually Mac binaries, just not for the last version:
http://pypi.python.org/pypi/scikits.audiolab/0.10.0
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
.
Maybe we should seriously think about working on a major overhaul of
NumPy to allow changes while keeping ABI compatibility, then. But
after finishing the transition to Py3k - maybe Pauli and Chuck would
have a better idea on the exact path forward w.r.t Py3k transition
timeline.
cheers,
David
On Thu, Feb 4, 2010 at 4:37 PM, Travis Oliphant oliph...@enthought.com wrote:
On Feb 4, 2010, at 12:59 AM, Charles R Harris wrote:
On Wed, Feb 3, 2010 at 11:48 PM, Travis Oliphant oliph...@enthought.com
wrote:
On Feb 2, 2010, at 11:59 PM, David Cournapeau wrote:
Travis Oliphant wrote
signal.
Peter Wang has an example using Chaco and ETS:
https://svn.enthought.com/enthought/browser/Chaco/trunk/examples/advanced/spectrum.py
David Cournapeau has written a libsndfile wrapper:
http://www.ar.media.kyoto-u.ac.jp/members/david/softwares/audiolab/sphinx/index.html
calls to API which are not safe. I have no
idea whether it is possible, but that's something to keep in mind once
we start a major overhaul.
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo
drawback is the dependency on libsndfile.
You can play numpy arrays with the play function (it uses ALSA) - having
a record function would be good as well, but I never took the time to
implement it (hint, hint :) ).
cheers,
David
___
NumPy-Discussion
On Thu, Jan 28, 2010 at 3:11 PM, David Cournapeau da...@silveregg.co.jp wrote:
Jankins wrote:
Yes. I am using scipy.sparse.linalg.eigen.arpack.
The exact output is:
/usr/local/lib/python2.6/dist-packages/scipy/sparse/linalg/eigen/arpack/_arpack.so
I need the output of ldd on this file
);
}
But I am not sure whether it would cause some issues if you do this
and then import the numpy C API (which is mandatory before using any C
functions from numpy). I know the python import system has some dark
areas, I don't know if that's one of them or not.
cheers,
David
On Thu, Feb 4, 2010 at 2:16 AM, Christopher Barker
chris.bar...@noaa.gov wrote:
David Cournapeau wrote:
Just so that there is no confusion: it is only about removing it for
1.4.x, not about removing datetime altogether. It seems that datetime in
1.4.x has few users,
Of course it has few
altogether
for 1.4.x as a solution. At least in my case, it is mostly justified
by the report from David Huard that the current datetime support is
still a bit too experimental to be useful for people who rely on
binaries.
Are there any objections ? I know in particular Travis was against it
when
whether it is available ?
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
version is updated ?
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
as the PyArray_ArrFuncs is concerned, that's the datime type
which broke the ABI, not the metadata. Does the metadata support needs
anything else besides the metadata pointer in the descriptor structure ?
David
___
NumPy-Discussion mailing list
NumPy-Discussion
Robert Kern wrote:
On Tue, Feb 2, 2010 at 21:08, David Cournapeau da...@silveregg.co.jp wrote:
Robert Kern wrote:
On Tue, Feb 2, 2010 at 20:23, Neil Martinsen-Burrell n...@wartburg.edu
wrote:
This is useful feature for more than just datetime
support and should be complete and useful
On Tue, Feb 2, 2010 at 9:23 PM, Neil Martinsen-Burrell n...@wartburg.edu
wrote:
On 2010-02-02 19:53 , David Cournapeau wrote:
Travis Oliphant wrote:
I think we just signal the breakage in 1.4.1 and move forward. The
datetime is useful as a place-holder for data. Math on date-time arrays
On Wed, Feb 3, 2010 at 12:23 PM, David Cournapeau da...@silveregg.co.jp wrote:
Sorry, my question was badly worded: besides the metadata pointer, is
there any other change related to the metadata infratructure which may
potentially change changes the publicly exported structures ? I wonder
Robert Kern wrote:
On Tue, Feb 2, 2010 at 22:46, David Cournapeau courn...@gmail.com wrote:
On Wed, Feb 3, 2010 at 12:23 PM, David Cournapeau da...@silveregg.co.jp
wrote:
Sorry, my question was badly worded: besides the metadata pointer, is
there any other change related to the metadata
Travis Oliphant wrote:
On Feb 2, 2010, at 11:46 PM, David Cournapeau wrote:
On Wed, Feb 3, 2010 at 12:23 PM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp wrote:
Sorry, my question was badly worded: besides the metadata pointer, is
there any other change related
Travis Oliphant wrote:
On Feb 2, 2010, at 8:53 PM, David Cournapeau wrote:
Travis Oliphant wrote:
I think we just signal the breakage in 1.4.1 and move forward. The
datetime is useful as a place-holder for data. Math on date-time
arrays
just doesn't work yet.I don't think
?
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
confusing than returning empty
arrays, though - maybe there is a usecase I don't know about.
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Charles R Harris wrote:
In this case I would expect an empty input to be a programming error and
raising an error to be the right thing.
Ok, I fixed the code in the trunk to raise a ValueError in that case.
Changing to return an empty array would be easy,
cheers,
David
), so just build
for ppc/x86. I never bothered with ppc64, and I think we can actually
give up on ppc soon.
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
of it.
That is, let's say my 4D array is A, I'd like to know
A[ndindex].shape
without actually creating A.
ndindex should support all numpy constructions (integer, boolean,
array, slice, ...). I am guessing something already exists to do this,
but I just can't put my finger on it.
Thanks.
David
On Fri, Jan 29, 2010 at 12:10 PM, josef.p...@gmail.com wrote:
On Fri, Jan 29, 2010 at 11:49 AM, David Huard david.hu...@gmail.com wrote:
Hi,
I have a 4D array with a given shape, but the array is never
actually created since it is large and distributed over multiple
binary files. Typical
it out there so it gets used, but for the
moment I think potential users are still those who compile from the
dev. tree anyway.
Thanks for all the hard work that has been put into this,
David
On Thu, Jan 28, 2010 at 7:58 PM, David Cournapeau da...@silveregg.co.jp wrote:
Charles R Harris wrote
For the record, here is what I came up with.
import numpy as np
def expand_ellipsis(index, ndim):
Replace the ellipsis, real or implied, of an index expression by slices.
Parameters
--
index : tuple
Indexing expression.
ndim : int
Number of dimensions of
Charles R Harris wrote:
On Thu, Jan 28, 2010 at 12:33 AM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp wrote:
Because Travis was against it when it was suggested last september or
so. And removing in 1.4.x a feature introduced in 1.4.0 is weird
Bruce Southey wrote:
On Tue, Jan 26, 2010 at 11:02 PM, David Cournapeau
da...@silveregg.co.jp wrote:
Charles R Harris wrote:
Whatever we do, it would be good to figure out some way to avoid this
problem in the future. We could hide access to the array, for instance.
But again, that would
, which would just have a different ABI
number than 1.4.0, without anything else.
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Alan G Isaac wrote:
On 1/27/2010 7:57 PM, David Cournapeau wrote:
Guido explicitly asked not to break compatibility while staying under
py3k, so we should try to do it once numpy has been ported to py3k (e.g.
if numpy 1.5 still is not py3k compatible, do a 1.6 before a 2.0 -
iterate
.
Would the change in the ABI numer prevent some other programs that use
numpy and are compiled against an older numpy, for me mainly
matplotlib, from running?
Not some, *all* of them (as long as they use the numpy C extension, that
is - pure python are obviously unaffected).
David
Alan G Isaac wrote:
On 1/27/2010 7:57 PM, David Cournapeau wrote:
Guido explicitly asked not to break compatibility while staying under
py3k, so we should try to do it once numpy has been ported to py3k (e.g.
if numpy 1.5 still is not py3k compatible, do a 1.6 before a 2.0 -
iterate
your platform details (i.e. OS, compiler, 32 vs 64
bits, the output of scipy.show_config()). This is needed to isolate the
problem,
cheers.
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy
/site-packages/scipy/sparse/linalg/eigen/arpack/_arpack.so
(you are using linalg.eigen from scipy.sparse, right ?).
Ideally, if the matrix is not too big, having the matrix which crashes
scipy is most helpful,
thanks,
David
___
NumPy-Discussion
Alan G Isaac wrote:
On 1/27/2010 8:56 PM, David Cournapeau wrote:
one could make the argument that releasing the API would avoid
having to port numpy twice (first to py3k with say numpy 1.5.0, then
to the new API for numpy 2.0). But I am not sure it is a big change in
practice ?
OK, I
the total available
memory, so something like matrices with ~ 1e7/1e8 entries on current
desktop computers)
- you need more than a few eigenvalues, or not just the
biggest/smallest ones
cheers,
David
___
NumPy-Discussion mailing list
NumPy
Charles R Harris wrote:
On Wed, Jan 27, 2010 at 6:20 PM, David Cournapeau da...@silveregg.co.jp
mailto:da...@silveregg.co.jp wrote:
josef.p...@gmail.com mailto:josef.p...@gmail.com wrote:
Can we/someone add a warning on the front page http://scipy.org/
(maybe under news
Charles R Harris wrote:
On Wed, Jan 27, 2010 at 11:39 PM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp wrote:
Charles R Harris wrote:
On Wed, Jan 27, 2010 at 6:20 PM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp
this because the offending commit was
4000 LOC, and it would have been very easy to find this were the code
committed as a set of small self-contained commits.
thanks,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http
Charles R Harris wrote:
Thinking a bit more, for 1.4.1 I think we should just remove the function.
This was rejected last time I suggested it, though :)
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org
this problem in the future: no more naked structures,
much cleaner/leaner headers to avoid accidental reliance on specific
private binary layouts, etc...
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo
Matthieu Brucher wrote:
How do you write the site.cfg accordingly?
I don't think you can do that through site.cfg,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
of a perfect scenario for generalized ufuncs as it
requires operations over an entire dimension (the max operation).
Cheers,
David
On 21-Jan-10, at 7:30 PM, Warren Weckesser wrote:
David,
I haven't tried creating a ufunc before, so I can't help you with
that, but since you are working
, the 'print' default is slightly worse than the previous 'ignore'.
Personally, I don't see great value in the invalid value encountered
reports that are appear every time a nan is generated...
I thought it was agreed that the default would be changed to warnings
for 1.5.0 ?
cheers,
David
On Thu, Jan 21, 2010 at 8:36 PM, Nils Wagner
nwag...@iam.uni-stuttgart.de wrote:
On Thu, 21 Jan 2010 10:04:56 +0900
David Cournapeau da...@silveregg.co.jp wrote:
Nils Wagner wrote:
Hi all,
I found a strange problem when I try to import numpy
python -v
import numpy
...
dlopen(/data/home
On Fri, Jan 22, 2010 at 12:06 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Thu, Jan 21, 2010 at 3:03 AM, David Cournapeau courn...@gmail.com
wrote:
On Thu, Jan 21, 2010 at 6:23 PM, Pauli Virtanen pav...@iki.fi wrote:
Wed, 20 Jan 2010 16:57:01 -0500, Darren Dale wrote:
[clip
On Fri, Jan 22, 2010 at 7:14 AM, David Cournapeau courn...@gmail.com wrote:
On Fri, Jan 22, 2010 at 12:06 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Thu, Jan 21, 2010 at 3:03 AM, David Cournapeau courn...@gmail.com
wrote:
On Thu, Jan 21, 2010 at 6:23 PM, Pauli Virtanen pav
the signature calls for?
Thanks,
David
char *logsumexp_signature = (i)-();
/**begin repeat
#TYPE=LONG,DOUBLE#
#typ=npy_long, npy_double#
#EXPFUN=expl, exp#
#LOGFUN=logl, log#
*/
/*
* This implements the function
*out[n] = sum_i { in1[n, i] * in2[n, i] }.
*/
static void
@t
on Centos to get your program loaded with the
debug version of glibc,
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
*.
search_static_first is inherently fragile - using the linker to do this
is much better (with -WL,-Bshared/-Wl,-Bstatic flags).
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
unicode, and numpy is built against a python
using 2-bytes/char). Anyway, very unlikely to be caused by r8077.
I suspect some mixedup in your build - can you build numpy r8077 from
scratch, after having removed installed and build directories ?
David
numpy is built with debug
symbols - having -g in both CFLAGS and LDFLAGS) ?
Having it happening inside the dlopen call is a bit weird, I can't see
what could cause it,
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http
Hi, Wayne.
They're not nearly as structured, but for the time being
(indefinitely? unless a volunteer steps forward to build something for
us more closely resembling the GMI), you could use the numpy and scipy
doc Wiki Milestones pages:
http://docs.scipy.org/numpy/Milestones/
it, and maybe run the whole test suite (as indicated in the ATLAS
installation notes).
Note that you can use the Accelerate framework on mac os x, this is much
easier to get numpy working on mac,
cheers,
David
___
NumPy-Discussion mailing list
NumPy
On Sat, Jan 16, 2010 at 4:30 PM, Dag Sverre Seljebotn
da...@student.matnat.uio.no wrote:
Charles R Harris wrote:
On Fri, Jan 15, 2010 at 8:56 AM, David Cournapeau courn...@gmail.com
mailto:courn...@gmail.com wrote:
On Fri, Jan 15, 2010 at 11:46 PM, Ralf Gommers
ralf.gomm
On Sat, Jan 16, 2010 at 4:57 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Fri, Jan 15, 2010 at 11:56 PM, David Cournapeau courn...@gmail.com
wrote:
How many combinations do you test manually? All supported Python
versions on
all platforms? Several Linux flavors?
I basically
On Sat, Jan 16, 2010 at 9:59 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Sat, Jan 16, 2010 at 5:19 PM, David Cournapeau courn...@gmail.com
wrote:
On Sat, Jan 16, 2010 at 4:57 PM, Ralf Gommers
From working on
the docs and scikits.image I am familiar with most of NumPy/SciPy
On Sun, Jan 17, 2010 at 4:12 AM, Kurt Smith kwmsm...@gmail.com wrote:
My questions here concern those familiar with configure/build/install
systems such as distutils, setuptools, scons/numscons or waf
(particularly David Cournapeau).
I'm creating a tool known as 'fwrap' that has a component
different.
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
.
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Fri, Jan 15, 2010 at 11:46 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
Hi David,
Here are some questions to get a clearer idea of exactly what's involved in
/ required for making a release.
On Thu, Jan 14, 2010 at 2:34 PM, David Cournapeau da...@silveregg.co.jp
wrote:
Charles R
Hi,
I encountered a problem in matlab which boils down to a surprising
behavior of np.ma.minimum:
x = np.random.randn(2, 3)
mx = np.matrix(x)
np.ma.minimum(x) # smallest item of x
ret = np.ma.minimum(mx) # flattened version of mx, i.e. ret == mx.flatten()
Is this expected ?
cheers,
David
desirable behavior. The problem appears when using pylab.imshow on
matrices, because matplotlib (and not matlab :) ) uses masked arrays
when normalizing the values.
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http
On Fri, Jan 15, 2010 at 11:59 AM, Pierre GM pgmdevl...@gmail.com wrote:
On Jan 14, 2010, at 8:52 PM, David Cournapeau wrote:
Pierre GM wrote:
Er, no.
np.ma.minimum(a, b) returns the lowest value of a and b element-wsie, or
the the lowest element of a is b is None. The behavior is inherited
Charles R Harris wrote:
On Wed, Jan 13, 2010 at 11:34 PM, David Cournapeau
da...@silveregg.co.jp mailto:da...@silveregg.co.jp wrote:
Charles R Harris wrote:
What is the setup one needs to build the installers? It might be
well to
document
together, that's imho a problem in the process;
I realize that testing is hard work, no glory.)
It is not so much hard-work than time consuming, at least as long as we
don't have automated testing of binaries.
Unfortunately, the problem was not caught properly during the beta phase,
David
almost 100 % automatically - the
testing is still manual.
I still think it would be a good idea to have a different release
manager for each release - it may be easier to find someone to do it
if it is only for one release cycle.
cheers,
David
/numpy/browser/trunk/pavement.py
which describes what is needed to build installers. On mac os x, the
release script may be used as is to build every installer + the release
notes.
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http
).
You should then be able to test your installations doing something like:
python -c import numpy; numpy.test(); import scipy; scipy.test()
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman
of magnitude
smaller than that (~ 5e4 x 5e4)
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
So, to get the new numpy.polynomial sub-package, one has to update to 1.4
(or is there a 1.3.x that has it)? Thanks!
DG
PS: my pressing need (another stupid question, at least coming from me):
chebyshev.chebdomain = [0,1] or [-1,1]? Thanks again!
___
On Fri, Jan 8, 2010 at 1:40 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
chebyshev.chebdomain is the default chebyshev domain and is [-1,1]. Maybe it
needs a bettter name? Note that it is integer; that isn't required, but it
makes it compatible with other types like Decimal that don't
On Fri, Jan 8, 2010 at 5:29 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
On Fri, Jan 8, 2010 at 5:19 PM, David Goldsmith d.l.goldsm...@gmail.com
wrote:
On Fri, Jan 8, 2010 at 1:40 PM, Charles R Harris
charlesr.har...@gmail.com wrote:
chebyshev.chebdomain is the default chebyshev
On 7-Jan-10, at 6:58 PM, Xue (Sue) Yang wrote:
Do I need any specifications when I run numpy with intel MKL (MKL9.1)?
numpy developers would be able to answer this question?
Are you sure you've compiled against MKL properly? What is printed by
numpy.show_config()?
David
Christopher Barker wrote:
David Cournapeau wrote:
On Thu, Jan 7, 2010 at 1:35 AM, Christopher Barker
In the past, I think folks' have used the default
name provided by bdist_mpkg, and those are not always clear. Something like:
numpy1.4-osx10.4-python.org2.6-32bit.dmg
The 32 bits
the right number.
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On 5-Jan-10, at 7:18 PM, Christopher Barker wrote:
If distutils/setuptools could identify the python version properly,
then
binary eggs and easy-install could be a solution -- but that's a
mess,
too.
Long live toydist! :)
David
___
NumPy
bug in the way ppc64 was detected. The fact that nobody found it
before me is probably evidence that it is nearly never used. It could
be useful in a minority of situations but I don't think it's going to
be worth it for most people.
David
On Fri, Jan 8, 2010 at 11:24 AM, David Warde-Farley d...@cs.toronto.edu wrote:
On 5-Jan-10, at 7:18 PM, Christopher Barker wrote:
If distutils/setuptools could identify the python version properly,
then
binary eggs and easy-install could be a solution -- but that's a
mess,
too.
Long
at the numpy neighborhood iterator performance in
one simple command, without special compilation flags:
44.69% python
/home/david/local/stow/scipy.git/lib/python2.6/site-packages/scipy/signal/sigtools.so
[.] _imp_correlate_nd_double
39.47% python
/home/david/local/stow/numpy-1.4.0
On Thu, Jan 7, 2010 at 1:22 AM, Christopher Barker
chris.bar...@noaa.gov wrote:
NOTE: cc-d to the pythonmac list from the numpy list -- this is really a
Mac issue. It's a discussion of what/how to produce binaries of numpy
for OS-X
David Cournapeau wrote:
On Wed, Jan 6, 2010 at 9:18 AM
how to make sure we do work there with distutils. The
whole MACOSX_DEPLOYMENT_TARGET confuses me quite a lot. Other than
that, the numpy 1.4.0 follows your advice, and contains the python.org
part.
David
___
NumPy-Discussion mailing list
NumPy-Discussion
an environment variable. Also,
the exact build commands depend on the version of the MKL, as its
libraries often change between versions.
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
are using.
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
not really a fan of packages polluting /usr/local, I'd rather the
tree appear /opt/packagename or /usr/local/packagename instead, for
ease of removal, but the general approach of stash somewhere and put
a .pth in both site-packages seems fine to me.
David
they could do is
removing the package so that people has slower, but accurate version.
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Wed, Jan 6, 2010 at 8:22 AM, David Warde-Farley d...@cs.toronto.edu wrote:
On 5-Jan-10, at 6:01 PM, Christopher Barker wrote:
As the 2.6 series is binary compatible, you can build a single
installer
that will work with both
I don't think that's true. 2.6.x are compatible with each other
of python
does not imply compatible python when C extensions are involved. In
current state of affairs, where python does not have a stable ABI, the
only workable solution is to target one specific python (or to build
your own as in EPD).
cheers,
David
threads instead of 4 was more efficient.
You can find this info in atlas_buildinfo.h file (the ATL_NCPU CPP
define). Note that you should not use atlas 3.8.0, as it has a number of
serious bugs - you should use 3.8.3.
David
___
NumPy-Discussion mailing
problem you (and me) have I think the best solution is
to integrate the tools mentioned above with what David is planning (SciPI
etc.). Or if that isn't good enough, find generic userland package
manager that has nothing to do with Python (I'm sure a dozen
half-finished ones must have been written
This is not the part I am afraid of. This is:
http://people.debian.org/~dburrows/model.pdf
cheers,
David
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Sun, Jan 3, 2010 at 8:05 PM, Nathaniel Smith n...@pobox.com wrote:
On Tue, Dec 29, 2009 at 6:34 AM, David Cournapeau courn...@gmail.com wrote:
Buildout, virtualenv all work by sandboxing from the system python:
each of them do not see each other, which may be useful for
development
On Mon, Jan 4, 2010 at 8:42 AM, Nathaniel Smith n...@pobox.com wrote:
On Sun, Jan 3, 2010 at 4:23 AM, David Cournapeau courn...@gmail.com wrote:
On Sun, Jan 3, 2010 at 8:05 PM, Nathaniel Smith n...@pobox.com wrote:
What I do -- and documented for people in my lab to do -- is set up
one
1001 - 1100 of 3108 matches
Mail list logo
