Thanks Rob. I will try upgrade to 2.7.12. Any idea of this memory view object that has been back ported to 2.7 can be disabled in any way?
Thanks Regards Sesha On Wed, Dec 14, 2016, 17:33 Robert Collins <robe...@robertcollins.net> wrote: > On 14 December 2016 at 18:10, Sesha Narayanan Subbiah > <sesha.subb...@gmail.com> wrote: > > Hi Rob > > > > Thanks for your reply. > > > > From http://legacy.python.org/download/, I could see that the current > > production releases are Python 3.4 and Python 2.7.6. > > Nope - https://www.python.org/downloads/ - 2.7.12 and 3.5.2 are > current. The 'legacy' domain there was from a site revamp, I think its > causing confusion at this point and we should look at retiring it > completely. > > > Since we use python for some our legacy applications, we don't want to > > switch to Python 3.0 right now. Moreover, since Python 2.6 is not > supported > > anymore, we want to upgrade to Python 2.7. > > > Do you suggest I should use Python 2.7.12 which is the latest version in > 2.7 > > series? I picked up 2.7.6, since it was listed as production release and > > assumed it is the most stable version. > > If you can, 3.5.2 is where to switch to. If that won't work, 2.7.12 yes. > > -Rob >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
