On Apr 14, 2009, at 10:31 PM, chris.bar...@noaa.gov wrote:
David Cournapeau wrote:
Christopher, would you mind trying the following binary ?
http://www.ar.media.kyoto-u.ac.jp/members/david/archives/numpy/scipy-0.7.0-py2.5-macosx10.5.mpkg.tar
I'm out of town and away from my Mac the whole we
I've been asked to provide Numpy & Scipy as python egg files.
Unfortunately Numpy and Scipy do not make official releases of their
product in .egg form for a Win32 platform - that means if I want eggs
then I have to compile them myself.
At the moment my employer provides Visual Studio.Net 2003, wh
Hi,
There is a Python limitation for the compiler. if you have 2.5 or
less, you're stuck with VS2003, if you have 2.6, you can use 2008 (or
2005, I don't remember). If you use numscons, you can go with any of
them (at your own risks).
You can also use mingw.
For scipy, you have to use mingw, beca
I'm compiling for Python 2.4, so I guess that means that I'm never going to be
able to use anything more than visual studio 2003?
What about compilors from other vendors, for example Intel or Borland?
Thanks
-Original Message-
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-di
Borland -> don't even try them, they are not worth it.
Intel -> you may try, but I don't know if numpy or scipy was compiled
with them. As there is a C compiler, as well as a C++ and a Fortran
one, you may try.
David compiles with mingw, you should give it a try (although
compiling them yourself w
So what is the official way to compile Numpy 1.3.0 for Python 2.4.x? If Visual
Studio 2003 will not compile it and nothing else is intended to work, then
surely nothing will work? That cannot be right.
PS. Perhaps there is another way to do it... compiling for me is just a means
to an end. We a
Fadhley Salim schrieb:
> So what is the official way to compile Numpy 1.3.0 for Python 2.4.x?
> If Visual Studio 2003 will not compile it and nothing else is
> intended to work, then surely nothing will work? That cannot be
> right.
>
> PS. Perhaps there is another way to do it... compiling for me
Thomasm,
What want is the current latest Numpy as a win32 .egg file for Python
2.4.4. I'm not bothered how I get there. We've been able to compile
numpy 1.1.1 on visual studio 2003 with no problems at all. I've not yet
been able to get anything newer to work.
At the moment I'm trying to build usi
2009/4/15 Fadhley Salim :
> So what is the official way to compile Numpy 1.3.0 for Python 2.4.x? If
> Visual Studio 2003 will not compile it and nothing else is intended to work,
> then surely nothing will work? That cannot be right.
Mingw is used to compile numpy and scipy AFAIK.
> PS. Perhaps
Fadhley Salim wrote:
> Thomasm,
>
> What want is the current latest Numpy as a win32 .egg file for Python
> 2.4.4. I'm not bothered how I get there. We've been able to compile
> * Dont care how I make it as long as it works!
Are you aware that the reason numpy is not distributed as an .egg is so
On Wed, Apr 15, 2009 at 11:58 AM, Fadhley Salim wrote:
> Thomasm,
>
> What want is the current latest Numpy as a win32 .egg file for Python
> 2.4.4. I'm not bothered how I get there. We've been able to compile
> numpy 1.1.1 on visual studio 2003 with no problems at all. I've not yet
> been able t
> Mingw is used to compile numpy and scipy AFAIK.
So if I just grab Mingw I should be able to compile the latest stuff
with no problems? Will that work perfectly with my standard Python.org
Cpython distribution?
> Why is exe files a problem ?
We deploy on a very large number of computers in 5 co
Good point - we do not require ultimate optimization. I'd be happy if I
could custom build an egg that is optimized for our PCs which are all
Xeons or Pentium 4's built in the last 2 years.
-Original Message-
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.
Chuck,
I'm not all that familiar with the bug reporting process but if you were
to point me to the relevant bug tracker I'd be delighted to file an
issue. If I could get somebody to fix this upstream I'd be so happy!
Thanks!
Sal
From: numpy-discussion-boun.
Hi Sal,
On Wed, Apr 15, 2009 at 12:37 PM, Fadhley Salim wrote:
> Chuck,
>
> I'm not all that familiar with the bug reporting process but if you were to
> point me to the relevant bug tracker I'd be delighted to file an issue. If I
> could get somebody to fix this upstream I'd be so happy!
>
> T
http://projects.scipy.org/numpy/ticket/1086
I filed this under numpy since that's what I am trying to compile.
Please feel free to correct if you think I've mis-described the fault.
I'm heading home now.
My sinceerest thanks to everybody in the group who's helped me with this
today.
Sal
The subject line says it all... Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Wed, Apr 15, 2009 at 1:15 PM, Charles R Harris wrote:
> The subject line says it all... Chuck
>
Seems to be fixed now.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Thu, Apr 16, 2009 at 1:17 AM, Fadhley Salim
wrote:
> I've been asked to provide Numpy & Scipy as python egg files.
> Unfortunately Numpy and Scipy do not make official releases of their
> product in .egg form for a Win32 platform - that means if I want eggs
> then I have to compile them myself.
On Wed, Apr 15, 2009 at 3:17 PM, David Cournapeau wrote:
> On Thu, Apr 16, 2009 at 1:17 AM, Fadhley Salim
> wrote:
>> I've been asked to provide Numpy & Scipy as python egg files.
>> Unfortunately Numpy and Scipy do not make official releases of their
>> product in .egg form for a Win32 platform
On Wed, Apr 15, 2009 at 1:17 PM, David Cournapeau wrote:
> On Thu, Apr 16, 2009 at 1:17 AM, Fadhley Salim
> wrote:
> > I've been asked to provide Numpy & Scipy as python egg files.
> > Unfortunately Numpy and Scipy do not make official releases of their
> > product in .egg form for a Win32 platfo
Mixing views and mutating (eg. in-place) operations can cause surprising
and ill-defined results. Consider
http://projects.scipy.org/numpy/ticket/1085:
>>> import numpy as np
>>> x = np.array([[1,2], [3,4]])
>>> x
array([[1, 2],
[3, 4]])
>>> x += x.T
>>> x
array([[2, 5],
[8, 8]])
Wed, 15 Apr 2009 15:42:05 -0400, josef.pktd wrote:
> On Wed, Apr 15, 2009 at 3:17 PM, David Cournapeau
> wrote:
>> On Thu, Apr 16, 2009 at 1:17 AM, Fadhley Salim
>> wrote:
>>> I've been asked to provide Numpy & Scipy as python egg files.
>>> Unfortunately Numpy and Scipy do not make official rel
On Wed, Apr 15, 2009 at 3:54 PM, Pauli Virtanen wrote:
> Wed, 15 Apr 2009 15:42:05 -0400, josef.pktd wrote:
>
>> On Wed, Apr 15, 2009 at 3:17 PM, David Cournapeau
>> wrote:
>>> On Thu, Apr 16, 2009 at 1:17 AM, Fadhley Salim
>>> wrote:
I've been asked to provide Numpy & Scipy as python egg f
On Wed, Apr 15, 2009 at 1:52 PM, Pauli Virtanen wrote:
>
> Mixing views and mutating (eg. in-place) operations can cause surprising
> and ill-defined results. Consider
> http://projects.scipy.org/numpy/ticket/1085:
>
> >>> import numpy as np
> >>> x = np.array([[1,2], [3,4]])
> >>> x
> array([[1,
I think this is unavoidable. If we state clearly that every numpy
function assums non-pointer aliasing, then people have to care about
this themselves (like they would in Fortran, or in C++ for object-like
arrays).
Matthieu
2009/4/15 Charles R Harris :
>
>
> On Wed, Apr 15, 2009 at 1:52 PM, Pauli
On Wed, Apr 15, 2009 at 4:10 PM, Charles R Harris
wrote:
>
>
> On Wed, Apr 15, 2009 at 1:52 PM, Pauli Virtanen wrote:
>>
>> Mixing views and mutating (eg. in-place) operations can cause surprising
>> and ill-defined results. Consider
>> http://projects.scipy.org/numpy/ticket/1085:
>>
>> >>> impor
On Wed, Apr 15, 2009 at 4:34 PM, Matthieu Brucher
wrote:
> I think this is unavoidable. If we state clearly that every numpy
> function assums non-pointer aliasing, then people have to care about
> this themselves (like they would in Fortran, or in C++ for object-like
> arrays).
"non-pointer ali
Wed, 15 Apr 2009 16:36:09 -0400, josef.pktd wrote:
[clip]
> Is there a list of gotchas for working with views that might produce
> unexpected results?
I don't think there is. Also, the reference manual would probably need a
separate section about views.
--
Pauli Virtanen
__
2009/4/15 :
> On Wed, Apr 15, 2009 at 4:34 PM, Matthieu Brucher
> wrote:
>> I think this is unavoidable. If we state clearly that every numpy
>> function assums non-pointer aliasing, then people have to care about
>> this themselves (like they would in Fortran, or in C++ for object-like
>> arrays
Hi! What I do is make a distutils.cfg file and put in the
$PYTHONHOME/Lib/distutils
directory (for me, c:\python25\lib\distutils)
and then it will use mingw32 for the compilation. I've attached the one I
use.
Cheers,
William
On Wed, Apr 15, 2009 at 4:06 PM, wrote:
> On Wed, Apr 15, 2009 at
Wed, 15 Apr 2009 22:34:49 +0200, Matthieu Brucher wrote:
> I think this is unavoidable. If we state clearly that every numpy
> function assums non-pointer aliasing, then people have to care about
> this themselves (like they would in Fortran, or in C++ for object-like
> arrays).
Nevertheless, thi
Hi all,
Just now when I tried to access http://projects.scipy.org/numpy,
Firefox complains (after a bit) that there's a redirect loop. Is anyone
else seeing this problem, and/or does anyone know how I can fix my side
of things to get me to the site?
Thanks,
Ken
Hi Pauli,
I'm going to move the docstrings from mtrand.pyx to add_newdocs.py. Will
this require any fixes to the doc editor so that the docs don't get readded
to mtrand?
Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scip
On Wed, Apr 15, 2009 at 2:51 PM, Pauli Virtanen wrote:
> Wed, 15 Apr 2009 22:34:49 +0200, Matthieu Brucher wrote:
>
> > I think this is unavoidable. If we state clearly that every numpy
> > function assums non-pointer aliasing, then people have to care about
> > this themselves (like they would i
On Wed, Apr 15, 2009 at 5:39 PM, Charles R Harris
wrote:
>
>
> On Wed, Apr 15, 2009 at 2:51 PM, Pauli Virtanen wrote:
>>
>> Wed, 15 Apr 2009 22:34:49 +0200, Matthieu Brucher wrote:
>>
>> > I think this is unavoidable. If we state clearly that every numpy
>> > function assums non-pointer aliasing,
Wed, 15 Apr 2009 15:27:21 -0600, Charles R Harris wrote:
> I'm going to move the docstrings from mtrand.pyx to add_newdocs.py. Will
> this require any fixes to the doc editor so that the docs don't get
> readded to mtrand?
Go ahead, nothing should break.
--
Pauli Virtanen
__
Wed, 15 Apr 2009 17:21:59 -0400, Ken Basye wrote:
> Just now when I tried to access http://projects.scipy.org/numpy,
> Firefox complains (after a bit) that there's a redirect loop. Is anyone
> else seeing this problem, and/or does anyone know how I can fix my side
> of things to get me to the site
On Wed, Apr 15, 2009 at 16:27, Charles R Harris
wrote:
> Hi Pauli,
>
> I'm going to move the docstrings from mtrand.pyx to add_newdocs.py. Will
> this require any fixes to the doc editor so that the docs don't get readded
> to mtrand?
IIRC, David has told me that recent Cythons will do the right
Hi Pauli, and thanks.
I tried clearing the cache (no luck), and then logging in from a completely different machine with a completely re-initialized browser. I can get to the site, but as soon as I try to log in, the same thing (redirect loop) happens. I should point out that just before this
On Wed, Apr 15, 2009 at 4:50 PM, Robert Kern wrote:
> On Wed, Apr 15, 2009 at 16:27, Charles R Harris
> wrote:
> > Hi Pauli,
> >
> > I'm going to move the docstrings from mtrand.pyx to add_newdocs.py. Will
> > this require any fixes to the doc editor so that the docs don't get
> readded
> > to m
On Wed, Apr 15, 2009 at 19:03, Charles R Harris
wrote:
>
> On Wed, Apr 15, 2009 at 4:50 PM, Robert Kern wrote:
>>
>> On Wed, Apr 15, 2009 at 16:27, Charles R Harris
>> wrote:
>> > Hi Pauli,
>> >
>> > I'm going to move the docstrings from mtrand.pyx to add_newdocs.py. Will
>> > this require any f
On Wed, Apr 15, 2009 at 6:05 PM, Robert Kern wrote:
> On Wed, Apr 15, 2009 at 19:03, Charles R Harris
> wrote:
> >
> > On Wed, Apr 15, 2009 at 4:50 PM, Robert Kern
> wrote:
> >>
> >> On Wed, Apr 15, 2009 at 16:27, Charles R Harris
> >> wrote:
> >> > Hi Pauli,
> >> >
> >> > I'm going to move th
David Cournapeau wrote:
> chris.bar...@noaa.gov wrote:
>> I think I'd prefer to patch bdist_mpkg, rather than re-writing or
>> forking.
> If you manage to do what you want as a command, then yes, forking does
> not make any sense. It is just that I am tired of wasting my time with
> distutils-r
Hi Sal,
On Wed, Apr 15, 2009 at 1:03 PM, Fadhley Salim
wrote:
> http://projects.scipy.org/numpy/ticket/1086
>
> I filed this under numpy since that's what I am trying to compile. Please
> feel free to correct if you think I've mis-described the fault. I'm heading
> home now.
>
> My sinceerest th
On Thu, Apr 16, 2009 at 9:13 AM, Charles R Harris
wrote:
>
> OK, I just ran mtrand through cython-0.9.8.1.1, which is probably horribly
> outdated, and it does break up the strings.
Please use cython 0.10.4 or above - below versions have a
bug/limitation which breaks 64 bits python 2.4. I don't
On Wed, Apr 15, 2009 at 8:19 PM, David Cournapeau wrote:
> On Thu, Apr 16, 2009 at 9:13 AM, Charles R Harris
> wrote:
>
> >
> > OK, I just ran mtrand through cython-0.9.8.1.1, which is probably
> horribly
> > outdated, and it does break up the strings.
>
> Please use cython 0.10.4 or above - bel
On Wed, Apr 15, 2009 at 07:33:48PM +0100, Fadhley Salim wrote:
> We deploy on a very large number of computers in 5 countries.
> PEAK's Setuptools gives us the ability to do all this deployment
> automatically. If we can package all of our dependancies as egg files
> then setuptools automatically
On Thu, Apr 16, 2009 at 00:45, Gael Varoquaux
wrote:
> On Wed, Apr 15, 2009 at 07:33:48PM +0100, Fadhley Salim wrote:
>> We deploy on a very large number of computers in 5 countries.
>
>> PEAK's Setuptools gives us the ability to do all this deployment
>> automatically. If we can package all of ou
Robert Kern wrote:
> It is David's desire to
> distribute numpy builds with optimized BLASes that does not fit into
> eggs, not numpy. Plain numpy eggs are really straightforward.
>
There may be a misunderstanding: I would not mind distributing something
without optimized BLAS. Not using atlas
On Thu, Apr 16, 2009 at 01:27, David Cournapeau
wrote:
> Robert Kern wrote:
>> It is David's desire to
>> distribute numpy builds with optimized BLASes that does not fit into
>> eggs, not numpy. Plain numpy eggs are really straightforward.
>
> There may be a misunderstanding: I would not mind dist
Fadhley Salim wrote:
> I've been asked to provide Numpy & Scipy as python egg files.
> Unfortunately Numpy and Scipy do not make official releases of their
> product in .egg form for a Win32 platform - that means if I want eggs
> then I have to compile them myself.
>
I think having a simple .ex
52 matches
Mail list logo
