1. configure and build python using the --includedir
option.  For example:

$ configure --prefix=/TANGO/3/rel
--includedir=/TANGO/3/rel/inc

2. Run

$ make install

3. Notice that the include files are placed in
/TANGO/3/rel/include not /TANGO/3/rel/inc.

4. Verify with

$ python -c 'from distutils.sysconfig import *;print
get_python_inc()

5. The problem is that get_python_inc() hard codes the
include file path to use the name "include"

6. Other programs using distutils will fail since the
INSTALL_SCHEMES found in install.py also have the name
"include" hard coded.

7.  Suggested fix would be to use --includedir to
calculate the include path used by distutils.

I'm having the same problem.
This is a real headache, especially on systems that
run both 32-bit and 64-bit apps, where I often see 
"lib64", "include64" and "bin64".

In my opinion, lib, include and bin shouldn't be hard-coded in anywhere.

Note that these hard-coded paths are found in other places, too.
See http://bugs.python.org/issue1294959 for further detials.

I think this is duplicate of issue858809.

Yes, this is a duplicate of issue858809 and tarek is assigned to that
one too.