-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
pylint cannot handle path with spaces #445
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
Comments
Original comment by BitBucket: moxian, GitHub: @moxian?: What about using quotes?
Works fine for me. If you don't enclose the path in quotes, you are effectively passing two "files" for pylint to inspect - first being "/some/path/with/" and the second being "/space/my/project". And it's not a problem with pylint, but a common command-line behaviour. |
Original comment by Xi Shen (BitBucket: davidshen84, GitHub: @davidshen84?): Ah, I see the problem. I notice this issue when I was using Emacs. I think Do you guys also maintain the pylint Emacs tool? Or I should find someone Thx, |
Original comment by Claudiu Popa (BitBucket: PCManticore, GitHub: @PCManticore): Xi Shen, if you mean pylint.el ( https://bitbucket.org/logilab/pylint/src/989b09c516024376cd2aea29919cd4c419e0a393/elisp/pylint.el?at=default ), then yes, we are maintaining it as well. Although I don't use Emacs, nor do I know lisp. :-) If you think there's a problem with the quoting of the paths in it, could you propose a pull request or a patch? |
Original comment by Xi Shen (BitBucket: davidshen84, GitHub: @davidshen84?): Hi Claudiu, I just made a pull request, #214. Please check. If accepted, please also Thanks, |
Original comment by Claudiu Popa (BitBucket: PCManticore, GitHub: @PCManticore): Thank you! I've merged your patch. |
Originally reported by: Xi Shen (BitBucket: davidshen84, GitHub: @davidshen84?)
My project on my system locates at
If I ran
I got ImportError.
But if I ran
It works well.
The text was updated successfully, but these errors were encountered: