From development build to public release
Visual Python Studio has a Windows application-publishing workflow and a separate SDK distribution model. The public website will distribute only packages selected and checked for a release.
Publication checklist
Build the application
Produce a complete Windows application using the supported publisher and note the IDE/SDK versions used.
Test outside the development environment
Confirm the package starts and its key workflows function on a supported Windows installation without relying on files from a development workspace.
Inspect packaged contents
Verify exactly which application and SDK files are included. Determine whether any proprietary Python source or development artifacts are exposed.
Release with a checksum
Publish a version, supported-platform notes, checksums, release notes, and a tested download URL.
A self-contained Windows executable does not by itself guarantee that Python source code is absent or unrecoverable. Source protection needs separate evaluation before commercial distribution.
Where downloads will live
The website is hosted on Cloudflare Pages. Large public packages can be delivered separately from Cloudflare R2 object storage, using a verified download domain once configured. Development ZIP files and private source repositories are excluded from the public site.
This material explains the workflow and current development direction. Exact menu labels, Python APIs and compatibility details will be checked against the public release and identified by version.
← All documentation