Find Your Feature Fit: How to Pick a Text Editor for Python Programming
summary
Direct comparison of VS Code and Vim with real work on the GatorGrader codebase shows how features behave: VS Code gives ctrl‑shift‑P command palette and ctrl‑P fuzzy search out of the box, Vim requires plugin hunting; both run black formatting and flake8 linting, both run pytest and coverage. The demo installs and runs a project with 71 dependencies, finds a hard‑coded path that drops coverage to 98–99%, fixes the test using pytest temporary fixtures and string conversion, and restores 100% coverage.
AI-written summary · about
chapters (22)
- 0:00Start
- 6:56Enable Black Code Formatting
- 7:26Enable Tab Completion
- 7:44Enable Flake8 Code Linting
- 9:19Overview of Vim's Configuration File
- 11:01Configuration and Plugins
- 12:53Install Application Dependencies
- 13:31Selecting a Virtual Environment
- 13:59Start Project in a Virtual Environment
- 14:21Virtual Environments and Package Installation
- 15:28Terminal command: pipenv run cover
- 16:26Fuzzy File Finding for the Test
- 17:57Use Pytest's tmpdir fixture
- 18:23View and Act on Flake8 Warning
- 18:52Automated Code Linting
- 19:40Code Autocompletion
- 20:13Source Code Formatting
- 21:17Python Test Explorer
- 21:50Convert tmpdir to a String
- 22:24Check Test Suite Coverage
- 23:08Automated Testing
- 24:42Snippet Expansion
related talks
48mVisual Studio Code can do that?
12mVim in the Modern Era: Leveraging a Small Editor for Big Results
59mUnleash the Power of Visual Studio Code
38mThe Battle of the IDEs (Pokemons)
52mHow Visual Studio Code Helps You Develop More Efficiently in C++
19mIDE-ntity Crisis: Choosing the Right Tool for Me
34mOpen Source Entertainment: Vim for fast and sustainable coding!
56mUsing Visual Studio Code Features to Speed Up Your Code