Re: Python 3.5 Update

395 views
Skip to first unread message
Message has been deleted

BBands

unread,
Oct 9, 2015, 12:18:17 PM10/9/15
to PyScripter Group
I'm sort of curious about this constant drumbeat calling for updates to the latest Python release. Is there something about 3.5 that makes it a must have for you? A new feature? A bug fix? Or are we just keeping up with the latest?

     John--who is still using 2.7.10

On Fri, Oct 9, 2015 at 1:33 AM, Adwait Chitale <hwo...@gmail.com> wrote:
Is there going to be an update so it is compatible with python 3.5?

Message has been deleted

BBands

unread,
Oct 9, 2015, 6:29:39 PM10/9/15
to PyScripter Group
I hear that. I was wondering why?

Best,

     John

On Fri, Oct 9, 2015 at 2:56 PM, Adwait Chitale <hwo...@gmail.com> wrote:
I want to keep up with the latest release.

Wlerin

unread,
Jan 18, 2016, 4:43:42 PM1/18/16
to PyScripter
For me it's quite simple. I'm starting a new project that will likely be in development for some time, so there's no reason to *not* use the latest Python version. Additionally, the latest version of Ubuntu now uses python 3.5 as the default (and the upcoming LTS likely will as well), so I would prefer to use the same version of Python on all machines for maximum consistency.

I'm sure I'm not the only one in this situation, and as much as I like working with PyScripter, there are other alternatives out there if its not going to support 3.5 in the near future (or rather, now). Granted I don't personally need any of the new functionality afforded by 3.5, at least not yet, so I may just trick PyScripter into loading it as 3.4 until a fix becomes available.

BBands

unread,
Jan 18, 2016, 5:15:13 PM1/18/16
to PyScripter Group
This seems to me to be a very slippery slope as many existing Python scripts written for 2.n.n fail silently or produce out-of-design results without warnings when run on 3.n.n. I know is is uber cool to be on the dump 2.7 band wagon, but I suspect that there are substantial hidden problems, many of which will go unnoticed until real damage is done. The whole focus seems to be on dependencies, which I am glad to see have largely been resolved, but I see almost no focus on existing code hurting users.

     John
Reply all
Reply to author
Forward
0 new messages