0

We are developing a tool and use various third party modules. Currently everything is running on python 2.5 but this causes a lot of problems. We would like to update to python 2.7, but 1 (One) module is 2.5 only. Is there a good way to run 1 package on a different python version. The only way we can think of is with threads, but maybe there is something simpler?

TomM
  • 23
  • 4
  • Most modules written for 2.5 can run just fine on Python 2.7. If the module does not work on 2.7, there is no way for you to somehow run it on an older version, not without extensive inter-process message passing, anyway. – Martijn Pieters Sep 29 '15 at 14:28
  • Not this one though. We tried, but it didn't work. Also there is no support to get it running on 2.7. – TomM Sep 29 '15 at 14:30
  • 1
    Then you are out of luck, unless you write some kind of daemon in Python 2.5 to run the module then pass messages between processes. – Martijn Pieters Sep 29 '15 at 14:31
  • 1
    See e.g. http://stackoverflow.com/q/17665124/3001761 – jonrsharpe Sep 29 '15 at 14:32
  • If you have the source code for the library, upgrade it to run on Python 2.7. – Martijn Pieters Sep 29 '15 at 14:32
  • What errors do you get if you run the module on 2.5 ? – Alex Sep 29 '15 at 14:32
  • Why can't you just contribute a patch for this third-party module? – ekhumoro Sep 29 '15 at 14:58
  • We don't gave the source. The error I get is "bad magic number", complete in line with trying to run a compiled file in the wrong version of Python. – TomM Sep 30 '15 at 15:47
  • @TomM. What exactly *is* this third-party package? What does it do? Have you looked for alternatives? – ekhumoro Sep 30 '15 at 17:13

0 Answers0