-
Notifications
You must be signed in to change notification settings - Fork 558
New issue
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
LeagueGameFinder returns an empty data array #95
Comments
What are you passing to start and end? I just ran what you sent here without start and from nba_api.stats.library.parameters import *
from nba_api.stats.endpoints import *
raw_game_data = leaguegamefinder.LeagueGameFinder(league_id_nullable=LeagueIDNullable().nba, season_type_nullable=SeasonType().regular) |
Hi @swar, I'm just passing in strings formatted like so: "m/d/yyyy" Example: After some initial trial and error it seemed that this was the date format that |
Could the issue be that there were no regular season games played 2019-10-06 and 2019-10-07? I get results when I switch |
Also if this is still an issue, if you switch back to |
Feel free to reopen if you're still having this issue. |
Hi swar, thanks so much for creating this api! I am loving it.
So prior to the changes that occurred on stats.nba.com that forced your recent header changes (see: #94), I was using the LeagueGameFinder to pull down various bits of game data. When that change occurred I got the connection issue reported above.
After adding headers, I no longer get the connection issue, but the object returned from
LeagueGameFinder
doesn’t return any meaningful results (theleague_game_finder_results.data
array always comes up empty, regardless of the query/params). Any idea what might be causing this?Sample
LeagueGameFinder
api call from my application (just in case I'm doing something terribly wrong):raw_game_data = leaguegamefinder.LeagueGameFinder(date_from_nullable=start, date_to_nullable=end, league_id_nullable=LeagueIDNullable().nba, season_type_nullable=SeasonType().regular)
The text was updated successfully, but these errors were encountered: