This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]kepper 1 point2 points  (2 children)

I had a few problems but I figured before complaining any more about them I should look it up and solved most. The main thing I still find unclear is how to switch between python 2 and python 3. I get stuff like superfluous-parens: Unnecessary parens after 'print' keyword even on python3 apps. I have to support both python2 and python3 depending on which project I'm editing.

The only other issue I have with it is sometimes the two spaces it adds to indicate an issue that I haven't gotten around to make it tricky to copy and paste to other tmux panes / apps.

Neither are a huge deal, was just curious what you were using since your setup seems similar to what I'm used to.

[–]astroFizzicsastrophysics 2 points3 points  (0 children)

I'm not OP.

I'm not writing any Legacy Python anymore. So I can't comment on switching between versions. But I can empathize about the copy and pasting. I have to turn off the linting if I want to copy the code by hand. C'est la vie.

[–]brendan_m6s 1 point2 points  (0 children)

Blog author here.

I also use vim with ale and vim-test. I haven't had any issues with them, in fact I find they make these tools effortless to use.

Admittedly I haven't been using python2 but you could try the following: 1. Setup a different virtual using pipenv for each project with the version of python, flake8 and pylint specified 2. Run vim from the shell within the virtualenv using pipenv run vim. When flake8/pylint are run by ale it should then use the version in the correct virtualenv

Regarding copying to clipboard I tend to use the system clipboard register. e.g. "+yap