[Python-Dev] Removing memoryview object patch from Python 2.7 (original) (raw)
Sesha Narayanan Subbiah sesha.subbiah at gmail.com
Wed Dec 14 00:10:50 EST 2016
- Previous message (by thread): [Python-Dev] Removing memoryview object patch from Python 2.7
- Next message (by thread): [Python-Dev] Removing memoryview object patch from Python 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
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.
Thanks Sesha
On Tue, Dec 13, 2016 at 11:49 PM, Robert Collins <robertc at robertcollins.net> wrote:
On 14 December 2016 at 01:26, Sesha Narayanan Subbiah <sesha.subbiah at gmail.com> wrote: > Hello > > > I have some implementation that currently uses python 2.6.4, which I m > trying to upgrade to Python 2.7.6. After upgrade, I get the following error: > > > "expected string or Unicode object, memoryview found" > > > On checking further, I could find that memory view object has been back > ported to python 2.7 using this patch: > > > https://bugs.python.org/issue2396 > > > I would like to know if it is safe to revert this patch alone from Python > 2.7.6, or do we know if there are any other dependencies?
I'm not sure - if you're going to run with old, custom, builds of Python, you're probably best served by testing comprehensively for this yourself. That said, I have to presume that the error you're getting is from some code that should be changed anyway, and will need to be changed when you move to Python 3. Please remember that Python 2.7.6 was released in 2013 - there have been many security issues since then, including some of the most egregious SSL issues ever, which should prompt you to run the latest 2.7 branch (if you're unable to migrate straight to 3.x. -Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20161214/40cc46c6/attachment.html>
- Previous message (by thread): [Python-Dev] Removing memoryview object patch from Python 2.7
- Next message (by thread): [Python-Dev] Removing memoryview object patch from Python 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]