-
Notifications
You must be signed in to change notification settings - Fork 117
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
Check availability of lxml #6
Comments
I think it's just been a bad design decision. |
Yes. Using requirements.txt is a good option and if "Please install x module" is used then there should be same mechanism for all components. General stacktrace when module is missing is pretty obvious too.. I can create a pull request for requirements.txt change. |
Using requirements.txt is a good way for this I would say. @gbrindisi Are you still actively maintaining this project? |
I am not actively developing, but I can review and merge pull requests 👍 |
@gbrindisi Thanks for your quick answer, packaging/releasing/publishing it for pip (#2) would be the next best thing to increase usage and pull requests. |
@tholu I will put this in my backlog |
Yes, I successfully get the output of the project Thank you. |
Currently if mechanize is missing xsssniper will say:
But if lxml is missing it will say:
Maybe xsssniper should also give pip install -commands rather than per project URLs, but that is design decision. Also the import errors are checked several times. Is there a reason for that?
The text was updated successfully, but these errors were encountered: