On Mon, Jul 19, 2010 at 8:31 PM, Robert Kern wrote:
> On Mon, Jul 19, 2010 at 14:17, Richard D. Moores wrote:
>> On Mon, Jul 19, 2010 at 09:00, Robert Kern wrote:
>>> On Mon, Jul 19, 2010 at 11:53, Richard D. Moores wrote:
On Mon, Jul 19, 2010 at 07:48, Robin wrote:
> On Mon, Jul 19,
On Mon, Jul 19, 2010 at 14:17, Richard D. Moores wrote:
> On Mon, Jul 19, 2010 at 09:00, Robert Kern wrote:
>> On Mon, Jul 19, 2010 at 11:53, Richard D. Moores wrote:
>>> On Mon, Jul 19, 2010 at 07:48, Robin wrote:
On Mon, Jul 19, 2010 at 1:53 PM, Matthieu Brucher
wrote:
> I'm af
On Mon, Jul 19, 2010 at 09:00, Robert Kern wrote:
> On Mon, Jul 19, 2010 at 11:53, Richard D. Moores wrote:
>> On Mon, Jul 19, 2010 at 07:48, Robin wrote:
>>> On Mon, Jul 19, 2010 at 1:53 PM, Matthieu Brucher
>>> wrote:
I'm afraid that if you don't know if you have a compiler, you don't
>>
On Mon, Jul 19, 2010 at 11:53, Richard D. Moores wrote:
> On Mon, Jul 19, 2010 at 07:48, Robin wrote:
>> On Mon, Jul 19, 2010 at 1:53 PM, Matthieu Brucher
>> wrote:
>>> I'm afraid that if you don't know if you have a compiler, you don't
>>> have one. This also means you will not be able to compi
On Mon, Jul 19, 2010 at 07:48, Robin wrote:
> On Mon, Jul 19, 2010 at 1:53 PM, Matthieu Brucher
> wrote:
>> I'm afraid that if you don't know if you have a compiler, you don't
>> have one. This also means you will not be able to compile Numpy, as
>> the official compiler is no longer available.
>
>On 19 July 2010 16:53, Richard D. Moores wrote:
> On Mon, Jul 19, 2010 at 07:38, Dave wrote:
>> When you say you "do have one" I'm assuming that when you entered gcc at the
>> command line you got the "gcc: no input files" error message back. In this
>> case
>> we need to tell python to use the
On Mon, Jul 19, 2010 at 07:38, Dave wrote:
> When you say you "do have one" I'm assuming that when you entered gcc at the
> command line you got the "gcc: no input files" error message back. In this
> case
> we need to tell python to use the gcc compilers.
No, I don't have gcc. I had access to g
On Mon, Jul 19, 2010 at 1:53 PM, Matthieu Brucher
wrote:
> I'm afraid that if you don't know if you have a compiler, you don't
> have one. This also means you will not be able to compile Numpy, as
> the official compiler is no longer available.
Is this the VS 2008 Express Edition? I saw something
Richard D. Moores gmail.com> writes:
>
> On Mon, Jul 19, 2010 at 06:03, Dave gmail.com> wrote:
> > My bad - typo. The command to build numpy should have been:
> >
> > C:\Python31\python setup.py bdist_wininst
>
> I tried that. See the attached.
>
> > i.e. the full path and filename of the pro
On Mon, Jul 19, 2010 at 06:56, Vincent Schut wrote:
>
>
> On 07/19/2010 03:34 PM, Richard D. Moores wrote:
>> On Mon, Jul 19, 2010 at 06:15, Vincent Schut wrote:
>> several years ago I was using Ulipad, an IDE for Python. It was under
>> active development and frequently updated via svn. So I h
On 07/19/2010 03:34 PM, Richard D. Moores wrote:
> On Mon, Jul 19, 2010 at 06:15, Vincent Schut wrote:
>>
>>
>> On 07/19/2010 02:56 PM, Richard D. Moores wrote:
>>> On Mon, Jul 19, 2010 at 05:28, Vincent Schutwrote:
Well, you might want to read up on some beginners guide for python
On Mon, Jul 19, 2010 at 06:15, Vincent Schut wrote:
>
>
> On 07/19/2010 02:56 PM, Richard D. Moores wrote:
>> On Mon, Jul 19, 2010 at 05:28, Vincent Schut wrote:
>>>
>>> Well, you might want to read up on some beginners guide for python? It's
>>> up to you, of course, but usually before starting
On Mon, Jul 19, 2010 at 06:03, Dave wrote:
> My bad - typo. The command to build numpy should have been:
>
> C:\Python31\python setup.py bdist_wininst
I tried that. See the attached.
> i.e. the full path and filename of the program you want to run (Python3).
> Paths
> are seperated by backslash
On 07/19/2010 02:56 PM, Richard D. Moores wrote:
> On Mon, Jul 19, 2010 at 05:28, Vincent Schut wrote:
>>
>> Well, you might want to read up on some beginners guide for python? It's
>> up to you, of course, but usually before starting with numpy (which
>> extends python), it is advised to have a
Richard D. Moores gmail.com> writes:
>
> >
> > The commands should therefore be:
> > cd c:\SVNRepository\numpy
> > C:\Python31>python setup.py bdist_wininst
>
> Dave, I got:
> c:\SVNRepository\numpy>C:\Python31>python setup.py bdist_wininst
> 'C:\Python31' is not recognized as an internal or ex
> Dave, I got:
> c:\SVNRepository\numpy>C:\Python31>python setup.py bdist_wininst
> 'C:\Python31' is not recognized as an internal or external command,
> operable program or batch file.
I shouldn't type "C:\Python31>python setup.py bdist_wininst". but python
setup.py bdist_wininst
You might have
On Mon, Jul 19, 2010 at 05:53, Matthieu Brucher
wrote:
>> Dave, I got:
>> c:\SVNRepository\numpy>C:\Python31>python setup.py bdist_wininst
>> 'C:\Python31' is not recognized as an internal or external command,
>> operable program or batch file.
>>
>> Or didn't I do exactly what you suggested?
>
>
On Mon, Jul 19, 2010 at 05:28, Vincent Schut wrote:
>
> Well, you might want to read up on some beginners guide for python? It's
> up to you, of course, but usually before starting with numpy (which
> extends python), it is advised to have at least some basic python
> understanding... Googling wil
> Dave, I got:
> c:\SVNRepository\numpy>C:\Python31>python setup.py bdist_wininst
> 'C:\Python31' is not recognized as an internal or external command,
> operable program or batch file.
>
> Or didn't I do exactly what you suggested?
python setup.py bdist_wininst
>> Assuming you have a C compiler
On Mon, Jul 19, 2010 at 05:37, Dave wrote:
> Richard D. Moores gmail.com> writes:
>> Dick
>
> You're 90% of the way there. Now you know that the Python3 "program" is called
> python.exe and is in the C:\Python31 directory.
>
> All you need to do now is compile numpy with the Python3 program. You
Richard D. Moores gmail.com> writes:
>
> On Mon, Jul 19, 2010 at 04:49, Alan G Isaac american.edu> wrote:
> > On 7/19/2010 7:33 AM, Richard D. Moores wrote:
> >> 'python3' is not recognized as an internal or external command,
> >> operable program or batch file.
> >
> > C:\Python31>dir *.exe
>
On 07/19/2010 02:08 PM, Richard D. Moores wrote:
> On Mon, Jul 19, 2010 at 04:49, Alan G Isaac wrote:
>> On 7/19/2010 7:33 AM, Richard D. Moores wrote:
>>> 'python3' is not recognized as an internal or external command,
>>> operable program or batch file.
>>
>> It's just ``python``.
>> hth,
>> A
> Now what? "Try simple commands"? Like "Lemme outta here!"?
I don't want to afraid you, but if you're not comfortable with command
line and numpy installation you should better wait for a binary release
and stick to the 2.X version until.
J.L.
___
N
On Mon, Jul 19, 2010 at 04:49, Alan G Isaac wrote:
> On 7/19/2010 7:33 AM, Richard D. Moores wrote:
>> 'python3' is not recognized as an internal or external command,
>> operable program or batch file.
>
> It's just ``python``.
> hth,
> Alan Isaac
>
> C:\Python31>dir *.exe
> Volume in drive C has
On 7/19/2010 7:33 AM, Richard D. Moores wrote:
> 'python3' is not recognized as an internal or external command,
> operable program or batch file.
It's just ``python``.
hth,
Alan Isaac
C:\Python31>dir *.exe
Volume in drive C has no label.
Volume Serial Number is 1464-2B08
Directory of C:\P
> Get:
> c:\Python31>python3 setup.py build
> 'python3' is not recognized as an internal or external command,
> operable program or batch file.
dude, look carefully to your commands, try to start python3 as a
interpreter. do simple tests, forward to lists the correct commands.
do NOT sniff glue,
On Mon, Jul 19, 2010 at 04:27, Renato Fabbri wrote:
> dick,
>
> The thing is:
>
> 1) get the path to where your python3 is installed (something like
> c:\Python3) i don't remember that anymore.
>
> 2) run that setup with it, like c:\python3\python3 setup.py build
Get:
c:\Python31>python3 setup.py
dick,
The thing is:
1) get the path to where your python3 is installed (something like
c:\Python3) i don't remember that anymore.
2) run that setup with it, like c:\python3\python3 setup.py build
3) read CAREFULLY the output at your console. Specially the last
lines. Start looking for an error,
On Mon, Jul 19, 2010 at 03:47, Renato Fabbri wrote:
> anyway, svn and tortoise are very useful.
>
> do some trial an error. try stuff, its easier than one usually imagine.
>
> (tip: checkout the svn address, whatever that should mean to you at the
> moment)
OK, I checked out, cd-ed to numpy, but
anyway, svn and tortoise are very useful.
do some trial an error. try stuff, its easier than one usually imagine.
(tip: checkout the svn address, whatever that should mean to you at the moment)
cheers,
rf
2010/7/19 David Cournapeau :
> On Mon, Jul 19, 2010 at 12:35 PM, Richard D. Moores
> wro
On Mon, Jul 19, 2010 at 12:35 PM, Richard D. Moores wrote:
> On Mon, Jul 19, 2010 at 00:38, Scott Sinclair
> wrote:
>>>On 19 July 2010 08:21, Richard D. Moores wrote:
>>> If not now, when?
>>
>> http://mail.scipy.org/pipermail/numpy-discussion/2010-July/051436.html
>
> I'm afraid I need some hel
On Mon, Jul 19, 2010 at 00:38, Scott Sinclair
wrote:
>>On 19 July 2010 08:21, Richard D. Moores wrote:
>> If not now, when?
>
> http://mail.scipy.org/pipermail/numpy-discussion/2010-July/051436.html
I'm afraid I need some help with that page. I'm interested in
--
>On 19 July 2010 08:21, Richard D. Moores wrote:
> If not now, when?
http://mail.scipy.org/pipermail/numpy-discussion/2010-July/051436.html
Cheers,
Scott
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinf
If not now, when?
Thanks,
Dick Moores
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
34 matches
Mail list logo
