Thanks.
And, yes, know it wasn't specifically python-win32 specific <smile>, but, in
terms of platform compatibility, my primary issue thus far has been generating
windows executables while making use of various external modules, and one of
the new releases along the lines of this is a newer version of py2exe, but,
only for python 3.3 upwards, and that's pretty much why even considered moving
over to newer version of python itself, but, on other hand, seems am managing
to work with what I want to most of the time, using python 2.7 and cx_freeze to
then generate executables to pass on to end users, on different versions of
windows itself, using workarounds like my relatively recent issue with MP3
playback, etc.
Stay well
Jacob Kruger
Blind Biker
Skype: BlindZA
"Roger Wilco wants to welcome you...to the space janitor's closet..."
----- Original Message -----
From: Bob Hood
To: Jacob Kruger ; python-win32@python.org
Sent: Sunday, 11 May, 2014 11:09 PM
Subject: Re: [python-win32] Python version itself
On 5/11/2014 2:39 PM, Jacob Kruger wrote:
I have thus far been working with python 2.7, for no particular reason
aside from that it's been stable/comfortable/usable from when I really got
going with python, but, while think latest release version of python is
something like 3.4, what are the reasons, if any, for sticking to/with the
older version for a while longer?
Cross platform compatibility? Code updates it will require if moving older
code over to newer interpreter, etc.?
Kind of off topic, but what the heck, I'm bored today. :)
Typically, it's dependencies and the cost of the effort to address them.
Python 3.x literally made language changes that have the potential to break
existing 2.7.x scripts, and I'd imagine the 2.7.x line still has a huge amount
of production dependency (I know it does for us). You can spend the time
retooling your product, and introduce the one-way upgrade in a new release, but
that trickles down to your customers, forcing them to spend time updating any
collection of Python tools they themselves may have created.
Personally, I've not seen anything in Python 3.x that is sexy enough to make
me want to put forth the effort. I have yet to run into something I cannot
accomplish using 2.7.x that 3.x makes possible (which is likely another reason
that the transition is so slow).
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
