Introduction

TurboPy is a free (as in “free speech” and also as in “free beer”) Integrated Development Environment for Python, built to simplify coding, testing, and managing Python projects in one place. Running in the Microsoft Windows environment, its use is governed by GNU General Public License v3.0. TurboPy is written in C++ and uses pure Win32 API and STL which ensures a higher execution speed and smaller program size. By optimizing as many routines as possible without losing user friendliness, TurboPy is trying to reduce the world carbon dioxide emissions. When using less CPU power, the PC can throttle down and reduce power consumption, resulting in a greener environment. I hope you enjoy TurboPy as much as I enjoy coding it!

Getting started

Install TurboPy using the installer

  • Download the installer
  • Run the executable binary and follow the installation flow

The installer will likely require Administrative privileges in order to install TurboPy (and later, to update TurboPy or install or update plugins, or anything else that requires writing to the installation directory). If you do not have Administrative privileges, you either need to tell the installer to use a location where you do have write permission (though that may still ask for Administrator privileges), or you may choose not use the installer and instead run a portable edition from a directory where you have write permission.

Install TurboPy from zip

These instructions will allow you to run a portable or mini-portable (also called “minimalist”), without requiring administrative privileges.

  • Create a new folder somewhere that you have write-permission
  • Unzip the content into the new folder
  • Run TurboPy from the new folder

The portable zip edition of TurboPy can be removed by deleting the directory they came in. If you manually set up file associations or context-menu entries in the OS, it is your responsibility to remove them yourself.

Create and Submit your Pull Request

As noted in the Contributing Rules for TurboPy, all Pull Requests need to be attached to a issue on GitHub. So the first step is to create an issue which requests that the functionality be improved (if it was already there) or added (if it was not yet there); in your issue, be sure to explain that you have the functionality definition ready, and will be submitting a Pull Request. The second step is to use the GitHub interface to create the Pull Request from your fork into the main repository. The final step is to wait for and respond to feedback from the developers as needed, until such time as your PR is accepted or rejected.

Software Content Register

Release Name: TurboPy
Description: TurboPy is an Integrated Development Environment for Python, built to simplify coding, testing, and managing Python projects in one place.
Outgoing License: GNU General Public License v3.0
Type of content: static/dynamic libraries, source code, binary

cpython
Desciption: The Python programming language.
Version: 3.16
Home Page: https://github.com/python/cpython
License: Python Software Foundation License Version 2
Format: source code, binary

genUp4win
Desciption: Generic Updater for Windows written in C++, with no external dependency.
Version: 3.03
Home Page: https://github.com/mihaimoga/genUp4win
License: MIT
Format: source code, binary

CHLinkCtrl
Description: This class allows you to create a static control on a window or dialog which behaves similar to a hyperlink as seen on a web page. When the mouse moves over the text the cursor becomes a hand and when you click on the text the hyperlink is executed.
Version: 1.43
Home Page: https://www.naughter.com/hlinkctrl.html
License: Custom (PJ Naughter’s license)
Format: source code, binary

CInstanceChecker
Description: This class implements single instance apps. Limiting your app to single instance is more tricky in Win32 with the removal of the hPrevInstance parameter from WinMain and the introduction of separate address spaces.
Version: 1.25
Home Page: https://www.naughter.com/sinstance.html
License: Custom (PJ Naughter’s license)
Format: source code, binary

Lexilla, Scintilla, and SciTE
Description: Scintilla is a free source code editing component. It comes with complete source code and a license that permits use in any free project or commercial product.
As well as features found in standard text editing components, Scintilla includes features especially useful when editing and debugging source code. These include support for syntax styling, error indicators, code completion and call tips. The selection margin can contain markers like those used in debuggers to indicate breakpoints and the current line. Styling choices are more open than with many editors, allowing the use of proportional fonts, bold and italics, multiple foreground and background colours and multiple fonts.
Version: 5.6.9
Home Page: https://www.scintilla.org/
License: Custom (Neil Hodgson’s license)
Format: source code, binary

CScintillaCtrl, CScintillaDoc, CScintillaView
Description: These classes provides a MFC and ATL/WTL wrapping for the Scintilla edit control (http://www.scintilla.org). This control provides an open source cross platform edit control. Some of the features it provides include syntax colouring, call tips, brace highlighting, Styles, margins and markers to name but a few. The provided wrapper classes make it easier to include the control in MFC / WTL projects on Windows.
Version: 1.98
Home Page: https://www.naughter.com/scintilla.html
License: Custom (PJ Naughter’s license)
Format: source code, binary

CVersionInfo
Description: This simple little class encapsulates the SDK calls which access version info from Win32 files. Most executables and DLL’s have a VS_VERSION_INFO resource associated with them and this class provides a simple C++ class to programmatically access this information.
Version: 1.13
Home Page: https://www.naughter.com/versioninfo.html
License: Custom (PJ Naughter’s license)
Format: source code, binary

PJ Naughter’s license: You are allowed to include the source code in any product (commercial, shareware, freeware or otherwise) when your product is released in binary form. You are allowed to modify the source code in any way you want except you cannot modify the copyright details at the top of each module. If you want to distribute source code with your application, then you are only allowed to distribute versions released by the author. This is to maintain a single distribution point for the source code.

History

  • Version 0.01 (November 6th, 2026): This is a pre-release version of the software and should be considered a work in progress. Not all planned functionalities have been implemented yet, and some features may be incomplete, unavailable, or subject to change. While the current version has undergone initial development and validation, it has not been fully tested across all scenarios, environments, and use cases. As a result, users may encounter bugs, unexpected behavior, performance issues, or limitations that will be addressed in future releases. This version is intended primarily for evaluation, feedback, and early adoption purposes, and should not be considered production-ready.