|
From: | Tamas Nepusz |
Subject: | Re: [igraph] igraph0.6 & python2.5 |
Date: | Wed, 15 Dec 2010 18:00:41 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 |
I will check the source of the Python interface tomorrow to see how difficult it would be to backport these changes to Python 2.5. @foo.setter is a nice touch that I really liked in Python 2.6; maybe there is an easy workaround to keep these changes while still supporting Python 2.5.Ok, so I should forget Python2.5... My only problem is that I run some jobs on a cluster which (until now) only know Python 2.5 (or 2.4 !) but I may manage soon to have Python2.6 on these machines.
As of version 0.6, the Python interface of igraph will support Python 3.x, but Python 2.x support will not be dropped at all. I myself have not adopted Python 3.x so far and it is unlikely that I will do so in the near future (due to lack of Py3.x support for NumPy/SciPy and many other packages I use). So, these are for sure:The question in fact is more about Python3 adoption... what is it plan for igraph ?
igraph 0.6 will support Python 3.1 and above igraph 0.6 will support Python 2.6 and aboveigraph 0.6 MAY support Python 2.5 if I find it easy enough to backport my recent changes to Python 2.6
Best, Tamas
[Prev in Thread] | Current Thread | [Next in Thread] |