view .hgignore @ 5543:bc3e00a3d24b

MySQL backend fixes for Python 3. With Python 2, text sent to and from MySQL is treated as bytes in Python. The database may be recorded by MySQL as having some other encoding (latin1 being the default in some MySQL versions - Roundup does not set an encoding explicitly, unlike in back_postgresql), but as long as MySQL's notion of the connection encoding agrees with its notion of the database encoding, no conversions actually take place and the bytes are stored and returned as-is. With Python 3, text sent to and from MySQL is treated as Python Unicode strings. When the database and connection encoding is latin1, that means the bytes stored in the database under Python 2 are interpreted as latin1 and converted from that to Unicode, producing incorrect results for any non-ASCII characters; furthermore, if trying to store new non-ASCII data in the database under Python 3, any non-latin1 characters produce errors. This patch arranges for both the connection and database character sets to be UTF-8 when using Python 3, and documents a need to export and import the database when moving from Python 2 to Python 3 with this backend.
author Joseph Myers <jsm@polyomino.org.uk>
date Sun, 16 Sep 2018 16:19:20 +0000
parents 8e34362a14f7
children b57c3d50505b
line wrap: on
line source

syntax: glob

*.orig
*.rej
*~
\#*\#
.\#*
*.swp
*.tmp
*.pyd
*.pyc
*.pyo
build
demo
dist
MANIFEST
_test_*
*.cover
share/doc/roundup/html
doc/FAQ.html
doc/admin_guide.html
doc/announcement.html
doc/customizing.html
doc/design.html
doc/developers.html
doc/features.html
doc/glossary.html
doc/implementation.html
doc/index.html
doc/installation.html
doc/mysql.html
doc/overview.html
doc/postgresql.html
doc/security.html
doc/tracker_templates.html
doc/upgrading.html
doc/user_guide.html
doc/whatsnew-0.7.html
doc/whatsnew-0.8.html
doc/xmlrpc.html
locale/*.mo
locale/*.bak
locale/*.poedit
website/www/_tmp/
website/www/COPYING.txt
website/www/docs
website/www/html/

Roundup Issue Tracker: http://roundup-tracker.org/