Difference between revisions of "User:Alvonruff"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
* Python3 does not tolerate mixed tabs and spaces. Convert tabs in all files to 8 spaces. | * Python3 does not tolerate mixed tabs and spaces. Convert tabs in all files to 8 spaces. | ||
| − | * Use [[User:Alvonruff/Python2.7_Futurize]] to perform a mass conversion from python2.7 syntax to python3 syntax. | + | * Use [[User:Alvonruff/Python2.7_Futurize]] to perform a mass conversion from python2.7 syntax to python3 syntax. This allows for locating potential unicode issues. This produces a result suitable for python2. |
| + | * Use 2to3 in a manner the same as futurize. This produces results suitable for python3. | ||
* Use of md5 needs to be replaced with hashlib | * Use of md5 needs to be replaced with hashlib | ||
* The next two items need to be done together, as there is no mysql-connector-python for python2: | * The next two items need to be done together, as there is no mysql-connector-python for python2: | ||
Revision as of 08:53, 24 April 2023
Founder of the ISFDB.
Python3 Notes
General outline of steps to move to Python3:
- Python3 does not tolerate mixed tabs and spaces. Convert tabs in all files to 8 spaces.
- Use User:Alvonruff/Python2.7_Futurize to perform a mass conversion from python2.7 syntax to python3 syntax. This allows for locating potential unicode issues. This produces a result suitable for python2.
- Use 2to3 in a manner the same as futurize. This produces results suitable for python3.
- Use of md5 needs to be replaced with hashlib
- The next two items need to be done together, as there is no mysql-connector-python for python2:
- Update to the official MySQL User:Alvonruff/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 leverages the futurize work, by removing the "from __future__" lines.
- Update all character sets. Final procedure still TBD.
- Change the default charset in MySQL
- Repair strings which have URL encodings in MySQL
System Upgrade Notes
Details on how to bring up a LAMP stack (on two different OSs), and how to setup https:
- User:Alvonruff/ISFDB_Move - Our old hosting service was bought out by a larger hosting service, and they are pushing off our ancient server onto something up to date. We've already been staging such a move at isfdb2.org for a few months, and have most things operational on the new server. The actual move will start sometime after Labor Day.
- User:Alvonruff/ISFDB On Ubuntu 20.04
- User:Alvonruff/ISFDB2_Notes - Another Fedora Core variant.
- User:Alvonruff/HTTPS Notes - Notes on moving to https on isfdb2
- User:Alvonruff/Link Tests - Combinations of http/https www/no www links.
Other Loose Notes
- Development/HTTPS - Discussion area.
- User:Alvonruff/The_Charset_Problem
- User:Alvonruff/Notes on MySQLdb
- User:Alvonruff/Test_Pages
Obituary Sources
- https://sf-encyclopedia.com/timeline.php?rip
- https://ansible.uk/ - (R.I.P. section)
- https://www.sfwa.org/category/excluded-categories/in-memoriam/