[MERGE] Better warnings when pyrex is not available

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vincent Ladeuil wrote:
>>>>>> "john" == John Arbash Meinel <john at arbash-meinel.com> writes:
> 
>     john> Since have finally merged our first Pyrex extension into bzr, we have now
>     john> started running into the user difficulties.
> 
> Don't forget dev difficulties ;-)
> 
> I ran into it yesterday, pyrex should be installed, but python-dev
> should be installed too or the compilation failed.
> 
>        Vincent
> 

That sounds like a packaging issue. Pyrex should depend on python-dev if it is
required to work.

Alternatively, we can check for whatever python-dev provides that we think we
need. But I think python from www.python.org doesn't split out a -dev package.
So it is really the distributers (debian/ubuntu/etc) that are breaking up the
package, and thus need to make sure it is available when needed.

Do you know a way to detect if python-dev is installed for your machine?

Preferably something along the lines of 'import foo', rather than
'os.subsystem("apt-cache search python-dev")'

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGm7ShJdeBCYSNAAMRAte3AJwJ+BwkhA6il2zsxdUbW1CyW0TTYgCfVMeX
6m0yaQ/7lER0+5/3/QnG2r8=
=EXzp
-----END PGP SIGNATURE-----