oj-toolkit 0.2.1__tar.gz → 0.2.2__tar.gz

{oj_toolkit-0.2.1 → oj_toolkit-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: oj-toolkit
-Version: 0.2.1
+Version: 0.2.2
 Summary: Centralized shared utilities for ownjoo-org projects: standardized logging config, type validation, data parsing, console output, and async utilities
 Author-email: Speedy <speedy@ownjoo.org>
 License: MIT
@@ -719,6 +719,12 @@ else:
 
 Returns `True` if the terminal likely supports Unicode characters. Used internally to choose between ASCII and Unicode box/table borders.
 
+Checks `NO_COLOR`/`CI`/`TERM` env vars first, then verifies `sys.stdout.encoding` can actually
+encode a box-drawing character -- this catches Windows consoles that default to a codepage
+(`cp1252`, `cp437`, etc.) that can't, even though the platform/terminal is otherwise
+Unicode-capable. Set `PYTHONIOENCODING=utf-8` (or use Windows Terminal with a UTF-8 codepage)
+to get Unicode borders on Windows instead of the ASCII fallback.
+
 ### `parsing` Module
 
 #### `validate(v, exp=None, default=None, converter=None, validator=None, pattern=None, **kwargs)`

{oj_toolkit-0.2.1 → oj_toolkit-0.2.2}/README.md

@@ -684,6 +684,12 @@ else:
 
 Returns `True` if the terminal likely supports Unicode characters. Used internally to choose between ASCII and Unicode box/table borders.
 
+Checks `NO_COLOR`/`CI`/`TERM` env vars first, then verifies `sys.stdout.encoding` can actually
+encode a box-drawing character -- this catches Windows consoles that default to a codepage
+(`cp1252`, `cp437`, etc.) that can't, even though the platform/terminal is otherwise
+Unicode-capable. Set `PYTHONIOENCODING=utf-8` (or use Windows Terminal with a UTF-8 codepage)
+to get Unicode borders on Windows instead of the ASCII fallback.
+
 ### `parsing` Module
 
 #### `validate(v, exp=None, default=None, converter=None, validator=None, pattern=None, **kwargs)`

{oj_toolkit-0.2.1 → oj_toolkit-0.2.2}/oj_toolkit/console/terminal.py

@@ -48,13 +48,18 @@ def detect_unicode_support() -> bool:
     """Detect if terminal supports Unicode characters.
 
     Checks environment variables and terminal type to determine if the terminal
-    can display Unicode characters (for pretty borders, etc.).
+    can display Unicode characters (for pretty borders, etc.), then verifies
+    sys.stdout's actual encoding can render them.
 
     Environment checks:
     - NO_COLOR: If set, disables colors/Unicode for accessibility
     - TERM: Terminal type (vt100, xterm, etc.)
     - CI: If in CI environment, assume Unicode support
-    - Platform: Windows console has limited Unicode, *nix terminals usually support it
+    - stdout encoding: Windows consoles commonly default to a codepage (cp1252,
+      cp437, etc.) that can't encode box-drawing characters even when the
+      platform/terminal is otherwise capable -- this is checked directly rather
+      than assumed from sys.platform, since PYTHONIOENCODING/chcp/Windows
+      Terminal all change what's actually possible independent of the OS.
 
     Returns:
         True if terminal likely supports Unicode, False otherwise.
@@ -78,20 +83,19 @@ def detect_unicode_support() -> bool:
     if term in ("dumb", "vt100", "vt220"):
         return False
 
-    # Windows console (cmd.exe, PowerShell) has limited Unicode support
-    # but modern versions and Windows Terminal support it
-    if sys.platform == "win32":
-        # Assume modern Windows (10+) or Windows Terminal supports Unicode
-        # Could be more conservative here if needed
+    # Verify stdout can actually encode a representative box-drawing character.
+    # Windows consoles commonly default to a codepage (cp1252, cp437, etc.) that
+    # can't, even when the platform/terminal is otherwise Unicode-capable.
+    try:
+        "─".encode(sys.stdout.encoding)
         return True
-
-    # *nix terminals typically support Unicode
-    if sys.platform in ("linux", "darwin"):
+    except UnicodeEncodeError:
+        return False
+    except (AttributeError, TypeError, LookupError):
+        # stdout has no usable encoding (e.g. a mock/capture stream in tests) --
+        # can't verify either way, so don't penalize it.
         return True
 
-    # Default: attempt Unicode
-    return True
-
 
 def select_style(
     style: str,

{oj_toolkit-0.2.1 → oj_toolkit-0.2.2}/oj_toolkit.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: oj-toolkit
-Version: 0.2.1
+Version: 0.2.2
 Summary: Centralized shared utilities for ownjoo-org projects: standardized logging config, type validation, data parsing, console output, and async utilities
 Author-email: Speedy <speedy@ownjoo.org>
 License: MIT
@@ -719,6 +719,12 @@ else:
 
 Returns `True` if the terminal likely supports Unicode characters. Used internally to choose between ASCII and Unicode box/table borders.
 
+Checks `NO_COLOR`/`CI`/`TERM` env vars first, then verifies `sys.stdout.encoding` can actually
+encode a box-drawing character -- this catches Windows consoles that default to a codepage
+(`cp1252`, `cp437`, etc.) that can't, even though the platform/terminal is otherwise
+Unicode-capable. Set `PYTHONIOENCODING=utf-8` (or use Windows Terminal with a UTF-8 codepage)
+to get Unicode borders on Windows instead of the ASCII fallback.
+
 ### `parsing` Module
 
 #### `validate(v, exp=None, default=None, converter=None, validator=None, pattern=None, **kwargs)`

{oj_toolkit-0.2.1 → oj_toolkit-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "oj-toolkit"
-version = "0.2.1"
+version = "0.2.2"
 description = "Centralized shared utilities for ownjoo-org projects: standardized logging config, type validation, data parsing, console output, and async utilities"
 authors = [
     { name = "Speedy", email = "speedy@ownjoo.org" }