Automatic specific compiler (mingw32) for win32 platform

[simon thepot]

Hi all,
as I tried to contribute to coverage.py, I wonder is there was a way to make thing simpler (ie: to remove some step in the howto.txt) for contributing to this module.

This improvment tries to get rid of the "building" step that need to go patching in your directories for specyfing the compiler to use.

(sample of howto.txt:
- Create PythonXX\Lib\distutils\distutils.cfg::
    [build]
    compiler = mingw32
)

Need to be test on a windows platform, but I think it works and would be a good move to make thing simpler and maybe bring more contributor for coverage.py (by making thiungs simpler and simpler.. I know this only step does not bring much.)

Regards,

Simon Thépot aka djcoin

[simon thepot]

You may find my patch on :
http://bitbucket.org/djcoin/coverage.py-patch-queue

Check for " Automatic specific compiler (mingw32) for win32 platform ".

Cheers

2010/5/10 simon thepot <simon....@gmail.com>

[Zooko Wilcox-O'Hearn]

I think this is a setting that should be in the system where
coverage.py is getting built, not in the coverage.py source. Some
people (unfortunately) have a Microsoft compiler instead of mingw32.

You can set this for all Python packages that you build on your system
by modifying your distutils configuration file:

http://docs.python.org/install/#inst-config-files

Regards,

Zooko

[Ned Batchelder]

That was my feeling as well. I have a line in my howto.txt that
explains how to do this to ensure mingw32 is used. I think Simon is
trying to reduce the amount of per-system setup that needs to be done
before the coverage.py tree can be used for development, which is a
great goal, but this does feel to me like something that shouldn't be
hard-coded into the coverage.py source.

--Ned.

[simon thepot]

All right :)

2010/5/11 Ned Batchelder <n...@nedbatchelder.com>