Executable not found on Windows about flycheck-pycheckers

[msherry]

Thanks for the detailed report! I don't have a Windows machine to test or develop on, so unfortunately it might be a while before I can build out a fix. If you have something that works and want to turn it into a pull request, I'm happy to take a look at it!

[sfavazza]

Cool, I am working on my forked repo already.
I got a working version with the hacks I mentioned in the previous post.
I will soon propose a merge request.

Actually, as python 2.7 won't be officially supported anymore by the end on this year, would you mind if I make the code compatible with python 3?

[sfavazza]

After long time I got some time to spent on this issue, yet I didn't get your answer about the python 3 migration...
Should we discuss this in another thread?

[msherry]

Sorry, I must have missed your earlier question. I'd be happy to accept a PR to make the code work correctly under python 3, but I'd want to make sure that it remains backwards-compatible for python 2.7, for people who haven't yet had the chance to migrate!

[sfavazza]

Well in that case it's already compatible, I always use python 3.

[msherry]

Going to close this issue out for lack of attention - please reopen if necessary.

[grolongo]

Hello,

I came accross that error when trying flycheck-pycheckers on Windows (same Emacs config works fine on macOS). I'm trying to use it with flake8 and bandit at the same time, both are in my path and functional from the command line (Powershell). Flake8 works without issue with Flycheck alone too. Is there any fix for this or a workaround available like OP suggested?

Thanks

[msherry]

Hi, @grolongo. Thanks for the report!

I suspect the default path for virtualenvs is not the same on Windows as it is on Linux/MacOS, but I don't have a windows machine handy to test with. Can you try debugging what path is being searched? I'm happy to accept pull requests, but I don't really have a way to debug this myself at the moment, unfortunately.

[grolongo]

@msherry hi, thanks for quick reply.

I would be happy to help but I'm very novice in Emacs/Elisp unfortunately. If you can provide me a debug command or quick guide I would gladly try to debug it and provide you the output of anything that can help fix this issue.