ctkmaker-core
The CustomTkinter runtime that powers CTkMaker — a visual designer for CustomTkinter UIs.
It's a fork of CustomTkinter (v5.2.2 baseline). What lands here is driven by what CTkMaker needs — this isn't a general-purpose alternative to upstream, just a focused runtime that anyone is welcome to install and use.
PyPI: ctkmaker-core
What it gives you over CustomTkinter 5.2.2
- Curated bug fixes — cherry-picked from the active fork landscape (Custom2kinter, ToastyToast25, upstream PRs).
- Drop-in module name — still
import customtkinter as ctk. CTkMessagebox, CTkColorPicker, CTkScrollableDropdown, CTkColorPalette work unchanged.
Per-release changes tracked in CHANGELOG.md.
Installation
pip uninstall customtkinter # if installed — both share the customtkinter module name
pip install ctkmaker-core
import customtkinter as ctk
print(ctk.__fork__) # "ctkmaker-core"
print(ctk.__fork_version__) # "5.3.1"
print(ctk.__version__) # "5.2.2" (upstream baseline)
Platform support
- Primary target: Windows 11 (development + manual testing).
- Linux / macOS: best-effort. Bug reports welcome via issues; feature direction follows CTkMaker.
License
MIT. See LICENSE and NOTICE for attributions to upstream CustomTkinter (Tom Schimansky) and other fork contributors whose work was cherry-picked.
Credits & contributing
ctkmaker-core exists because of the people whose CustomTkinter work was cherry-picked into it. Thank you to:
- Tom Schimansky — author of CustomTkinter; the baseline this fork is built on.
- Federico Spada —
Custom2kinteris the primary source of cherry-picked fixes and theconfigure()/cget()audit triad. - ToastyToast25 — DPI, destroy-cleanup, and rendering improvements.
- ...and every individual PR author credited per-pick in
CHANGELOG.md.
If you've shipped a CustomTkinter fix or improvement of your own, please open an issue or PR — happy to look at it together.
Project status
Pre-1.0. CTkMaker is the primary consumer and drives the roadmap.
Metadata
Release files for ctkmaker-core 5.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ctkmaker_core-5.5.1.tar.gz | 128.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ctkmaker_core-5.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 293.8 kB
Release files / ctkmaker_core-5.5.1.tar.gz
| Download URL | ctkmaker_core-5.5.1.tar.gz |
|---|---|
| Size | 128.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5a24627b56cbd798e713ad1f5d525203d150a49027023dc6a3b450f94a43055
|
|
BLAKE2b-256 checksum How to use checksums |
e487a22e40caa72f29e30e77395ec89e631bfda2ececc52d7b6ce2e16c11dd71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / ctkmaker_core-5.5.1-py3-none-any.whl
| Download URL | ctkmaker_core-5.5.1-py3-none-any.whl |
|---|---|
| Size | 165.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c56bc1f0ce9b754a6ab8284290625ee90b51af67665c52378da6c4da14872340
|
|
BLAKE2b-256 checksum How to use checksums |
4c2da89473f851364c1fea68d8a51dd9e48d863d4d06617d798f654c6beb0c82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for ctkmaker-core 5.5.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.