scrapy parse -h throws error
See original GitHub issueDescription
running scrapy parse -h
from inside of a project throws an error.
Steps to Reproduce
scrapy startproject example
cd example
scrapy parse -h
Expected behavior: It should show the help message output for the parse
command
Actual behavior: Throws error and displays traceback information
Reproduces how often: Every time I tried it.
Versions
v2.6.1
Additional context
I identified the issue and will submit a PR shortly.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Scrapy throws Attribute Error - python - Stack Overflow
1 Answer 1 · You have ROBOTSTXT_OBEY = True which tells scrapy to check for the robots.txt file of the domains it crawls,...
Read more >Frequently Asked Questions — Scrapy 2.7.1 documentation
What's the best way to parse big XML/CSV data feeds? Does Scrapy manage cookies automatically? How can I see the cookies being sent...
Read more >Scrapy Documentation - Read the Docs
Scrapy (/skrepa/) is an application framework for crawling web sites and extracting structured data which can be used.
Read more >An Introduction | Python Scrapy Tutorial - Great Learning
parse (response) – Callback method is used to get the response returns the scraped data. log(message,level,component) – Sends the log throught the “logger”....
Read more >5 Useful Tips While Working With Python Scrapy - Jerry Ng
Reduce database write using bulk insert in Scrapy item pipeline, ... Not only that, but you can also reduce the chances of getting...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Not yet. We will close it once we port the change from the 2.6 branch to the main branch.
Actually, since we merge 2.6.2 into the main branch as part of the release process, there is no reason to keep this open.