Re: [Pytables-users] Why setup.py build_ext --inplace?

2007-07-02 Thread Andrew Straw
Francesc Altet wrote: > Perhaps somebody in the list knows a clean way of deleting the > extensions created with the 'build_ext --inplace' flags? Not exactly what you ask, but close enough for my purposes: (with a setuptools enabled setup.py:) python setup.py develop (and then:) python setup.py

Re: [Pytables-users] Why setup.py build_ext --inplace?

2007-07-02 Thread Francesc Altet
El dl 02 de 07 del 2007 a les 13:50 +0100, en/na Michael Hoffman va escriure: > Francesc Altet wrote: > > El dl 02 de 07 del 2007 a les 12:41 +0100, en/na Michael Hoffman va > > escriure: > >> The instructions indicate that one should use python setup.py build_ext > >> --inplace. Contrary to my in

Re: [Pytables-users] Why setup.py build_ext --inplace?

2007-07-02 Thread Michael Hoffman
Francesc Altet wrote: > El dl 02 de 07 del 2007 a les 12:41 +0100, en/na Michael Hoffman va > escriure: >> The instructions indicate that one should use python setup.py build_ext >> --inplace. Contrary to my initial belief, using python setup.py build >> seems to work. > > Well, it works, but yo

Re: [Pytables-users] Why setup.py build_ext --inplace?

2007-07-02 Thread Francesc Altet
El dl 02 de 07 del 2007 a les 12:41 +0100, en/na Michael Hoffman va escriure: > The instructions indicate that one should use python setup.py build_ext > --inplace. Contrary to my initial belief, using python setup.py build > seems to work. Well, it works, but you cannot use the build directory

[Pytables-users] Why setup.py build_ext --inplace?

2007-07-02 Thread Michael Hoffman
The instructions indicate that one should use python setup.py build_ext --inplace. Contrary to my initial belief, using python setup.py build seems to work. Using python setup.py build is the usual idiom, and allows things like python setup.py clean to work. -- Michael --