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

ModuleNotFoundError: No module named 'cazy_webscraper.cazy_webscraper‘ #69

Closed
NaiveLittleTiger opened this issue Jan 12, 2022 · 1 comment · Fixed by #70 or #71
Closed

ModuleNotFoundError: No module named 'cazy_webscraper.cazy_webscraper‘ #69

NaiveLittleTiger opened this issue Jan 12, 2022 · 1 comment · Fixed by #70 or #71
Assignees
Labels
bug Something isn't working

Comments

@NaiveLittleTiger
Copy link

Describe the bug

I finished installing cazy-webscraper package using 'pip install cazy-webscraper', when I try to use it then get the following error,"ModuleNotFoundError: No module named 'cazy_webscraper.cazy_webscraper‘ ", Then I try to install from source code, I also get same error. I don't know the reason. Can anyone assist me? thanks!
image

@HobnobMancer HobnobMancer self-assigned this Jan 12, 2022
@HobnobMancer HobnobMancer added the bug Something isn't working label Jan 12, 2022
This was linked to pull requests Jan 12, 2022
@HobnobMancer
Copy link
Owner

Thanks for the bug report, they are extremely useful (especially while cazy_webscraper is still in beta).

The issues was the result of line 77 in the setup.py not having been updated to match the new program architecture.
The line has been updated to point to the correct file name for the main entry point (it now points to cazy_scraper instead of cazy_webscraper).

This should now be fixed in the new pypi release (v2.0.2).

In future, it is good practice to fill out the bug report form in full. This facilitates the reproducibility of what caused the issue to be raised, which in turn makes finding the possible cause of the issue far easier and significantly faster. Luckily, in this case I was able to reproduce the issue; however, with the information provided arguably your work is not reproducible. The screen capture of your terminal isn't displaying the standard output for a Linux system. If you were not using a POSIX os then that could have been a cause of the problem. Additionally, with no information provided about the virtual environment you are using, the issue could have been caused by import and/or version conflicts. Without that information up front we can't rule out or rule in a lot of possibilities without a lot of backwards and forwards via comments and often a lot of extra work and playing around our end, especially if we aren't able to reproduce the issue. Long story short, provide all the info necessary for reproducing your work, which makes likes life easier for everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants