python.include setting?

[Jeremy Lavergne]

"m" means that they were built with pymalloc. 

On Apr 9, 2013, at 10:44 AM, Michael Dickens wrote:

> I'm working on fixing a ticket with regard to numpy, and came upon an
> odd issue with Python: the actual header directory name is different
> than that found in python.include for 3.2 and 3.3, but not for 2.7.
> 
> {{{
> % ls -AFd
> /opt/local/Library/Frameworks/Python.framework/Versions/*/include/python*
> /opt/local/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/
> /opt/local/Library/Frameworks/Python.framework/Versions/3.2/include/python3.2m/
> /opt/local/Library/Frameworks/Python.framework/Versions/3.3/include/python3.3m/
> }}}
> 
> The python-1.0 Portgroup python.include variable does not include the
> trailing "m" for any version of Python (nor is this present in any of
> the other Python PortGroups).  I see nothing from the Python 3.2 or 3.3
> Portfiles that indicate that the "m" should be there, nor anything from
> any of the python PortGroups in that regard either.
> 
> I'm wondering which is correct?  I'm guessing the non-"m" version is.
> Thoughts? - MLD