Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is Python 2.7, need to upgrade to 3 #59

Open
ryanteck opened this issue Aug 13, 2020 · 3 comments
Open

Is Python 2.7, need to upgrade to 3 #59

ryanteck opened this issue Aug 13, 2020 · 3 comments

Comments

@ryanteck
Copy link
Contributor

We need to upgrade this to Python 3 at one stage as Python 2.7 is EOL.

@tvoverbeek
Copy link
Collaborator

Yes, also the i2c code needs some refresh.

@shawaj
Copy link
Member

shawaj commented Nov 18, 2020

@ryanteck @tvoverbeek could this be the same thing causing #52 ?

@ryanteck
Copy link
Contributor Author

@shawaj The customer who first had an issue turned out a replacement board fixed it so it could be a hardware issue.

I don't actually see any Python 2 errors causing #52 as the error message is only given when quitting which doesn't make me think Python 2 is to blame.

Weather the I2C code is causing it I'm not sure, as back in july I did some tweaks to fix the most common error I believe.

I don't think I have a Flick HAT or pHAT so could look at doing the python 3 upgrade if you could send one over (I should only need 1 of the 2 and not both). I think I have the big one but a HAT version would be slightly tidier to work with.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants