Configuring extension modules with distutils/setuptools?

From my experience working with other people's modules, I can say there is certainly not consensus on the right way to do this.

From my experience working with other people's modules, I can say there is certainly not consensus on the right way to do this. I have tried and rejected subclassing bits of distutils -- I found it fragile and difficult to get working across different Python versions and different systems. For our code, after trying the types of things you are considering, I have settled on doing detection and configuration right in setup.

Py before the main call to setup(). This is admittedly a bit ugly, but it means that someone trying compile your stuff has one place to figure out e.g. Why the include path is wrong. (And they certainly don't need to be experts on distutils internals).

My own experience with changing distutils has been weak and shaky, so all I can offer are pointers. Take a look at numpy. That has an entire submodule (numpy.

Distutils) with ways to work with (or work around) distutils. Otherwise, ask the distutils mailing list.

I would subclass distutils.core. Distribution and pass it with distutils.core. Setup(distclass=CustomDistribution) - this gives you access to the command-line parameters in the same way that the normal setup has them, and you can do things like adjusting the extensions list in the CustomDistribution.

__init__ method. But I agree with dalke, the way of distutils is full of pain...

The config command is designed to be subclassed and used by projects with requirements like yours.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.