mirror of
https://github.com/probberechts/soccerdata.git
synced 2026-04-25 10:05:53 +03:00
[GH-ISSUE #581] [WhoScored] Broken read_schedule() method #104
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#104
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 @probberechts on GitHub (May 14, 2024).
Original GitHub issue: https://github.com/probberechts/soccerdata/issues/581
Originally assigned to: @probberechts on GitHub.
WhoScored has updated the HTML structure of their fixture pages. The scraper must be updated accordingly.
@ds-oliver commented on GitHub (May 20, 2024):
Hey - are we getting WS scraper back up?
@probberechts commented on GitHub (May 20, 2024):
I am working on it. You can already use the version in the
fix/whoscored-schedulebranch. I need to do a bit more testing before releasing it.@ds-oliver commented on GitHub (May 20, 2024):
I'll check that out. Cheers.
@ds-oliver commented on GitHub (May 23, 2024):
I tried to follow your advice with this and have encountered an issue while trying to check out and install the
fix/whoscored-schedulebranch. Here are the steps I followed and the errors I encountered:Cloned the repository:
Checked out the specific branch:
Created and activated a virtual environment:
Upgraded pip, setuptools, and wheel:
Attempted to install the package in editable mode:
Despite these steps, I received the following error:
I also tried creating a
pyproject.tomlfile with the following content, but the issue persisted:Additionally, I attempted to bypass the isolated build environment:
However, the error still persists. Could you please provide guidance on how to resolve this issue? Is there a known problem with the
setup.pyor any dependencies in this branch that I should be aware of?@probberechts commented on GitHub (May 24, 2024):
Simply running the following works for me:
You could also try to install it using poetry.