[BangPypers] Moving from python 2.6 to 2.7
shyran at gmail.com
Wed Oct 8 11:23:39 CEST 2014
Thanks Abdul. Fortunately we don't have any native bindings in the project.
On Oct 8, 2014, at 11:12 AM, Abdul Muneer <abdulmuneer at gmail.com> wrote:
> As far as I know, nothing written in python should break. If you are
> upgrading OS too, then you should be watchful as some of the c libraries
> can introduce version conflicts.
> We had faced such a problem with pyactivemq at our office. Pyactivemq
> depends on activemq-cpp library which in turn depends on a few system
> libraries. The problem was that the development of pyactivemq stagnated
> while activemq-cpp moved on the version checks caused conflicts. If I used
> a version of activemq-cpp that satisfies pyactivemq, activemq-cpp had
> problems with system libraries as they too had moved on to newer versions.
> IIRC, I solved it by changing the regex that looks for the versions.
> Abdul Muneer
> Abdul Muneer
> Follow me on Twitter: @abdulmuneer <http://twitter.com/#%21/abdulmuneer>
> On Tue, Oct 7, 2014 at 3:53 PM, Kulkarni, Shreyas <shyran at gmail.com> wrote:
>> Hi guys,
>> We are planning to move our production environment from 2.6 to 2.7 on one
>> of the projects. While I understand it's not a significant upgrade, this
>> being a production environment, I was wondering what aspects of 2.6 might
>> break under 2.7 and what I should be watching out for. I tried searching
>> about it, but didn't hit anything useful.
>> Anyone here has any suggestions, or has experienced any difficulties after
>> bumping the version to 2.7?
>> Thanks in advance.
>> BangPypers mailing list
>> BangPypers at python.org
> BangPypers mailing list
> BangPypers at python.org
More information about the BangPypers