Merge lp:~jpakkane/evemu/python3-preparation into lp:evemu
Proposed by
Jussi Pakkanen
Status: | Needs review |
---|---|
Proposed branch: | lp:~jpakkane/evemu/python3-preparation |
Merge into: | lp:evemu |
Diff against target: |
112 lines (+20/-2) 9 files modified
python/evemu/__init__.py (+4/-1) python/evemu/base.py (+2/-0) python/evemu/const.py (+2/-0) python/evemu/exception.py (+2/-0) python/evemu/testing/result.py (+3/-1) python/evemu/testing/runner.py (+2/-0) python/evemu/testing/testcase.py (+2/-0) python/evemu/tests/test_base.py (+2/-0) python/evemu/tests/test_device.py (+1/-0) |
To merge this branch: | bzr merge lp:~jpakkane/evemu/python3-preparation |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot (community) | continuous-integration | Needs Fixing | |
Open Input Framework Team | Pending | ||
Review via email: mp+100103@code.launchpad.net |
Description of the change
Python 3 is coming. This branch prepares for that by cleaning up the code and adding __future__ imports that add stricter checking.
There are very few changes, but personally I would not merge this until after 12/04 has been released.
To post a comment you must log in.
Unmerged revisions
- 55. By Jussi Pakkanen
-
Use unicode literals to prepare for Python 3.
- 54. By Jussi Pakkanen
-
Added absolute_import for Python 3 preparation.
- 53. By Jussi Pakkanen
-
Added print_function to prepare for Python 3.
I don't understand why you bother importing stuff from __future__ that never gets used. For example, there are no print statement in any of this code, so why import print_function? Is it not bad form in Python to import moduoles that do not get used?