[pylucene-dev] Re: building JCC on Windows with MinGW

[Bill Janssen]

> For simplicity's sake, until modern setuptools is widespread

Good luck with that...  Wake me in 2015.

> I'd like to keep the static case simplest and the default.

I don't like that approach, because it means that two JCC-generated
modules won't live together in the same Python.

If I understand this right, this is only about the build.  A
distribution of a JCC-wrapped module can be built "shared", and
distributed, and the target machine need not have setuptools installed
to have everything work properly.  Given this, I'd still think that
doing things "shared" by default is a good thing; it requires the
builder to have a modern setuptools (and can complain if they don't),
which is not a difficult thing to achieve, but avoids the problems of
non-shared module distributions "poisoning" the Python for other
modules.

If it meant that the target Python had to have a modern setuptools,
then perhaps I'd agree with you.

Bill