no module found error resolved #1061
Open
+13
−13
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
…s in the package names which resulted in no module found error
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 running the program, several "No module found" errors are displayed, even though most of the missing modules are listed in the requirements file.
This project relies on lib_resume_builder_AIHawk, which introduces various dependencies like selenium and openai. However, these dependencies conflict with some packages in Jobs_Applier_AI_Agent.
I noticed that certain packages, such as inquirer (a dependency of lib_resume_builder_AIHawk), do not get installed alongside the other packages listed in the requirements file. I had to manually install inquirer after encountering a "No module found" error.
To resolve the conflicts between the dependencies of both projects, I replaced the dashes in the package names with underscores, which fixed the issue.
I've attached an image with this PR that highlights the differences between the package lists for better clarity.