I know this is the wrong forum, but:
Yet another reason Python itself needs a standard, supported way to
handle package versioning.
*sigh*
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R(206) 526-6959 voice
7600 Sand Point Way NE (20
On 4/17/2009 11:50 AM, Gael Varoquaux wrote:
> Could you elaborate on your reason.
Probably silly reasons though...
I have a distutils.cfg file and a build system set up that works. I
don't want to bother setting up a different build system when I already
have one that works. I can use the Int
On Fri, Apr 17, 2009 at 11:48:57AM +0200, Sturla Molden wrote:
> I use this 32 bit mingw binary to build my Cython and f2py extensions. I
> works like a charm. I have licenses for Intel compilers at work, but I
> prefer gfortran 4.4.
Could you elaborate on your reason.
Gaël
On 4/17/2009 10:50 AM, David Cournapeau wrote:
> I think Matthieu meant you have to use VS2003 as a MS compiler. Mingw is
> obviously fine, since that's how numpy binaries are built for quite a
> long time
That is what I thought he meant as well, and it seems to be a widespread
belief. The fact
Sturla Molden wrote:
> On 4/15/2009 6:44 PM, Matthieu Brucher wrote:
>
>
>> There is a Python limitation for the compiler.
>>
>
> There is a common misunderstanding that only VS2003 can be used to
> compile extension objects for Python 2.5. Don't believe it. There is no
> Python limitati
On 4/15/2009 6:44 PM, Matthieu Brucher wrote:
> There is a Python limitation for the compiler.
There is a common misunderstanding that only VS2003 can be used to
compile extension objects for Python 2.5. Don't believe it. There is no
Python limitation for the compiler.
There is a Python limit
ssion-boun...@scipy.org] On Behalf Of David
Cournapeau
Sent: 17 April 2009 05:46
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
On Fri, Apr 17, 2009 at 1:38 PM, Robert Kern
wrote:
> On Thu, Apr 16, 2009 at 23:37, David Cournapeau
wrote:
>>
April 2009 05:08
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
On Thu, Apr 16, 2009 at 7:43 PM, David Cournapeau
wrote:
On Fri, Apr 17, 2009 at 12:25 AM, David Cournapeau
wrote:
>> We need to be able to run both pr
On Thu, Apr 16, 2009 at 23:45, David Cournapeau wrote:
> Since I am not an egg user myself, I wonder whether it would be useful
> to make numpy zip-safe ? Can it be done without numpy relying on
> setuptools, or do we have to use setuptools for pkg_resources (maybe
> pkg_resources can be used wit
On Fri, Apr 17, 2009 at 1:38 PM, Robert Kern wrote:
> On Thu, Apr 16, 2009 at 23:37, David Cournapeau wrote:
>> On Thu, Apr 16, 2009 at 4:23 PM, Robert Kern wrote:
>>
>>> I think it will try to collect all of the possibilities by looking at
>>> PyPI and the download link, then decide on the best
On Thu, Apr 16, 2009 at 23:37, David Cournapeau wrote:
> On Thu, Apr 16, 2009 at 4:23 PM, Robert Kern wrote:
>
>> I think it will try to collect all of the possibilities by looking at
>> PyPI and the download link, then decide on the best one. But it could
>> be that if there are files on PyPI, i
On Thu, Apr 16, 2009 at 4:23 PM, Robert Kern wrote:
>
> I think it will try to collect all of the possibilities by looking at
> PyPI and the download link, then decide on the best one. But it could
> be that if there are files on PyPI, it will only consider those. I
> don't know.
I ended up push
On Thu, Apr 16, 2009 at 7:43 PM, David Cournapeau wrote:
> On Fri, Apr 17, 2009 at 12:25 AM, David Cournapeau
> wrote:
> >> We need to be able to run both projects concurrently on the same grid.
> >> Setuptools + eggs allows this to happen. If we used .exe installers then
> >> we could only have
On Fri, Apr 17, 2009 at 12:25 AM, David Cournapeau wrote:
>> We need to be able to run both projects concurrently on the same grid.
>> Setuptools + eggs allows this to happen. If we used .exe installers then
>> we could only have one single version of any given dependancy at any
>> time and so we
On Thu, Apr 16, 2009 at 11:50 PM, Fadhley Salim
wrote:
> I just installed the latest stable mingw, and made sure that the mingw
> bin directory is in my PATH. I used the command you suggested and got
> the following output:
>
> http://pastebin.com/m4aea512c
Could you make sure to remove entirely
> We need to be able to run both projects concurrently on the same grid.
> Setuptools + eggs allows this to happen. If we used .exe installers then
> we could only have one single version of any given dependancy at any
> time and so we would not be able to run the two projects in paralell.
I think
@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of David
Cournapeau
Sent: 16 April 2009 07:50
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
Robert Kern wrote:
>
> I have found that people are more willing to accept that th
Message-
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of David
Cournapeau
Sent: 16 April 2009 07:42
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
I think having a simple .exe installer that
On Fri, Apr 17, 2009 at 12:12 AM, Fadhley Salim
wrote:
> I agree with Robert
>
> There should be no reason on earth why you cannot use an Egg to package
> Numpy.
Actually, there is, although it is not really an egg deficiency. We
use ATLAS as blas/lapack, and ATLAS binaries are tuned for one
arch
On Fri, Apr 17, 2009 at 12:10 AM, wrote:
> On Thu, Apr 16, 2009 at 11:03 AM, Fadhley Salim
> wrote:
>> No joy yet - this time a completely different error. I just tried r6871 and
>> r6872...
>>
>> http://pastebin.com/d4d240b36
>
> do you have g77 included in mingw and on your path?
g77 should n
l 2009 06:51
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
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
On Thu, Apr 16, 2009 at 11:03 AM, Fadhley Salim
wrote:
> No joy yet - this time a completely different error. I just tried r6871 and
> r6872...
>
> http://pastebin.com/d4d240b36
do you have g77 included in mingw and on your path?
Josef
___
Numpy-discus
: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
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
co
n.org
-Original Message-
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Pauli Virtanen
Sent: 15 April 2009 20:55
To: numpy-discussion@scipy.org
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
I think it might work if you sep
On Thu, Apr 16, 2009 at 02:02, David Cournapeau
wrote:
> Robert Kern wrote:
>>
>> easy_install is documented to be able to find and convert a
>> bdist_wininst .exe on the fly, so I believe that should be sufficient.
>
> Yes, I've tried locally on a bdist_wininst exe, and easy_install could
> insta
On Thu, Apr 16, 2009 at 04:02:01PM +0900, David Cournapeau wrote:
> What about just pushing the non optimized bdist_wininst installer on
> pypi ?
With a clear note saying that they are non optimised.
G.
___
Numpy-discussion mailing list
Numpy-discussion
Robert Kern wrote:
>
> easy_install is documented to be able to find and convert a
> bdist_wininst .exe on the fly, so I believe that should be sufficient.
>
Yes, I've tried locally on a bdist_wininst exe, and easy_install could
install it. I have not tested it from the network.
> It might be
On Thu, Apr 16, 2009 at 01:52, David Cournapeau
wrote:
> David Cournapeau wrote:
>> Robert Kern wrote:
>>
>>> I have found that people are more willing to accept that they have to
>>> do something different to get a technically chalenging feature (i.e.
>>> use a particular installer to get a safe,
David Cournapeau wrote:
> Robert Kern wrote:
>
>> I have found that people are more willing to accept that they have to
>> do something different to get a technically chalenging feature (i.e.
>> use a particular installer to get a safe, optimized BLAS) than to
>> accept that a relatively straigh
Robert Kern wrote:
>
> I have found that people are more willing to accept that they have to
> do something different to get a technically chalenging feature (i.e.
> use a particular installer to get a safe, optimized BLAS) than to
> accept that a relatively straightforward feature is not available
On Thu, Apr 16, 2009 at 12:50:59AM -0500, Robert Kern wrote:
> > PEAK's setuptools is fragile with complex packages. This is the core
> > reason numpy is not distributed as an egg, as the implications on what
> > numpy would have to do to 'fit' in an egg compromise numpy's instal
> > quality (read:
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
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
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 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
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
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
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
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
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 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
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 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.
th this
today.
Sal
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Charles R
Harris
Sent: 15 April 2009 20:01
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
Hi S
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
discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Charles R
Harris
Sent: 15 April 2009 19:32
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
On Wed, Apr 15, 2009 at 11:58 AM, Fadhley Salim
wrote:
ssion-boun...@scipy.org] On Behalf Of Andrew Straw
Sent: 15 April 2009 19:31
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
Fadhley Salim wrote:
> Thomasm,
>
> What want is the current latest Numpy as a win32 .egg file for Python
> 2.4.4.
> 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
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
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
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
e how I make it as long as it works!
:-)
-Original Message-
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Thomas Heller
Sent: 15 April 2009 18:48
To: numpy-discussion@scipy.org
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
Fadhley Salim
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
9 17:45
> To: Discussion of Numerical Python
> Subject: Re: [Numpy-discussion] Compiling for free on Windows32
>
> 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&#x
bout compilors from other vendors, for example Intel or Borland?
>
> Thanks
>
> -Original Message-
> From: numpy-discussion-boun...@scipy.org
> [mailto:numpy-discussion-boun...@scipy.org] On Behalf Of Matthieu Brucher
> Sent: 15 April 2009 17:45
> To: Discussion of Nu
ilto:numpy-discussion-boun...@scipy.org] On Behalf Of Matthieu Brucher
Sent: 15 April 2009 17:45
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] Compiling for free on Windows32
Hi,
There is a Python limitation for the compiler. if you have 2.5 or less, you're
stuck with VS20
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'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
58 matches
Mail list logo
