Next Pyweek : please use python3 !!!

Buffalo974 on 2017/06/30 18:17

For pedagocic purpose , it should be better to integrate obligation do give python3 working source.
It's painfull to 2to3 all interesting code source and finally have broken code.

transition

(log in to comment)

Comments

DR0ID on 2017/06/30 18:48:

Well, for the newer pyweeks this might be true, but for the older ones it would have been a bit difficult to code in py3 without its existence...

Buffalo974 on 2017/06/30 20:12:

of course you are right.

But Python 3.0 was released on December 3rd, 2008. so , it's time now.

Buffalo974 on 2017/09/28 07:28:

BitWarp on 2018/04/06 01:21:

Some of the stuff I want to use has been largely tested with Python 2.7 and Python 3.4

I've just found it's buggy with Python 3.6 and Python 2.7 or Python 3.4 are the way to go.

Will Python 3.4 be allowed even though Python 3.6 is the newest?

Zuzu_Typ on 2018/04/06 12:47:

There is no rule saying you couldn't use an earlier version of Python (like 3.4 or 2.7), it's only a warm-hearted recommendation.

For example:

PyHook simply doesn't work right on Python 3 on Windows 10, crashing when hovering over the taskbar, etc. which is why sometimes Python 2 is the only choice.

If you distribute your game as a binary executable, you won't have this problem anyway, because people aren't required to have a second Python 2 install (which I would recommend to anyone, but iguessyougottaknowwhat'sbestforyou..)

BitWarp on 2018/04/06 17:18:

What's the best way to make a binary executable ?

Zuzu_Typ on 2018/04/06 17:25:

The best (and easiest) way would be PyInstaller.