Hi, A small batch of patches intended to improve & fix python_wrapper_setup(), pretty much thanks to perfinion.
Long story short, he noticed two issues: 1. we are missing pythonN-config, both in wrappers and in eselect-python (addressed by patch 2), 2. since python3.4, some symlink reading magic is applied that causes python to use wrong prefixes if python-config is symlinked somewhere (addressed by patch 1). While at it, I also added some 'unsupported' wrappers to ban trying to use pythonY (accidental fallback to system python) when pythonX is selected via wrapper, and changed the exit code for unsupp-scripts. Patches 1 & 4 should be harmless. Patch 2 should not cause issues either. Some scripts may start using pythonN-config when they used to fallback to python-config. However, fixing eselect-python side of this may actually cause issues if this causes configure scripts to prefer python3-config over wrapped python2-config. Patch 3 addresses this. Patch 3 is going to cause issues if configure scripts look for pythonN-config before python-config. For example, in python2.7 they are going to find python3-config and try (and fail) to use that, while right now they falled back to python-config. However, the worse would happen if we fixed eselect-python without committing this patch first.
