Getting Started

Beginner guide to pyIDE status, files, projects, interpreters, running, output, external consoles, autosave, and next steps.

v2.0 In Development Legacy Python Release

Status

pyIDE v2.0: Public v2.0 download is not available yet.

Legacy Python Release: Legacy Python Release

What pyIDE is

pyIDE is a lightweight Windows-focused IDE from sonicFanTech. The downloadable legacy release was built with Python and PySide6. The future pyIDE v2.0 is a C++ recode in development.

  • Legacy Python release is the current downloadable version.
  • pyIDE v2.0 public download is not available yet.
  • The AI Desktop Assistant belongs to the v2.0 development direction.
Download the legacy release

Use the Downloads page to get the selected legacy installer for your chosen website language. The selector changes the GitHub release filename where a localized installer exists.

  • Do not look for a v2.0 installer yet.
  • Run the legacy setup from the GitHub release link.
Create a new file

Create a new untitled editor tab, write Python code, then save it with a .py filename before relying on autosave.

  • Ctrl+N creates a new file.
  • Untitled files need a Save or Save As location.
Open and save files

Open existing Python files, edit them in tabs, and save changes when the unsaved indicator appears.

  • Ctrl+O opens a file.
  • Ctrl+S saves the current file.
  • Ctrl+Shift+S saves with a new name.
Open a project folder

A project folder becomes the active project for file browsing, search, and AI tool boundaries.

  • Open the folder that contains your script files.
  • Use the project tree to open, create, rename, or delete files.
Select an interpreter

Choose the Python executable pyIDE should use when running scripts. Verify the selected python.exe exists.

  • Multiple Python versions can exist on one machine.
  • If running fails, check the interpreter path first.
Run a script internally

F5 runs the current script inside pyIDE and sends output to the output panel.

  • Save the file before running.
  • Check visible error output when execution fails.
Read the output panel

The output panel shows normal print output, error text, and prompts where stdin is supported.

  • A script that waits for input may need stdin support.
  • Terminal-style programs may behave better externally.
Run in an external terminal

Ctrl+F5 launches the script in an external console such as Command Prompt, Windows PowerShell, PowerShell 7, Windows Terminal, or a configured custom terminal.

  • Use external mode for interactive CLI and curses-style tools.
  • Check custom terminal paths if launch fails.
Autosave

Autosave protects named files at the configured interval. Untitled files still need a save location.

  • Set the autosave interval in Settings.
  • Autosave does not replace intentional Save As workflow.
Next steps

After the beginner walkthrough, continue into the editor, project manager, running scripts, settings, and troubleshooting guides.

  • Read the editor guide.
  • Read the project manager guide.
  • Read the running scripts guide.