On Tue, Mar 5, 2013 at 6:34 AM, Charles R Harris
wrote:
> I note that the way to access it is to run python setup.py with no
> arguments. I wonder what the proper message should be in that case?
Just let distutils handle it.
$ python setup.py
usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2
On Mon, Mar 4, 2013 at 10:34 PM, Charles R Harris wrote:
> I note that the way to access it is to run python setup.py with no
> arguments. I wonder what the proper message should be in that case?
>
How about usage instructions and an error message, similar to what a basic
distutils setup script
On Mon, Mar 4, 2013 at 10:37 PM, Ralf Gommers wrote:
>
>
>
> On Tue, Mar 5, 2013 at 5:12 AM, Aron Ahmadia wrote:
>
>> I've built numpy on many different machines, including supercomputers,
>> and I have never used interactive setup. I agree with the proposal to
>> remove it.
>>
>> A
>>
>>
>> On
On Tue, Mar 5, 2013 at 5:12 AM, Aron Ahmadia wrote:
> I've built numpy on many different machines, including supercomputers, and
> I have never used interactive setup. I agree with the proposal to remove
> it.
>
> A
>
>
> On Mon, Mar 4, 2013 at 11:10 PM, Charles R Harris <
> charlesr.har...@gmai
I've built numpy on many different machines, including supercomputers, and
I have never used interactive setup. I agree with the proposal to remove
it.
A
On Mon, Mar 4, 2013 at 11:10 PM, Charles R Harris wrote:
> In distutils there are three files that provide some interactive setup:
>
>
>
In distutils there are three files that provide some interactive setup:
1. numpy/distutils/core.py
2. numpy/distutils/fcompiler/gnu.py
3. numpy/distutils/interactive.py
In Python3 `raw_input` has been renamed 'input' and python2 'input' is
gone. I propose that the easiest solution to th
