-
Notifications
You must be signed in to change notification settings - Fork 506
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
Feature: Create a compat.py for correct PY3 support and implement it #300
Comments
It can be started by just adding the file, and using it where we have discussed in the other pr, all the changes doesn't have to happen at once. |
There currently might be a lot of bugs in buildozer when run in py3. Atleast getting it working in py3 under some condition is required I guess. Then addressing bugs one at a time will be possible, else no one will be able to test correctly. |
Are you suggesting that #293 should not use compat now because there may be other bugs in other places where using compat would be the right option? |
The compat file can be added in a separate pr, then you can update #293, if mixing them is your main concern. |
Mixing the pr s was a concern, but my main concern is not being able to test it until other bugs(such as the one I posted another issue about) are resolved. Probably I should rename this issue to "support py3" :P. |
There's another issue regarding supporting py3 #175. |
Python3 is now supported |
If buildozer is to work on Py3, such a file is required.
We can just use this file from kivy: https://github.com/kivy/kivy/blob/master/kivy/compat.py
But implementing it will require replacing current code to use
compat
.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: