Point well taken. It is always a tradeoff / balancing act where you can have 'anything' but not 'everything'. Where would the fun be if we could have everything :) ? . In our situation, there were a couple of extensions that did not work (at least out of the box) in Python 2.7.
Raul On 14/12/2012 1:09 AM, Sturla Molden wrote: > So when upgrading everything you prefer to keep the bugs in 2.6 that were > squashed in 2.7? Who has taught IT managers that older and more buggy > versions of software are more "professional" and better for corporate > environments? > > Sturla > > > Den 14. des. 2012 kl. 05:14 skrev Raul Cota <r...@virtualmaterials.com>: > >> >> +1 from me >> >> For what is worth, we are just moving forward from Python 2.2 / Numeric >> and are going to 2.6 and it has been rather painful because of the >> several little details of extensions and other subtleties. I believe we >> will settle there for a while. For companies like ours, it is a big >> problem to upgrade versions. There is always this or that hiccup that >> "works great" in a version but not so much in another and we also have >> all sorts of extensions. >> >> >> >> Raul >> >> >> >> >> >> On 13/12/2012 9:34 AM, Charles R Harris wrote: >>> Time to raise this topic again. Opinions welcome. >>> >>> Chuck >>> >>> >>> _______________________________________________ >>> NumPy-Discussion mailing list >>> NumPy-Discussion@scipy.org >>> http://mail.scipy.org/mailman/listinfo/numpy-discussion >>> >> >> _______________________________________________ >> NumPy-Discussion mailing list >> NumPy-Discussion@scipy.org >> http://mail.scipy.org/mailman/listinfo/numpy-discussion > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
