Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] 1.7.1 not support 1.6.0 script #3893

Kenith opened this issue Jul 22, 2019 · 2 comments · Fixed by #3896

[Bug] 1.7.1 not support 1.6.0 script #3893

Kenith opened this issue Jul 22, 2019 · 2 comments · Fixed by #3896


Copy link

@Kenith Kenith commented Jul 22, 2019

Hello All,

My spider is created by scrapy 1.6.0.
These days, the scrapy updated to 1.7.1, and we found that it cannot support the code build by 1.6.0.

Here is the error:

Traceback (most recent call last):
  File "/usr/bin/scrapy", line 6, in <module>
    from scrapy.cmdline import execute
  File "/usr/lib64/python2.7/site-packages/scrapy/", line 10, in <module>
    from scrapy.crawler import CrawlerProcess
  File "/usr/lib64/python2.7/site-packages/scrapy/", line 11, in <module>
    from scrapy.core.engine import ExecutionEngine
  File "/usr/lib64/python2.7/site-packages/scrapy/core/", line 14, in <module>
    from scrapy.core.scraper import Scraper
  File "/usr/lib64/python2.7/site-packages/scrapy/core/", line 18, in <module>
    from scrapy.core.spidermw import SpiderMiddlewareManager
  File "/usr/lib64/python2.7/site-packages/scrapy/core/", line 13, in <module>
    from scrapy.utils.conf import build_component_list
  File "/usr/lib64/python2.7/site-packages/scrapy/utils/", line 4, in <module>
    import configparser
ImportError: No module named configparser

Would you please take time to check the issue?

Appreciate for your help in advance.

Thank you.

@Kenith Kenith changed the title [Bug] 1.7.0 not support 1.6.0 script [Bug] 1.7.1 not support 1.6.0 script Jul 22, 2019
Copy link

@elacuesta elacuesta commented Jul 22, 2019

Hello @Kenith, this has been reported already at #3889
As I commented there, if you can install additional dependencies you can work around the issue by installing the backported version (
If you don't mind, please consider closing this issue as it is a a duplicate of #3889. Thanks!

Copy link

@Kenith Kenith commented Jul 23, 2019

Hello @elacuesta , really appreciate for your time and effort.
I closed the issue. Thank you.

@Kenith Kenith closed this as completed Jul 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging a pull request may close this issue.

2 participants