nflverse / nflverse/nflreadpy

[BUG] 2025 injuries are missing

Open
#17 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
217
Forks
33
Avg merge
1d 2h
Merged PRs (30d)
2

Description

Is there an existing issue for this?
  • I have searched the existing issues
Have you installed the latest development version of the package(s) in question?
  • I have installed the latest development version of the package.
If this is a data issue, have you tried clearing your nflverse cache?

I have cleared my nflverse cache and the issue persists.

What version of the package do you have?

0.1.3

Describe the bug

Injuries for 2025 are missing. I saw you already have an issue to check the missing parquets, but it does not include injuries:
Check where nflverse-data is missing .parquet files

Reprex
injuries = nfl.load_injuries([2025])

#Here is the error:
#ConnectionError: Failed to download https://github.com/nflverse/nflverse-#data/releases/download/injuries/injuries_2025.parquet: 404 Client Error: Not Found for url: #https://github.com/nflverse/nflverse-data/releases/download/injuries/injuries_2025.parquet
Expected Behavior

I would expect to the get the data for injuries in 2025 same as I get for other years.

Screenshots

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the nfl.load_injuries([2025]) reproduction and inspect the related missing-parquets issue (#15). Check why the injuries_2025.parquet release URL returns 404 and determine whether the missing data belongs in nflreadpy or the linked nflverse-data release. Done means loading 2025 injuries succeeds like other years.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.