Python 3 migration

[decentral1se]

AFAICT, pi-scan still works on Python 2 and the raspbian image it builds too. Python 2 is EOL'd however and raspbian ecosystem is moving along. The longer pi-scan leaves upgrade work undone, the potentially more difficult it can become later on.

So, I am wondering if there is some motivation to migrate the code base to Python 3. Typically this migration process is low priority but I thought I'd raise the issue regardless.

#17 is related (if I could build new images, I could start to experiment with this migration process).

[duerig]

It will be important to migrate to Python 3 soon. Once you are familiar with the build process for general Raspbian images and I help get you started with the build process for this, I'd be happy to accept a conversion patch. I don't expect the transition to be difficult, mostly a matter of updating to the new exceptions syntax.

…

On Sun, Jan 19, 2020, at 5:07 AM, decentral1se wrote: AFAICT, pi-scan still works on Python 2 and the raspbian image it builds too. Python 2 is EOL'd however and raspbian ecosystem is moving along. The longer pi-scan leaves upgrade behind, the potentially more difficult it can become later on. So, I am wondering if there is some motivation to migrate the code base to Python 3. Typically this migration process is low priority but I thought I'd raise the issue regardless. #17 <#17> is related (if I could build new images, I could start to experiment with this migration process). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#20?email_source=notifications&email_token=AAGWYTAVD2LTPTY52WRK6GTQ6Q66RA5CNFSM4KIY4MR2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IHFQYPQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGWYTECVQWIZ5OKLYU2C6TQ6Q66RANCNFSM4KIY4MRQ>.