yapfify
yapfify copied to clipboard
Support for setup.cfg as style definition
I was wondering if this also works with style definitions that are in [yapf] section in a setup.cfg in the directory or one of the parent directories (see https://github.com/google/yapf)? It didn't seem to work for me.
Also would this also work with emacs tramp (ie when opening a file through ssh and the folder or the parents contain a style file in the project)?
I'm not sure about setup.cfg
Yapf is running locally even for tramp buffers, so formatting will be done according to the global yapf style. No style search on the remote host will be done.
I add tramp support for very similar package isortify.
I want to give this feature some time to stabilize. If it will not cause any troubles, I'll backport it to this package.
@proofit404 is there any way to run a yapf formatter that exists within a docker container on a local file?
I add tramp support for very similar package isortify.
I want to give this feature some time to stabilize. If it will not cause any troubles, I'll backport it to this package.
Note: is this still actual? I would love to have yapf using the setup.cfg when using tramp, since it is actually part of my workflow. I can of course do it manually, but still would be great to have the automation here.
I add tramp support for very similar package isortify. I want to give this feature some time to stabilize. If it will not cause any troubles, I'll backport it to this package.
Note: is this still actual? I would love to have yapf using the setup.cfg when using tramp, since it is actually part of my workflow. I can of course do it manually, but still would be great to have the automation here.
@proofit404 I don't think isortify does this currently?
@JorisE @Dav1d23 Hi guys,
isortify package does a similar feature in this way:
- You install isort on the remote host.
- You have setup.cfg on the remote host.
- You activate the remote virtual environment using
pythonic-activate.
It works well for me with vagrant and docker.
But this approach forces us to run isort as a python module using pythonic-call function. And we lose an ability to deal with executables on the local machine until you activate the virtual environment manually.