upstream-archive/VoiceStudio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test(db): say which installs read alembic.ini

Browse Source 
Review follow-up: packaged desktop installs do not ship alembic.ini, so the
locale decode only reaches from-source runs.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
kevin9327
2026-09-14 08:49:24 +09:00
co-authored by Claude Opus 5
parent 61f99debb4
commit 651b621e4a
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/test_alembic_ini_locale.py
+4 -5
View File
@@ -2,11 +2,10 @@
alembic reads its ini with ``encoding="locale"`` (``alembic.util.compat.
read_config_parser``). On Python 3.11 that is the Windows ANSI code page even
with ``PYTHONUTF8=1``, which the desktop shell sets — so on a Chinese, Japanese
or Korean Windows the em dashes in the ini's comments raised
``UnicodeDecodeError`` inside ``Config()``, and every startup logged
"alembic upgrade head skipped" and never ran a migration or took the
pre-migration backup.
with ``PYTHONUTF8=1`` — so on a Chinese, Japanese or Korean Windows the em
dashes in the ini's comments raised ``UnicodeDecodeError`` inside ``Config()``,
and every startup of a from-source install logged "alembic upgrade head
skipped" and never ran a migration or took the pre-migration backup.
"""
from __future__ import annotations