mirror of
https://github.com/probberechts/soccerdata.git
synced 2026-04-25 10:05:53 +03:00
[GH-ISSUE #629] [FBref] Available leagues in docs do not match current FBref available leagues #123
Labels
No labels
ESPN
FBref
FotMob
MatchHistory
SoFIFA
Sofascore
WhoScored
WhoScored
bug
build
common
dependencies
discussion
documentation
duplicate
enhancement
good first issue
invalid
performance
pull-request
question
question
removal
understat
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/soccerdata#123
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ethanfinkel on GitHub (Jul 5, 2024).
Original GitHub issue: https://github.com/probberechts/soccerdata/issues/629
Hey team,
I found this issue in the docs as I was getting set up and thought I'd flag it. Awesome package by the way!
The docs have instructions for pulling EPL data from FBref, but the EPL is not a valid league for FBref currently. This leads to an error when following the docs verbatim.
Docs
Value error from following docs
Currently available leagues
Fix
I think a simple updates to the docs is what's needed here unless the available leagues should include the leagues that are currently not available. I'm new to the repo but thought I'd file the issue as I go through. Happy to put up a PR updating the docs.
@probberechts commented on GitHub (Jul 5, 2024):
Hey,
This seems to work fine on my end.
Did you perhaps edit the
league_dict.jsonconfig file?@ethanfinkel commented on GitHub (Jul 5, 2024):
Hey @probberechts thanks for the prompt reply.
I didn't edit any config files. Running off a fresh install. Looks like I'm on the same version you are.
@probberechts commented on GitHub (Jul 6, 2024):
I'm closing this since there is absolutely no way in which I can reproduce it. All tests are passing. But let me know if you would be able to figure out what's causing the issue.
@babu-akhil commented on GitHub (Feb 9, 2025):
Facing the same issue.
gives the output
Issue only occurs when I'm working inside a venv. Outside venv It is working correctly!
@babu-akhil commented on GitHub (Feb 9, 2025):
Its working now after I restart kernel. No code change in package. Very Strange!