Skip to content

Clear the Dependabot alerts: drop eppy, require Python 3.11 - #35

Merged
btokarzewskidb merged 1 commit into
mainfrom
chore/security-alerts
Nov 17, 2026
Merged

btokarzewskidb merged 1 commit into
mainfrom
chore/security-alerts

Conversation

@btokarzewskidb

Copy link
Copy Markdown
Contributor

Clears all 84 open Dependabot alerts. All of them were in dev tooling; the package has no runtime dependencies and is unchanged.

What changed

  • Removed eppy from the dev group. Only scripts/run_resource_models.py used it, to wrap each IDF and run it with runIDFs. It pulled in the Sphinx / nbsphinx / Jupyter toolchain behind most alerts: bleach, mistune, nbconvert, tornado, soupsieve, requests, urllib3, certifi, idna, lxml. No test imports it; the tests read the committed files in tests/test_files/.
  • Rewrote scripts/run_resource_models.py to call each EnergyPlus installation's energyplus executable directly (--weather, --output-directory, --output-prefix), one process per CPU. It adds --expandobjects when an IDF uses HVACTemplate: objects, and exits non-zero if a simulation fails. Each installation reads its own Energy+.idd, so the per-version IDD reset is gone. Output naming and the copy to tests/test_files/ are unchanged.
  • Python 3.11+: the patched filelock, pylint, pytest and pyarrow need Python 3.10 or 3.11, so the lock kept vulnerable versions for 3.9 and 3.10. Both are end of life. requires-python = ">=3.11", ruff target-version = "py311", and the CI matrix is now 3.11 to 3.14. The README badge is updated too.
  • uv lock upgraded the rest: certifi, filelock, idna, lxml, pyarrow, pygments, pylint, pytest, virtualenv. The lock goes from 113 to 28 packages.

What I ran

  • Checked each of the 84 alerts' vulnerable range against every version in the new uv.lock: none match. Against the old lock, all 84 matched.
  • uv run ruff check ., uv run ruff format --check ., and uv run pylint db_eplusout_reader (10.00/10). pylint scripts/run_resource_models.py also scores 10.00/10.
  • uv run pytest tests -q on Python 3.14: 226 passed.
  • Ran the new runner on resources/252_1ZoneUncontrolled.idf, with its Version changed to 26.2 (the only EnergyPlus installed here), in a scratch folder. EnergyPlus 26.2 ran it in 1.8 s and the .eso was copied, and DBEsoFileCollection.from_path reads it (3 environments).

What I did not run

  • The tests on 3.11 to 3.13; CI runs those.
  • The runner on the 23.1, 25.1 and 25.2 IDFs in resources/, because those EnergyPlus versions aren't installed here.
6 files changed, 266 insertions(+), 2443 deletions(-)

🤖 Generated with Claude Code

All 84 open alerts were in dev tooling; the package itself has no runtime
dependencies.

- eppy was only used by scripts/run_resource_models.py, to wrap IDFs and
  run them with runIDFs, and it pulled in the Sphinx, nbsphinx and Jupyter
  toolchain behind most alerts (bleach, mistune, nbconvert, tornado,
  soupsieve, requests, urllib3, certifi, idna, lxml). The script now calls
  each installation's energyplus executable directly, in parallel, with
  -x added when an IDF uses HVACTemplate objects. Each version reads its
  own Energy+.idd, so the per-version IDD reset is gone.
- The patched filelock, pylint, pytest and pyarrow need Python 3.10 or
  3.11, so the lock kept vulnerable versions for 3.9 and 3.10. 3.9 and
  3.10 are end of life; requires-python is now >=3.11, ruff targets
  py311, and CI tests 3.11-3.14.
- uv lock upgraded the remaining alerted packages (certifi, filelock,
  idna, lxml, pyarrow, pygments, pylint, pytest, virtualenv).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@btokarzewskidb
btokarzewskidb merged commit 7b9fa06 into main Nov 17, 2026
5 checks passed
@btokarzewskidb
btokarzewskidb deleted the chore/security-alerts branch November 17, 2026 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant