FIX: Allow Indeed search term with complex syntax #139
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
good catch |
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When scraping using Indeed, simple syntax must be used. Otherwise, for example using
search_term='"Python" AND "Java"'it logs the following message:JobSpy - INFO - Indeed responded with status code: 400 (submit GitHub issue if this appears to be a beg)The suggested fix, it escapes the quote in order to be able to be processed. I've compared the results between the scrape and the job platform result with the same syntax and, sorted by date, it returns the same results.
Besides, with this change now it also can be used any expression included in the Indeed syntax search guide