On Wed, Oct 8, 2008 at 2:41 PM, Ravi firstname.lastname@example.org wrote:
The majority of my colleagues work on Windows and are very resistant to toolset changes. Hence, from my perspective, whenever a new project starts, it is very important to start with the latest version of any software packages used. Usually, over the typical 3-4 year lifetime of a project, the tools are never updated unless there is an absolutely critical bug fix. We are still on python 2.2 for a couple of currently active projects (neither of which uses numpy). For the next project, I was hoping to use Python 2.6 + numpy 1.2 as the base versions, but that seems unworkable now.
How about python 2.5 and numpy 1.2 instead? Python 2.6 makes some important changes to python 2.5 (in preparation for Python 3.0), so you may find several other packages will take a couple of months to work 100% with python 2.6 - so check this out if you do plan to use more than just numpy. There are sometimes drawbacks to using brand new releases ;)