pythia-plsql 0.4.2__tar.gz → 0.4.4__tar.gz

{pythia_plsql-0.4.2/scripts/pythia_plsql.egg-info → pythia_plsql-0.4.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythia-plsql
-Version: 0.4.2
+Version: 0.4.4
 Summary: PL/SQL development for AI agents on Oracle Database - expert data-dictionary queries, impact analysis, and a snapshot-verified write path with honest rollback.
 License: MIT
 Project-URL: Homepage, https://github.com/thaildhe172591/pythia
@@ -151,6 +151,11 @@ hand with
 works just as well.
 `pythia check` warns when the session runs with more power than the task needs.
 
+Using Claude Code? [`examples/claude-code-settings.example.json`](examples/claude-code-settings.example.json)
+stops it prompting for the read-only commands and asks it to pause on
+writes — optional, and yours to install
+([why pythia does not](GUIDE.md#11-optional-claude-code-permission-settings)).
+
 Per-group write policy, `.pythia/policy.json` (defaults shown):
 
 | Group | Default | Is rollback real? |

{pythia_plsql-0.4.2 → pythia_plsql-0.4.4}/README.md

@@ -137,6 +137,11 @@ hand with
 works just as well.
 `pythia check` warns when the session runs with more power than the task needs.
 
+Using Claude Code? [`examples/claude-code-settings.example.json`](examples/claude-code-settings.example.json)
+stops it prompting for the read-only commands and asks it to pause on
+writes — optional, and yours to install
+([why pythia does not](GUIDE.md#11-optional-claude-code-permission-settings)).
+
 Per-group write policy, `.pythia/policy.json` (defaults shown):
 
 | Group | Default | Is rollback real? |

{pythia_plsql-0.4.2 → pythia_plsql-0.4.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pythia-plsql"
-version = "0.4.2"
+version = "0.4.4"
 description = "PL/SQL development for AI agents on Oracle Database - expert data-dictionary queries, impact analysis, and a snapshot-verified write path with honest rollback."
 readme = "README.md"
 license = { text = "MIT" }

{pythia_plsql-0.4.2 → pythia_plsql-0.4.4}/scripts/pythia.py

@@ -185,6 +185,49 @@ def paint_diff_line(ln, enabled):
     return ln
 
 
+def installed_scripts_dir():
+    """The directory pip put our executable in. The default scheme is wrong
+    for `pip install --user` — the common case on Windows — so the candidate
+    that actually holds the executable wins."""
+    import sysconfig
+    candidates = [sysconfig.get_path("scripts")]
+    try:
+        candidates.append(
+            sysconfig.get_path("scripts", sysconfig.get_preferred_scheme("user")))
+    except (AttributeError, KeyError):      # very old Python: no user scheme
+        pass
+    exe = "pythia.exe" if os.name == "nt" else "pythia"
+    for d in candidates:
+        if d and (pathlib.Path(d) / exe).exists():
+            return d
+    return candidates[-1] if candidates else None
+
+
+def entry_point_hint(found, scripts_dir):
+    """What to say when `pythia` will not resolve as a command. pip installs
+    the executable into a scripts directory that is often not on PATH — the
+    default for `pip install --user` on Windows — and the shell's
+    CommandNotFound names nothing that helps. Seen on a real machine, at the
+    step immediately after the install the docs tell you to run."""
+    if found:
+        return None
+    out = ["`pythia` is installed but not on your PATH."]
+    if scripts_dir:
+        out.append("  It lives in: " + str(scripts_dir))
+        if os.name == "nt":
+            out.append("  Add it once, in PowerShell, then reopen the terminal:")
+            out.append("    [Environment]::SetEnvironmentVariable('PATH',")
+            out.append("      \"$env:PATH;" + str(scripts_dir) + "\", 'User')")
+        else:
+            out.append("  Add it to your shell profile:")
+            out.append("    export PATH=\"$PATH:" + str(scripts_dir) + "\"")
+    else:
+        out.append("  Add pip's scripts directory to PATH.")
+    out.append("Either way, this works right now, PATH or no PATH:")
+    out.append("  " + pathlib.Path(sys.executable).stem + " -m pythia <command>")
+    return "\n".join(out)
+
+
 def invocation():
     """How to invoke this tool, exactly as the user actually ran it. Every
     printed command must be paste-able: a bare `pythia ...` is
@@ -1930,6 +1973,11 @@ def cmd_install(conn, schema, ns):
             clean_legacy_skills(ns.project_root)
     print(f"\nNext: fill in {path}")
     print(f"Then: {invocation()} check")
+    hint = entry_point_hint(shutil.which("pythia"),
+                             installed_scripts_dir())
+    if hint:
+        print()
+        print(hint)
 
 
 COMMANDS = {"check": cmd_check, "ls": cmd_ls, "src": cmd_src, "args": cmd_args,

{pythia_plsql-0.4.2 → pythia_plsql-0.4.4/scripts/pythia_plsql.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythia-plsql
-Version: 0.4.2
+Version: 0.4.4
 Summary: PL/SQL development for AI agents on Oracle Database - expert data-dictionary queries, impact analysis, and a snapshot-verified write path with honest rollback.
 License: MIT
 Project-URL: Homepage, https://github.com/thaildhe172591/pythia
@@ -151,6 +151,11 @@ hand with
 works just as well.
 `pythia check` warns when the session runs with more power than the task needs.
 
+Using Claude Code? [`examples/claude-code-settings.example.json`](examples/claude-code-settings.example.json)
+stops it prompting for the read-only commands and asks it to pause on
+writes — optional, and yours to install
+([why pythia does not](GUIDE.md#11-optional-claude-code-permission-settings)).
+
 Per-group write policy, `.pythia/policy.json` (defaults shown):
 
 | Group | Default | Is rollback real? |

{pythia_plsql-0.4.2 → pythia_plsql-0.4.4}/tests/test_install.py

@@ -183,6 +183,31 @@ def test_one_version_across_every_manifest():
     assert "oracledb" in pyproject
 
 
+def test_entry_point_hint_names_the_directory_to_add():
+    """pip install --user on Windows puts pythia.exe in a Scripts directory
+    that is not on PATH, so the very next documented command fails with
+    CommandNotFound -- naming nothing that helps. Seen on a real machine."""
+    hint = pythia.entry_point_hint(found=None, scripts_dir=r"C:\Py\Scripts")
+    assert hint is not None
+    assert r"C:\Py\Scripts" in hint          # the exact directory to add
+    assert "-m pythia" in hint                # the fallback that works now
+    # once the command resolves, say nothing
+    assert pythia.entry_point_hint(found="/usr/local/bin/pythia",
+                                   scripts_dir="/usr/local/bin") is None
+    # cannot locate the directory: still offer the fallback, claim nothing else
+    hint = pythia.entry_point_hint(found=None, scripts_dir=None)
+    assert "-m pythia" in hint and "PATH" in hint
+
+
+def test_scripts_dir_prefers_where_the_executable_really_is():
+    import sysconfig
+    user = sysconfig.get_path("scripts", sysconfig.get_preferred_scheme("user"))
+    # whichever candidate holds the executable wins; with none holding it the
+    # answer is the user scheme, which is where pip --user puts it
+    assert pythia.installed_scripts_dir() in (
+        sysconfig.get_path("scripts"), user, None)
+
+
 def main():
     failed = 0
     for name, fn in sorted(globals().items()):