Setting up a Python Development Environment in Sublime Text

Setting up a Python workflow in Sublime Text hinges on three layers: installing Package Control, applying editor-wide preferences (themes, fonts, and behavior), and adding a Python-focused package that brings linting and auto-formatting. Once those pieces are in place, Sublime Text can run Python code and provide “IDE-like” feedback—catching common syntax and naming mistakes as code is edited.

The process starts with installing Sublime Text 3 from the official download page. The license model is evaluation-first: Sublime Text can be downloaded and used indefinitely for testing, with periodic purchase prompts if it isn’t licensed. After installation on macOS (dragging the app into Applications), a sample Python module is used to confirm basic execution. Sublime Text’s default “automatic” build system can run the current file via Tools → Build (Command+B on macOS), producing output from the script and demonstrating that a fresh install already supports running Python.

From there, the setup becomes more customized. Package Control is installed through the Command Palette (Tools → Command Palette, or Command+Shift+P on macOS). With Package Control available, additional packages are installed to improve the editing experience. For visual styling, the workflow installs Predon as a color scheme and Material Theme as the interface theme, then pulls recommended and personal settings from a GitHub-hosted configuration into Sublime Text’s user settings. The settings update changes the entire editor appearance, and the author restarts Sublime Text to ensure the changes fully apply. Key preferences include selecting Source Code Pro as the font (from Google Fonts), enabling scroll past the end, converting tabs to spaces for consistency, and suppressing some on-screen popups (like definitions/errors) to reduce interruptions.

Next comes functionality. Several quality-of-life packages are added: Bracket Highlighter to visually match opening and closing braces across lines, and Sidebar Enhancements to expand sidebar actions such as searching and opening files. The Python-specific upgrade is the Anaconda package for Sublime Text (distinct from the Anaconda Python distribution by Continuum Analytics). Its configuration turns on auto-formatting to keep code PEP 8 compliant when possible, with ignore lists for specific PEP 8 checks (including E501 for line length). Linting and error markers appear in the gutter; the author demonstrates missing colons and incorrect variable names producing “invalid syntax” and “undefined name” warnings that disappear once the code is corrected.

Finally, the workflow addresses running different Python versions. Sublime Text’s build systems can be duplicated and customized so projects use Python 2.7 or Python 3.5 instead of the default interpreter. The author creates new build system files (saving them with the Sublime Build extension) and shows that selecting the Python 3.5 build system runs the script using a user-local Python 3.5 path. If packages ever need to be removed, the Command Palette supports “Remove Package.” The result is a reproducible editor environment that supports theming, formatting, linting, and version-specific execution—without forcing users into a full IDE replacement.