Do you use python setup.py build_ext --inplace ?

Hello all,

When you are working on matplotlib, after a checkout from the SVN
repository, which method do you use to compile extensions without
re-building and re-installing everything each time?

For now, I use this method:
- I checkout matplotlib in directory c:\projects\matplotlib.
- I add c:\projects\matplotlib\lib to my PYTHONPATH.
- I use the command "python setup.py build_ext --inplace" each time I
modify a C/C++ file.
- Without anything else, I can use matplotlib in my scripts.

The problem:
This method builds smoothly my extensions (.pyd files) alongside my
Python files (.py files). But I have no directory
c:\projects\matplotlib\lib\matplotlib\mpl-data, like in a standard
installation. As a workaround, I've created it manually by copying
files from directory fonts and images.

My question:
Matplotlib's developers, how do you proceed on your own computer?

Thanks a lot for your answers,

Nicolas Grilly

I rebuild and reinstall each time. Since only the changed files are
built, this usually goes fairly quickly after a svn update. If you
ware working on extension code, it can get slow if you are building
the numpy, Numeric and numarray extensions each time. You can
manually override the NUMERIX list in setup.py to just build one of
the array extensions while developing, which should cut your compile
times.

JDH

ยทยทยท

On 2/11/07, Nicolas Grilly <nicolas.grilly@...475...> wrote:

When you are working on matplotlib, after a checkout from the SVN
repository, which method do you use to compile extensions without
re-building and re-installing everything each time?