fa-console 2.0.0__tar.gz → 2.0.2__tar.gz

{fa_console-2.0.0 → fa_console-2.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fa-console
-Version: 2.0.0
+Version: 2.0.2
 Summary: Correct Persian (Farsi) console input/output for Python on Windows: automatic UTF-8 setup plus visual letter shaping and bidi for the classic console.
 Author-email: Alireza Hosseini <alireza.hosseini@hotmail.com>
 License: MIT
@@ -87,9 +87,10 @@ It fixes both independent layers of the problem:
 - ✅ **Live-typing echo** — `fa_input()` renders letters joined and right-to-left
   *while you type*, with built-in-`input()`-compatible semantics
   (`KeyboardInterrupt` / `EOFError`)
-- ✅ **Smart detection** — Windows Terminal, VS Code-style terminals, IDEs and
-  redirected files/pipes are detected and left untouched (standard text flows
-  there, as it should)
+- ✅ **Smart detection** — Windows Terminal and redirected files/pipes are
+  left untouched; the VS Code integrated terminal gets the same visual
+  transform as the classic console (its xterm.js engine lacks reliable
+  bidi reordering)
 - ✅ **Fail-open design** — the module never crashes the host application; every
   internal failure is logged through the `fa_console` logger and degrades
   gracefully to standard Python behaviour
@@ -175,7 +176,8 @@ terminal type, active bidi backend and a rendered sample.
 |-------------|-----------|
 | `cmd.exe` / standalone PowerShell (conhost) | Encoding fixed + visual transform + live typing echo |
 | Windows Terminal | Encoding fixed; native rendering (module steps aside) |
-| VS Code / JetBrains / IDLE consoles | Encoding fixed; module steps aside |
+| VS Code integrated terminal | Encoding fixed + visual transform (xterm.js has no reliable bidi) |
+| JetBrains / IDLE consoles | Encoding fixed; module steps aside (non-tty) |
 | Output redirected to file / pipe | Standard logical UTF-8 — safe for other tools |
 | Linux / macOS | Safe no-op (standard behaviour) |
 
@@ -188,6 +190,10 @@ terminal type, active bidi backend and a rendered sample.
   — the module detects it and lets it do the shaping.
 - **Does the transform corrupt my data?** No — it is display-only. Values,
   comparisons and files always hold logical text.
+- **Persian looks wrong in the VS Code terminal.** That is an xterm.js
+  limitation — this package compensates automatically by applying the same
+  visual transform used for the classic console (see
+  `FA_CONSOLE_NO_VISUAL=1` if you ever need to switch it off).
 - **Other RTL languages?** The shaping tables cover Arabic and Persian letters;
   the engine is language-agnostic for the letters it knows.
 

{fa_console-2.0.0 → fa_console-2.0.2}/README.md

@@ -50,9 +50,10 @@ It fixes both independent layers of the problem:
 - ✅ **Live-typing echo** — `fa_input()` renders letters joined and right-to-left
   *while you type*, with built-in-`input()`-compatible semantics
   (`KeyboardInterrupt` / `EOFError`)
-- ✅ **Smart detection** — Windows Terminal, VS Code-style terminals, IDEs and
-  redirected files/pipes are detected and left untouched (standard text flows
-  there, as it should)
+- ✅ **Smart detection** — Windows Terminal and redirected files/pipes are
+  left untouched; the VS Code integrated terminal gets the same visual
+  transform as the classic console (its xterm.js engine lacks reliable
+  bidi reordering)
 - ✅ **Fail-open design** — the module never crashes the host application; every
   internal failure is logged through the `fa_console` logger and degrades
   gracefully to standard Python behaviour
@@ -138,7 +139,8 @@ terminal type, active bidi backend and a rendered sample.
 |-------------|-----------|
 | `cmd.exe` / standalone PowerShell (conhost) | Encoding fixed + visual transform + live typing echo |
 | Windows Terminal | Encoding fixed; native rendering (module steps aside) |
-| VS Code / JetBrains / IDLE consoles | Encoding fixed; module steps aside |
+| VS Code integrated terminal | Encoding fixed + visual transform (xterm.js has no reliable bidi) |
+| JetBrains / IDLE consoles | Encoding fixed; module steps aside (non-tty) |
 | Output redirected to file / pipe | Standard logical UTF-8 — safe for other tools |
 | Linux / macOS | Safe no-op (standard behaviour) |
 
@@ -151,6 +153,10 @@ terminal type, active bidi backend and a rendered sample.
   — the module detects it and lets it do the shaping.
 - **Does the transform corrupt my data?** No — it is display-only. Values,
   comparisons and files always hold logical text.
+- **Persian looks wrong in the VS Code terminal.** That is an xterm.js
+  limitation — this package compensates automatically by applying the same
+  visual transform used for the classic console (see
+  `FA_CONSOLE_NO_VISUAL=1` if you ever need to switch it off).
 - **Other RTL languages?** The shaping tables cover Arabic and Persian letters;
   the engine is language-agnostic for the letters it knows.
 

{fa_console-2.0.0 → fa_console-2.0.2}/fa_console.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fa-console
-Version: 2.0.0
+Version: 2.0.2
 Summary: Correct Persian (Farsi) console input/output for Python on Windows: automatic UTF-8 setup plus visual letter shaping and bidi for the classic console.
 Author-email: Alireza Hosseini <alireza.hosseini@hotmail.com>
 License: MIT
@@ -87,9 +87,10 @@ It fixes both independent layers of the problem:
 - ✅ **Live-typing echo** — `fa_input()` renders letters joined and right-to-left
   *while you type*, with built-in-`input()`-compatible semantics
   (`KeyboardInterrupt` / `EOFError`)
-- ✅ **Smart detection** — Windows Terminal, VS Code-style terminals, IDEs and
-  redirected files/pipes are detected and left untouched (standard text flows
-  there, as it should)
+- ✅ **Smart detection** — Windows Terminal and redirected files/pipes are
+  left untouched; the VS Code integrated terminal gets the same visual
+  transform as the classic console (its xterm.js engine lacks reliable
+  bidi reordering)
 - ✅ **Fail-open design** — the module never crashes the host application; every
   internal failure is logged through the `fa_console` logger and degrades
   gracefully to standard Python behaviour
@@ -175,7 +176,8 @@ terminal type, active bidi backend and a rendered sample.
 |-------------|-----------|
 | `cmd.exe` / standalone PowerShell (conhost) | Encoding fixed + visual transform + live typing echo |
 | Windows Terminal | Encoding fixed; native rendering (module steps aside) |
-| VS Code / JetBrains / IDLE consoles | Encoding fixed; module steps aside |
+| VS Code integrated terminal | Encoding fixed + visual transform (xterm.js has no reliable bidi) |
+| JetBrains / IDLE consoles | Encoding fixed; module steps aside (non-tty) |
 | Output redirected to file / pipe | Standard logical UTF-8 — safe for other tools |
 | Linux / macOS | Safe no-op (standard behaviour) |
 
@@ -188,6 +190,10 @@ terminal type, active bidi backend and a rendered sample.
   — the module detects it and lets it do the shaping.
 - **Does the transform corrupt my data?** No — it is display-only. Values,
   comparisons and files always hold logical text.
+- **Persian looks wrong in the VS Code terminal.** That is an xterm.js
+  limitation — this package compensates automatically by applying the same
+  visual transform used for the classic console (see
+  `FA_CONSOLE_NO_VISUAL=1` if you ever need to switch it off).
 - **Other RTL languages?** The shaping tables cover Arabic and Persian letters;
   the engine is language-agnostic for the letters it knows.
 

{fa_console-2.0.0 → fa_console-2.0.2}/fa_console.py

@@ -92,11 +92,12 @@ downstream tools receive standards-compliant UTF-8.
 Scope and limitations
 ---------------------
 
-* The visual transform targets classic ``conhost``. Windows Terminal
-  (``WT_SESSION``) and VS Code-style terminals (``TERM_PROGRAM``) render
-  Arabic correctly by themselves; the module detects them and steps
-  aside. Escape hatches: ``FA_CONSOLE_FORCE_VISUAL=1`` forces the
-  transform on, ``FA_CONSOLE_NO_VISUAL=1`` forces it off.
+* The visual transform targets the classic console host (``conhost``) and
+  the VS Code integrated terminal — xterm.js has no reliable bidirectional
+  reordering, so logical Persian renders disconnected/backwards there.
+  Windows Terminal (``WT_SESSION``) shapes and reorders Arabic natively
+  and is left untouched. Escape hatches: ``FA_CONSOLE_FORCE_VISUAL=1``
+  forces the transform on, ``FA_CONSOLE_NO_VISUAL=1`` forces it off.
 * The live-typing editor mirrors built-in ``input()`` semantics
   (``KeyboardInterrupt`` on Ctrl+C, ``EOFError`` on Ctrl+Z) but provides
   no history or cursor movement; arrow keys are consumed and ignored.
@@ -137,7 +138,7 @@ from typing import Any, Iterator
 
 __author__ = "Alireza Hosseini"
 __email__ = "alireza.hosseini@hotmail.com"
-__version__ = "2.0.0"
+__version__ = "2.0.2"
 
 __all__ = [
     "FaConsoleError",
@@ -479,11 +480,21 @@ def _reconfigure_stream(name: str) -> bool:
 
 def _modern_terminal() -> bool:
     """
-    ``True`` for terminals that shape and reorder Arabic text natively
-    (Windows Terminal, VS Code-style terminals). The visual transform
-    stays off there to avoid double processing.
+    ``True`` for terminals that shape and reorder Arabic text natively and
+    reliably — Windows Terminal (``WT_SESSION``) and other ``TERM_PROGRAM``
+    hosts (mintty, etc.).
+
+    Note:
+        VS Code's integrated terminal (``TERM_PROGRAM=vscode``, powered by
+        xterm.js) deliberately does **not** count as modern: xterm.js lacks
+        reliable bidirectional reordering for RTL text, so logical Persian
+        appears disconnected/backwards there. The visual transform is
+        therefore applied inside VS Code as well.
     """
-    return bool(os.environ.get("WT_SESSION") or os.environ.get("TERM_PROGRAM"))
+    if os.environ.get("WT_SESSION"):
+        return True
+    term_program = os.environ.get("TERM_PROGRAM")
+    return bool(term_program) and term_program != "vscode"
 
 
 # --------------------------------------------------------------------------- #
@@ -1071,6 +1082,7 @@ def get_console_info() -> dict[str, Any]:
         "stdout_isatty": _stream_isatty(sys.stdout),
         "console_codepage": _get_console_output_codepage(),
         "modern_terminal": _modern_terminal(),
+        "term_program": os.environ.get("TERM_PROGRAM"),
         "visual_mode": _visual_mode,
         "bidi_backend": _transformer.backend_name if _visual_mode else "none",
         "force_visual_env": bool(os.environ.get(ENV_FORCE_VISUAL)),

{fa_console-2.0.0 → fa_console-2.0.2}/pyproject.toml

@@ -4,7 +4,9 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "fa-console"
-version = "2.0.0"
+# Single source of truth: the version lives in fa_console.__version__ and is
+# injected here at build time, so it can never drift between module and package.
+dynamic = ["version"]
 description = "Correct Persian (Farsi) console input/output for Python on Windows: automatic UTF-8 setup plus visual letter shaping and bidi for the classic console."
 readme = "README.md"
 requires-python = ">=3.8"
@@ -56,3 +58,6 @@ Issues = "https://github.com/Padandish/fa-console/issues"
 [tool.setuptools]
 # Flat layout: publish the single module without restructuring the folder.
 py-modules = ["fa_console"]
+
+[tool.setuptools.dynamic]
+version = { attr = "fa_console.__version__" }