Insteon, wtdio, w800rf32 and arduino ported to python 3

[George Farris]

Greetings all,

I have updated the Insteon, w800rf32, wtdio and arduion interfaces to
run under Python 3. This is further to the work that David has done
porting Pytomation to Python 3. Along with these changes
are some bug fixes as well. All this can be found in the
features/python3 branch in git.

I have also updated the News portion of the Pytomation web site.

Cheers
George

[David Heaps]

Awesome, I also merged those changes to the dev branch.

I noticed that you removed some Python 2 specific code. I think we might want to add that back. I'd like for it to be capable of running in either Python 2 or 3. That may become a bit much with the character encodings and if it is, we can drop the Python 2 support; I'd just rather not, if it can be avoided.

George

--
You received this message because you are subscribed to the Google Groups "pytomation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pytomation+unsubscribe@googlegroups.com.
To post to this group, send email to pytom...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[George Farris]

From the Insteon code yeah. I guess I thouight since it was Python 3 and we were moving forward it wasn't required but sure we can put it back. I actually think the Python 3 code runs better but I don't have any difinitive facts to support that. I beleive Python 2 is officially supported until 2020.

What about moving the Python 2 code to a separate branch and basing master off the Python 3 code? That way we can use more features from Python 3 as we move forward and not worry about compatibility?

I'm good either way though.

George

To unsubscribe from this group and stop receiving emails from it, send an email to pytomation+...@googlegroups.com.

[David Heaps]

What features of Python 3 are you referring to? The only thing that I see different in the code is the character encoding: byte arrays vs. strings. The other code would run in Python 2 just fine... Just slower.

I agree that Python 3 runs better. The only proof I can give is the massively reduced startup time... Along with the logic that Python 3 was built to improve Python 3.

I prefer to allow users to upgrade and everything just work, without them needing to change there setup. That's not always possible though, so if dual support becomes too much, we can just drop Python 2 support. 

I wouldn't want to maintain Python 2 code in a separate branch, as other dev tasks have higher priority and maintaining that would be a serious drain. If the code can't be universal, we should just drop the support.