blamcode 0.4.0__tar.gz → 0.4.2__tar.gz

{blamcode-0.4.0 → blamcode-0.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: blamcode
-Version: 0.4.0
+Version: 0.4.2
 Summary: BLAMCODE — AI coding CLI for Termux. Your app, BLAM, done!
 Author: zyvo9
 License: MIT

{blamcode-0.4.0 → blamcode-0.4.2}/blamcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: blamcode
-Version: 0.4.0
+Version: 0.4.2
 Summary: BLAMCODE — AI coding CLI for Termux. Your app, BLAM, done!
 Author: zyvo9
 License: MIT

blamcode-0.4.2/blamcode.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+blamcode = blamcode.cli:main

{blamcode-0.4.0 → blamcode-0.4.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "blamcode"
-version = "0.4.0"
+version = "0.4.2"
 description = "BLAMCODE — AI coding CLI for Termux. Your app, BLAM, done!"
 readme = "README.md"
 requires-python = ">=3.8"
@@ -23,7 +23,7 @@ classifiers = [
 dependencies = []
 
 [project.scripts]
-blamcode-boot = "blamcode.cli:main"
+blamcode = "blamcode.cli:main"
 
 [tool.setuptools]
 packages = ["blamcode"]

{blamcode-0.4.0 → blamcode-0.4.2}/python/blamcode/__init__.py

@@ -6,4 +6,4 @@ hands over to the real installer (install.sh) which does everything
 else (core engine, deps, single-line live progress).
 """
 
-__version__ = "0.3.1"
+__version__ = "0.4.2"

{blamcode-0.4.0 → blamcode-0.4.2}/python/blamcode/cli.py

@@ -1,12 +1,12 @@
 """blamcode — command-line bootstrap for installing BLAMCODE from PyPI.
 
-`pip install blamcode` gives you the `blamcode-boot` command (the name is
-deliberately NOT `blamcode`: on Termux pip writes scripts to $PREFIX/bin,
-where the real installer also puts its `blamcode` wrapper — an alias would
-collide with it). Running it installs the BLAMCODE layer (scripts + config +
-skills + installer) from the wheel's own bundled copy — no network fetch
-for the layer — then hands over to the real installer, which downloads
-the core engine with a single live progress line.
+`pip install blamcode` gives you the `blamcode` command. Running it
+installs the BLAMCODE layer (scripts + config + skills + installer) from
+the wheel's own bundled copy — no network fetch for the layer — then hands
+over to the real installer, which downloads the core engine with a single
+live progress line. On Termux the installer later replaces the bootstrap
+with the full `blamcode` wrapper at the same path, so the name never
+changes for the user.
 
 Design: the pip package bundles the layer and acts as the launcher;
 all real logic lives in install.sh, so curl-install and pip-install
@@ -42,7 +42,7 @@ def _jump_to_installer(boot):
     if not os.path.isfile(installer):
         sys.exit(
             "error: boot layer is incomplete (missing install.sh);\n"
-            "       rerun:  blamcode-boot install"
+            "       rerun:  blamcode install"
         )
     if not os.access(installer, os.X_OK):
         os.chmod(installer, 0o755)

blamcode-0.4.0/blamcode.egg-info/entry_points.txt

@@ -1,2 +0,0 @@
-[console_scripts]
-blamcode-boot = blamcode.cli:main