Difference between revisions of "User:Alvonruff/Python3"
Jump to navigation
Jump to search
(Replaced content with "There are two major steps to move to python3: * Update to the official MySQL connector. There is no python3 support for MySQLdb, which is our current connector. Moving to...") Tag: Replaced |
|||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
There are two major steps to move to python3: | There are two major steps to move to python3: | ||
+ | * Fix the inconsistent tabs/spaces problem in numerous files (pretty much every file attempted so far). It appears that 8-spaces is far more popular than tabs. | ||
* Update to the official MySQL connector. There is no python3 support for MySQLdb, which is our current connector. Moving to a new connector is a prerequisite. | * Update to the official MySQL connector. There is no python3 support for MySQLdb, which is our current connector. Moving to a new connector is a prerequisite. | ||
− | * Update to python3 | + | * Update to python3. This can leverage the futurize work, by removing the "from __future__" lines. |
+ | * Change the default charset in MySQL | ||
+ | * Repair strings which have URL encodings in MySQL |
Latest revision as of 19:31, 11 April 2023
There are two major steps to move to python3:
- Fix the inconsistent tabs/spaces problem in numerous files (pretty much every file attempted so far). It appears that 8-spaces is far more popular than tabs.
- Update to the official MySQL connector. There is no python3 support for MySQLdb, which is our current connector. Moving to a new connector is a prerequisite.
- Update to python3. This can leverage the futurize work, by removing the "from __future__" lines.
- Change the default charset in MySQL
- Repair strings which have URL encodings in MySQL