Write Python. Deploy Everywhere.
Posts
Toga 0.5.5 has been released! This release includes a major performance improvement for the WinForms event loop, more improvements to the Canvas widget aimed at aligning with the HTML5 Canvas API, as well as a range of smaller improvements and bug fixes.
June 2026 Status Update: June saw a major push on logging support for macOS 26, a continuing overhaul of Toga's Canvas API, as well as many other improvements.
Want to catch up on what the BeeWare community has been doing? Here's the recording of our monthly community call - The Buzz: Live!
Join us in 5 minutes for the first edition of The Buzz: Live!https://discord.gg/PaUjnTyr?event=1509015071890870443
Join us on Discord this Thursday 11PM UTC (7PM EDT, 4PM PST, 9AM AEST) for the first edition of The Buzz: Live - our monthly community meeting! The call will be recorded and posted to YouTube for those in other timezones.
Are you headed to #PyConIT? Want to learn more about packaging apps with #BeeWare? @juanlu.space is giving a workshop.
Unfortunately, the Bee Team is missing out, but you don't have to!
https://fed.brid.gy/r/https://bsky.app/profile/did:plc:p7v4p6njfpdv6gen4bllnkqm/post/3mmr4wpv3fk2j
Are you at #PyConUS? Ever wanted to write an application for your phone using Python? Or to write a GUI application for your laptop and package it so someone else can run it without installing Python? Or to publish a mobile wheel?
Come along to the BeeWare Open Space to find out more: 2PM Saturday, Room 201B
At PyCon US? We're running an open space at 2pm today, in room 202A: Make a GUI app with BeeWare. Ever wanted to write an application for your phone using Python? Or to write a GUI application for your laptop and package it so someone else can run it without installing Python? Come along to find out more, and to try out the BeeWare tools in person. Or - want to share ideas about how you are already using (or want to use) BeeWare? The core team will be there to chat. See you there! #PyConUS
@paulehoffman@infosec.exchange The policy says, explicitly, that:
- A human is always responsible
- The human contributor must understand the code they contribute
- The human reviewer must understand the code they're reviewing.
There is functionally no difference between accepting a PR from a drive-by human contributor, and accepting an AI-generated PR.
Yes, there is a different long term load balance on the maintainers, but that's an entirely different issue, and one unlikely to be fixed with a policy.
We've just rolled out a new policy for using generative AI tools when contributing to BeeWare.
In short, we don't care if you use AI tooling or not. However, we *do* expect that a human takes responsibility for everything that is contributed - including adhering to project guidelines - and for that human to declare if they've used AI tooling.
The full policy can be found here:
https://beeware.org/contributing/guide/policies/ai-policy/
2026Q2 Roadmap: Q1 has seen some significant improvements to Toga, Android packages, and a milestone for official iOS support. https://beeware.org/news/buzz/2026/2026q2-roadmap/
March 2026 Status Update: March has seen some big improvements in Briefcase, as well as some major discussions of design and policy issues in the rest of the project.
https://beeware.org/news/buzz/2026/march-2026-status-update/
Security advisory CVE-2026-33430: We have just published details of a privilege escalation vulnerability in Windows MSI installers created with Briefcase. Users who have published an MSI built using Briefcase will need to rebuild and republish their MSI to mitigate the issue. https://github.com/beeware/briefcase/security/advisories/GHSA-r3r2-35v9-v238
Are you currently using BeeWare to build an app?
Do you have something in mind that you want to build with BeeWare?
We're looking for people who are (or want to be) BeeWare users to share their story. If that's you - let us know!