Re: python version support

On 11-2-2015 8:42, Thorsten Rangwich wrote:
> Hi Irmen,
> 
> valid when using native Python. But: If you're using it from an
> application that ships with its own Python, then you are not that
> free. Example? Trading system Front Arena. They stayed for an eternity
> on 2.3 and migrated AFAIR directly to 2.6 because that was a huge
> effort to do all over there system with its native C integration.

I didn't immediately think of those instances of Python but yeah, the embedded
interpreters tend to trail behind a long time. Seems like Blender for instance already
sits comfortably on Python 3 though, so this is not generally true!

However am I wrong to assume it is not a big deal for those users (if they use Pyro) to
commit to a specific older Pyro version that still supports 2.6
(and maybe even apply the odd patch themselves if they really require a newer Pyro to
work on their older platform).   Thoughts?


Thing is I want to spend less time on supporting aging platforms. As you all hopefully
know Pyro is still 100% done in my spare time and that time is precious to me :)


> To make that decision based on state of Linux distributions does not
> make sense anyway, in my opinion. They're almost immediatly on the
> latest state anyway. Using the slowest one (Solaris) is a much better
> indicator. Don't know which default is used there.

http://docs.oracle.com/cd/E23824_01/html/820-0696/gktgg.html

Python 2.6. Damn.  Slowlaris :)
It does say you can install multiple versions.


Irmen


------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/