Skip to content

Commit

Permalink
Update the llnl-scraper version constraint in the Pipfile
Browse files Browse the repository at this point in the history
We need some changes that were added in the LLNL/scraper repo but do
not yet have a PyPI release. Rather than continue to use a fork in our
GitHub organization it makes sense to pull in LLNL/scraper at a
specific commit until a new version is release to PyPI.
  • Loading branch information
mcdonnnj committed Aug 28, 2024
1 parent 36a533c commit 73a003a
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 4 deletions.
8 changes: 6 additions & 2 deletions src/Pipfile
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,12 @@ name = "pypi"
# Minimum version for IMDSv2 support
boto3 = ">=1.13.23"
docopt = ">=0.6.2"
# Use our fork for required functionality that is not in LLNL/scraper yet.
llnl-scraper = {file = "https://github.com/cisagov/scraper/archive/v0.14.0-dev.tar.gz"}
# We need a bugfix for behavior in newer versions of cloc. Since there is not a
# release on PyPI with the code in https://github.com/LLNL/scraper/pull/79, we
# must instead pull directly from the GitHub repository. We use the latest (as
# of this comment) commit on the default branch to serve as our version pin
# equivalent.
llnl-scraper = {file = "https://api.github.com/repos/LLNL/scraper/tarball/536a72ce1ceb2e209281ff72a2ed59e735d45c33"}

[requires]
python_full_version = "3.12.3"
4 changes: 2 additions & 2 deletions src/Pipfile.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit 73a003a

Please sign in to comment.