Skip to content

Add a FAQ entry about name collisions #3669

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

Merged
merged 5 commits into from
Aug 17, 2021

Conversation

Gallaecio
Copy link
Member

@Gallaecio Gallaecio commented Mar 8, 2019

Fixes #2680

@codecov
Copy link

codecov bot commented Mar 8, 2019

Codecov Report

Merging #3669 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3669   +/-   ##
=======================================
  Coverage   84.80%   84.80%           
=======================================
  Files         163      163           
  Lines        9987     9987           
  Branches     1487     1487           
=======================================
  Hits         8469     8469           
  Misses       1254     1254           
  Partials      264      264           

@Gallaecio Gallaecio changed the title Add a FAQ entry about name collisions [WIP] Add a FAQ entry about name collisions Mar 15, 2019
@Gallaecio Gallaecio force-pushed the spider-name-collision branch from 31ab5ff to 72cf190 Compare March 22, 2019 14:37
@Gallaecio
Copy link
Member Author

I’ve modified the entry to cover (and only cover) the scenarios where users are using a Scrapy project.

@Gallaecio Gallaecio changed the title [WIP] Add a FAQ entry about name collisions Add a FAQ entry about name collisions Dec 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

name collision of spider with existing module
3 participants