mirror of
https://github.com/probberechts/soccerdata.git
synced 2026-04-25 10:05:53 +03:00
[GH-ISSUE #93] [WhoScored] Schedule keeps scraping the same dates #20
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#20
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 @aegonwolf on GitHub (Oct 16, 2022).
Original GitHub issue: https://github.com/probberechts/soccerdata/issues/93
Hello,
Thank you for this wonderful package!
I am using python 3.10.6 and the latest version of soccerdata.
I am not sure if there is an error or a bug or if this is expected behaviour, I apologize in advance if it is.
The following code:
keeps posting
Scraping game schedule for date....for the same dates over and over, it iterates at random, i.e. the dates are not ordered Sept 30, then Oct 5, then Oct 1, then Oct 30 (which is in the future), etc.Is this expected?
There is no error.
Edit:
Might be related.
When trying to scrape a particular game, the following error occurs after also giving the same info messages (dates scraping schedules):
@probberechts commented on GitHub (Oct 17, 2022):
I've just tested it and everything seems to work fine. I have absolutely no clue why it would iterate at random over the schedule. In the expected flow, the scraper should go to the league page, click on fixtures in the menu and then cycle back from the current month to the first month of the season.
The "AttributeError" seems to suggest that there was a game without an away team in the schedule. Maybe it was a bug on the WhoScored website that was resolved by now? Could you try to run the code again?
@aegonwolf commented on GitHub (Oct 17, 2022):
Hmm, I still get the same error for the 22-23 season. It works fine for the earlier season until I get blocked (no worries I found a workaround). I was thinking it might be retrying several processes in parallel and its just the case that the IP addresses get blocked.