I frequently use vim -O somefile.py test_somefile.py and when using pyvim the same way I'm running into a case where when I make changes to the secondary file (right pane) and save :w, they apparently aren't actually being written, as when I go to :q it warns me that a file has changes that haven't been written.
I only discovered this because when running pytest via :!pytest the failing test was from before I made my changes, and the tests should have been passing and the traceback output showed the old code. Making these changes via vim instead has the test passing.
I frequently use
vim -O somefile.py test_somefile.pyand when usingpyvimthe same way I'm running into a case where when I make changes to the secondary file (right pane) and save:w, they apparently aren't actually being written, as when I go to:qit warns me that a file has changes that haven't been written.I only discovered this because when running pytest via
:!pytestthe failing test was from before I made my changes, and the tests should have been passing and the traceback output showed the old code. Making these changes viaviminstead has the test passing.