We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am not using an nflverse R package (nflreadr, nflfastR) to access this data.
0.3.3
import_qbr doesn't return any data for the 2024 (current) season.
import_qbr
import nfl_data_py as nfl qbr = nfl.import_qbr([2024], 'nfl', 'weekly') qbr.head() The above returns an empty dataframe
I expected a dataframe similar to what the following would return, but for the current season:
import nfl_data_py as nfl qbr = nfl.import_qbr([2023], 'nfl', 'weekly') qbr.head()
NA
No response
The text was updated successfully, but these errors were encountered:
The data source for this method is outdated, it should point to the espn_data feed.
@mawi510 here's a workaround until I can get that fixed.
import pandas as pd url = "https://github.com/nflverse/nflverse-data/releases/download/espn_data/qbr_week_level.parquet" qbr = pd.read_parquet(url).loc[lambda x: x.season == 2024].reset_index(drop=True)
Sorry, something went wrong.
@alecglen No worries, really appreciate the workaround!
No branches or pull requests
Is there an existing issue for this?
Have you installed the latest development version of the package(s) in question?
If this is a data issue, have you tried clearing your nflverse cache?
I am not using an nflverse R package (nflreadr, nflfastR) to access this data.
What version of the package do you have?
0.3.3
Describe the bug
import_qbr
doesn't return any data for the 2024 (current) season.Reprex
Expected Behavior
I expected a dataframe similar to what the following would return, but for the current season:
nflverse_sitrep
NA
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: