svn commit: r310199 - in head/math/py-matplotlib: . files

[Dmitry Sivachenko]

On 11.01.2013, at 14:44, Ruslan Makhmatkhanov <cvs-src at yandex.ru> wrote:

> Dmitry Sivachenko wrote on 11.01.2013 11:43:
>> 
>> On 11.01.2013, at 11:20, Ruslan Makhmatkhanov <cvs-src at yandex.ru> wrote:
>> 
>>> Dmitry Sivachenko wrote on 11.01.2013 00:53:
>>>> 
>>>> 
>>>> 
>>>> Hello,
>>>> 
>>>> According to changelog, version 1.2.0 of matplotlib supports python-3.X.
>>>> 
>>>> So why USE_PYTHON=-2.7?
>>> 
>>> Hi, I wasn't aware about this. Will check soon. But I believe it will fail at dependencies that not 3.x-aware.
>>> 
>> 
>> 
>> How could developers support python3 in matplotlib if it's dependencies are not python3-aware? :)
>> The only significant dependency is py-numpy which does work with python3.
> 
> I consider this from ports tree point of view. If any of the deps need python2.7, this breaks the python3 build. As bare minimum, I see two problems with dependencies:
> - current devel/py-dateutils doesn't supports python3


dateutils version 2.0 with python3 support is out for almost 2 years now.


> - matplotlib depends on pygtk2 (read: python2 only) by default
> 


I would rather insist for python-2.X only if pygtk2 is selected.
I think it is rather common usage for matplotlib without GUI at all or at least without pygtk2.

So no need to prevent all others to build it with python3.