Python 3.4 support for ports

[Rainer Müller]

Hi,

On 2014-02-11 18:44, Peter Danecek wrote:
> I realise that only very little python packages currently enable 3.4
> support (only 31 py34 subports compared to 260 py32 subports and 243
> py33 subports), probably because Python 3.4 was development so far
> and maintainers did not want to support it.

I tried to support +python34 for the vim ports, but trying the same 
method as for +python33 failed as it does not find Python.h anymore:

--------
/usr/bin/clang -c -I. -Iproto -DHAVE_CONFIG_H   -isystem/opt/local/include -DMACOS_X_UNIX -no-cpp-precomp  -pipe -Os -arch x86_64       -DPYTHON3_HOME='L"/opt/local/Library/Frameworks/Python.framework/Versions/3.4"' -fPIE  -o objects/if_python3.o if_python3.c
if_python3.c:66:10: fatal error: 'Python.h' file not found
#include <Python.h>
         ^
1 error generated.
make[1]: *** [objects/if_python3.o] Error 1
--------

It's obviously missing some -I option pointing to the Python.framework 
include directory, which I confirmed is used on the +python33 build.

Before looking further for patching this, I noticed that the python33 
port uses the destroot targets 'frameworkinstall maninstall', but 
python34 uses 'altinstall'. Is there a reason for this change?
I suspect this to be the reason for the problem I am seeing.

Rainer