pirl-unc / hitlist / 33544963348
83%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 30
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 81.118%. Remained the same
33544963348

push

github

web-flow 
v1.55.1: develop.sh installs into the active virtualenv, and says where it landed (#400)

The script created and activated ./.venv unconditionally. Run from a shell that
already had a virtualenv active -- which is the normal case here, since the
sibling repos are all installed editable into a shared env -- it therefore
installed into a *different* environment than the one in use, and reported
success.

That failure is silent by construction: the install genuinely works, it is just
somewhere else. On this machine it let a 1.45.0 site-packages tree survive
behind a 1.55.0 checkout across several releases, with `pip list` showing 1.45.0
and `hitlist --version` running 1.45.0 code while `python -c "import hitlist"`
from inside the repo reported 1.55.0 (cwd on sys.path, not the install). The
first symptom was a build crashing on a data file that had shipped two releases
earlier.

Two changes:

Honour VIRTUAL_ENV when it is set, and only fall back to creating .venv when
no environment is active.

Print the resolved import path and what the console script on PATH actually
reports, and warn when they disagree. An exit code cannot express this failure
-- the install succeeded -- so the only useful confirmation is the path, which
is exactly what was missing.

Verified both branches: with VIRTUAL_ENV set it installs into the active env
and reports agreeing versions; with it unset it still creates .venv.

Claude-Session: https://claude.ai/code/session_014cBpazLoFvftLSLavT7T9X

6139 of 7568 relevant lines covered (81.12%)

0.81 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33544963348.1 30
81.12
 GitHub Action Run
Source Files on build 33544963348