Feature #18301
Apply code modernization
0%
Description
Thomas worked this summer to migrate the code towards python 3.
1. modernize the code to python 2.6, 2.7 standards
2. migrate to python 3
Part one changes are beneficial to the current code base and should be merged
Related issues
History
#1 Updated by Marco Mambelli almost 3 years ago
- Tracker changed from Bug to Feature
- Status changed from New to Feedback
- Assignee changed from Marco Mambelli to Dennis Box
changes are in branch migration_3_1
I merged branch_v3_2 to include what we changed in the meantime
#2 Updated by Marco Mambelli almost 3 years ago
- Status changed from Feedback to Resolved
- Assignee changed from Dennis Box to Marco Mambelli
Following Parag's suggestion, I did a rebase of migration_3_1, called migration_3_1_rebase.
This requested manual corrections and highlighted some differences from the merge.
The fixed code includes Dennis's fixes (one came automatically, I applied the other by hand).
PEP8 warnings went from around 1800 to 1125. Futurize to refactor files went from 126 to 0.
Future merges to branch_v3_2 will have to maintain the futurize tests compliance.
#3 Updated by Marco Mambelli almost 3 years ago
- Target version changed from v3_2_22 to v3_2_23
#4 Updated by Marco Mambelli over 2 years ago
- Target version changed from v3_2_23 to v3_4_0
#5 Updated by Marco Mambelli over 2 years ago
- Status changed from Resolved to Closed
#6 Updated by Marco Mambelli 8 months ago
- Related to Feature #20227: Migrate to Python3 added