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

future_builtins shouldn't be blacklisted #228

Closed
oprypin opened this issue Apr 20, 2014 · 2 comments
Closed

future_builtins shouldn't be blacklisted #228

oprypin opened this issue Apr 20, 2014 · 2 comments

Comments

@oprypin
Copy link

oprypin commented Apr 20, 2014

So I started my Kivy application on Android, only to have it crash right after the loading screen.
To my great surprise, the cause of the problem was:

from future_builtins import *

As I later found out, this is because the module is blacklisted.

This module is very useful for making Python 2 bearable behave more like Python 3 and it makes single-codebase 2.x+3.x compatibility easy. It is also very small (future_builtins.c is 3.0 KiB and future_builtins.so is 7.5 KiB).
I think it should not be blacklisted.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@FeralBytes
Copy link
Contributor

Although I agree. This issue has details to help you use Python 3 syntax.

@inclement
Copy link
Member

This was never blacklisted under SDL2, and I've removed it from the old pygame backend too.

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