Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
diff --git a/ar_AR/news/buzz/atom.xml b/ar_AR/news/buzz/atom.xml
index 84502caf14..8599e4b33e 100644
--- a/ar_AR/news/buzz/atom.xml
+++ b/ar_AR/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/ar_AR/news/buzz/index.html b/ar_AR/news/buzz/index.html
index ef1dbb4d67..b00c23aac6 100644
--- a/ar_AR/news/buzz/index.html
+++ b/ar_AR/news/buzz/index.html
@@ -188,6 +188,67 @@
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
-
-نُشِرَ من طرف
-
-
- Katie McLaughlin
-
-
-في
- 1 February 2017
-
-
-
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
+
+نُشِرَ من طرف
+
+
+ Katie McLaughlin
+
+
+في
+ 1 February 2017
+
+
+
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
diff --git a/cs/news/buzz/atom.xml b/cs/news/buzz/atom.xml
index 305a9b738b..2b41fd1896 100644
--- a/cs/news/buzz/atom.xml
+++ b/cs/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/cs_CZ/bee/index.html b/cs_CZ/bee/index.html
index 49cb3248e3..96e9d5f5a2 100644
--- a/cs_CZ/bee/index.html
+++ b/cs_CZ/bee/index.html
@@ -175,12 +175,12 @@
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
diff --git a/da/news/buzz/atom.xml b/da/news/buzz/atom.xml
index ae200fe197..5deb48daf3 100644
--- a/da/news/buzz/atom.xml
+++ b/da/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/da_DK/bee/index.html b/da_DK/bee/index.html
index 53b02c9dcd..5a70815282 100644
--- a/da_DK/bee/index.html
+++ b/da_DK/bee/index.html
@@ -175,12 +175,12 @@
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
diff --git a/de_DE/news/buzz/atom.xml b/de_DE/news/buzz/atom.xml
index 237f77eab7..47b714d45a 100644
--- a/de_DE/news/buzz/atom.xml
+++ b/de_DE/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/de_DE/news/buzz/index.html b/de_DE/news/buzz/index.html
index 7fc5a92081..3194f68474 100644
--- a/de_DE/news/buzz/index.html
+++ b/de_DE/news/buzz/index.html
@@ -188,6 +188,67 @@
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Vor einigen Monaten haben wir angekündigt, dass das BeeWare-Projekt von der PSF einen Zuschuss erhalten hat, um unsere Unterstützung für Android zu verbessern. Damals riefen wir Auftragnehmer auf, uns bei der Durchführung dieser Arbeit zu unterstützen.
-
Wir freuen uns sehr, euch mitteilen zu können, dass wir jetzt einen Auftragnehmer ausgewählt haben: Asheesh Laroia.
-
Asheesh ist ein regelmäßiger Referent bei Python-Veranstaltungen, wo er sich in eine Reihe von detaillierten und komplexen Themen vertieft hat. Er hat uns auch mit der Liste unkonventioneller technischer Integrationsprojekte beeindruckt, an denen er in professioneller und gelegentlicher Tätigkeit mitgewirkt hat.
-
Auf die Frage, warum er sich für eine Zusammenarbeit mit BeeWare für diesen Auftrag beworben hat, sagte Asheesh: "Ich benutze jeden Tag ein Android-Telefon und fühle mich geehrt, an der Umsetzung der BeeWare-Vision mitwirken zu können, Python zur Erstellung erstklassiger, nativer Anwendungen einzusetzen.
-
Asheesh wird seine Arbeit Mitte Dezember aufnehmen, und wenn alles gut läuft, sollten wir ab Mitte bis Ende Februar signifikante Ergebnisse sehen. Wenn du den Fortschritt verfolgen möchtest, kannst du BeeWare auf Twitter verfolgen; wir werden auch größere Updates auf diesem Blog veröffentlichen.
Vor einigen Monaten haben wir angekündigt, dass das BeeWare-Projekt von der PSF einen Zuschuss erhalten hat, um unsere Unterstützung für Android zu verbessern. Damals riefen wir Auftragnehmer auf, uns bei der Durchführung dieser Arbeit zu unterstützen.
+
Wir freuen uns sehr, euch mitteilen zu können, dass wir jetzt einen Auftragnehmer ausgewählt haben: Asheesh Laroia.
+
Asheesh ist ein regelmäßiger Referent bei Python-Veranstaltungen, wo er sich in eine Reihe von detaillierten und komplexen Themen vertieft hat. Er hat uns auch mit der Liste unkonventioneller technischer Integrationsprojekte beeindruckt, an denen er in professioneller und gelegentlicher Tätigkeit mitgewirkt hat.
+
Auf die Frage, warum er sich für eine Zusammenarbeit mit BeeWare für diesen Auftrag beworben hat, sagte Asheesh: "Ich benutze jeden Tag ein Android-Telefon und fühle mich geehrt, an der Umsetzung der BeeWare-Vision mitwirken zu können, Python zur Erstellung erstklassiger, nativer Anwendungen einzusetzen.
+
Asheesh wird seine Arbeit Mitte Dezember aufnehmen, und wenn alles gut läuft, sollten wir ab Mitte bis Ende Februar signifikante Ergebnisse sehen. Wenn du den Fortschritt verfolgen möchtest, kannst du BeeWare auf Twitter verfolgen; wir werden auch größere Updates auf diesem Blog veröffentlichen.
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
-Publicado por
-
-
- Russell Keith-Magee
-
-
-en
- 2023-11-01
-
-
... más artículos
diff --git a/es/noticias/zumbido/atom.xml b/es/noticias/zumbido/atom.xml
index 1226ec025e..48c863479e 100644
--- a/es/noticias/zumbido/atom.xml
+++ b/es/noticias/zumbido/atom.xml
@@ -1,5 +1,44 @@
-El Zumbidourn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+El Zumbidourn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1763,33 +1802,4 @@ Also shout out to the BeeWare community for answering my queries and reviewing m
<p>Aún son los primeros días para BeeWare. El apoyo financiero significa un progreso más rápido. Más widgets. Mejor documentación. Más de todo lo que has visto hasta ahora de BeeWare. Si puedo encontrar financiación a tiempo completo para mí -o mejor aún, para mí y para un equipo pequeño-, no tengo dudas de que la suite BeeWare se convertirá en una alternativa viable para proyectos comerciales en muy poco tiempo. Lo mejor de todo, seremos capaces de hacer esto sin tener que renunciar a los ideales del movimiento de código abierto.</p>
<p>Estoy emocionado por lo que le depara el futuro a BeeWare. Espero que nos acompañes en este viaje.</p>
<p>(Y si tu estás pensando en registrarte, y vienes a PyCon US en Portland este mes de mayo, déjame dejar una pista suave ... inscríbete ahora. Vale la pena #cryptic)</p>
-Ven al sprint con nosotros en PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>Los boletos para PyCon US 2017 han sido regalados. ¡Esperamos ver a todos los que lleguen a la conferencia en el stand 103!</strong></p>
-<hr class="docutils" />
-<p><em>¿Quieres ir al @PyCon, no puede permitírselo? @PyBeeWare tiene 2 entradas para regalar. Envía un correo electrónico a contact@beeware.org y cuéntanos por qué quiere estar allí!</em></p>
-<p>— PyBee (@PyBeeWare) 30 e Enero, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> se está llevando cabo en Portland, Oregon del 17 al 25 de mayo, y está destinado a ser otra increíble conferencia.</p>
-<p>Por segundo año consecutivo, el equipo <a class="reference external" href="https://beeware.org">BeeWare</a> estará en el sitio con un <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">stand en el salón de exhibiciones</a>, junto con otros proyectos de Código Abierto del mundo Python.</p>
-<p>Con este stand, tenemos dos entradas para la conferencia. Esto incluye:</p>
-<ul class="simple">
-<li>acceso a la recepción de apertura</li>
-<li>3 días de conferencias, salón de exposiciones/feria de trabajo</li>
-<li>desayunos, pausas, almuerzos y bolsa de <em>swag</em></li>
-</ul>
-<p>La cosa es que tanto <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> como yo, ya nos hemos registrado.</p>
-<p>Por lo tanto, queremos darte un boleto.</p>
-<p>Sí <strong>a ti.</strong></p>
-<p>Si tu puedes llegar a Portland en los días de la conferencia, queremos darte nuestro boleto gratis.</p>
-<p>¿Qué queremos a cambio?</p>
-<p>Sólo un poco de tu tiempo.</p>
-<p>El <a class="reference external" href="/es/comunidad/equipo/">equipo Bee</a> estará ayudando al personal de nuestro stand, pero también nos gustaría ver (y dar!) charlas, así que ayudarnos mientras estamos corriendo fuera del puesto sería encantador. (Además, y estoy segura de que Russell estaría de acuerdo, sólo ayudando en la cabina te ganas una <a class="reference external" href="/es/contribuir/monedas-de-desafio">moneda</a>)</p>
-<p>Además, nos encantaría que te quedaras a los famosos Sprints de código. Estos se celebran en los cuatro días posteriores al evento, mientras las personas se encuentran aun en la ciudad. Tomaremos café, almorzaremos y tendremos acceso a una habitación llena de mesas, sillas y cantidad copiosa de tomas de corriente, y escribiremos código para los diferente proyectos. Estaremos haciendo un <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">sprint de BeeWare</a> donde estaremos asesorando y ayudando a los colaboradores principiantes a ganar su primera <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">moneda brillante de desafío</a></p>
-<p>¿Esto suena como algo que te interesa?</p>
-<p>Por favor, <a class="reference external" href="mailto:contact@beeware.org">envíanos un correo electrónico!</a></p>
-<p>¡Cuéntanos acerca de tí! Quién eres, qué haces, por qué quieres ir a PyCon y lo que te interesa de Python.</p>
-<p>Necesitamos asignar nuestras entradas con anticipación, así que envíanos un correo electrónico <strong>antes del 12 deFebrero, 2017</strong></p>
-<p>Si tiene alguna pregunta solo pregunta <a class="reference external" href="https://twitter.com/glasnt">a mi</a> o a <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>¡Nos encantaría verte allí! ✨</p>
-<p>[Este artículo ha sido publicado en
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/es/noticias/zumbido/index.html b/es/noticias/zumbido/index.html
index 07082ce4e2..0c40af2b88 100644
--- a/es/noticias/zumbido/index.html
+++ b/es/noticias/zumbido/index.html
@@ -188,6 +188,67 @@
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
-
-Publicado por
-
-
- Katie McLaughlin
-
-
-en
- 1 February 2017
-
-
-
Los boletos para PyCon US 2017 han sido regalados. ¡Esperamos ver a todos los que lleguen a la conferencia en el stand 103!
-
-
¿Quieres ir al @PyCon, no puede permitírselo? @PyBeeWare tiene 2 entradas para regalar. Envía un correo electrónico a contact@beeware.org y cuéntanos por qué quiere estar allí!
-
— PyBee (@PyBeeWare) 30 e Enero, 2017
-
-
PyCon US 2017 se está llevando cabo en Portland, Oregon del 17 al 25 de mayo, y está destinado a ser otra increíble conferencia.
-
Por segundo año consecutivo, el equipo BeeWare estará en el sitio con un stand en el salón de exhibiciones, junto con otros proyectos de Código Abierto del mundo Python.
-
Con este stand, tenemos dos entradas para la conferencia. Esto incluye:
-
-
acceso a la recepción de apertura
-
3 días de conferencias, salón de exposiciones/feria de trabajo
-
desayunos, pausas, almuerzos y bolsa de swag
-
-
La cosa es que tanto Russell como yo, ya nos hemos registrado.
-
Por lo tanto, queremos darte un boleto.
-
Sí a ti.
-
Si tu puedes llegar a Portland en los días de la conferencia, queremos darte nuestro boleto gratis.
-
¿Qué queremos a cambio?
-
Sólo un poco de tu tiempo.
-
El equipo Bee estará ayudando al personal de nuestro stand, pero también nos gustaría ver (y dar!) charlas, así que ayudarnos mientras estamos corriendo fuera del puesto sería encantador. (Además, y estoy segura de que Russell estaría de acuerdo, sólo ayudando en la cabina te ganas una moneda)
-
Además, nos encantaría que te quedaras a los famosos Sprints de código. Estos se celebran en los cuatro días posteriores al evento, mientras las personas se encuentran aun en la ciudad. Tomaremos café, almorzaremos y tendremos acceso a una habitación llena de mesas, sillas y cantidad copiosa de tomas de corriente, y escribiremos código para los diferente proyectos. Estaremos haciendo un sprint de BeeWare donde estaremos asesorando y ayudando a los colaboradores principiantes a ganar su primera moneda brillante de desafío
+
+Publicado por
+
+
+ Katie McLaughlin
+
+
+en
+ 1 February 2017
+
+
+
Los boletos para PyCon US 2017 han sido regalados. ¡Esperamos ver a todos los que lleguen a la conferencia en el stand 103!
+
+
¿Quieres ir al @PyCon, no puede permitírselo? @PyBeeWare tiene 2 entradas para regalar. Envía un correo electrónico a contact@beeware.org y cuéntanos por qué quiere estar allí!
+
— PyBee (@PyBeeWare) 30 e Enero, 2017
+
+
PyCon US 2017 se está llevando cabo en Portland, Oregon del 17 al 25 de mayo, y está destinado a ser otra increíble conferencia.
+
Por segundo año consecutivo, el equipo BeeWare estará en el sitio con un stand en el salón de exhibiciones, junto con otros proyectos de Código Abierto del mundo Python.
+
Con este stand, tenemos dos entradas para la conferencia. Esto incluye:
+
+
acceso a la recepción de apertura
+
3 días de conferencias, salón de exposiciones/feria de trabajo
+
desayunos, pausas, almuerzos y bolsa de swag
+
+
La cosa es que tanto Russell como yo, ya nos hemos registrado.
+
Por lo tanto, queremos darte un boleto.
+
Sí a ti.
+
Si tu puedes llegar a Portland en los días de la conferencia, queremos darte nuestro boleto gratis.
+
¿Qué queremos a cambio?
+
Sólo un poco de tu tiempo.
+
El equipo Bee estará ayudando al personal de nuestro stand, pero también nos gustaría ver (y dar!) charlas, así que ayudarnos mientras estamos corriendo fuera del puesto sería encantador. (Además, y estoy segura de que Russell estaría de acuerdo, sólo ayudando en la cabina te ganas una moneda)
+
Además, nos encantaría que te quedaras a los famosos Sprints de código. Estos se celebran en los cuatro días posteriores al evento, mientras las personas se encuentran aun en la ciudad. Tomaremos café, almorzaremos y tendremos acceso a una habitación llena de mesas, sillas y cantidad copiosa de tomas de corriente, y escribiremos código para los diferente proyectos. Estaremos haciendo un sprint de BeeWare donde estaremos asesorando y ayudando a los colaboradores principiantes a ganar su primera moneda brillante de desafío
diff --git a/content/project/projects/support/python-apple-support/contents.lr b/content/project/projects/support/python-apple-support/contents.lr
-index 9071485923..89df1a5d0d 100644
---- a/content/project/projects/support/python-apple-support/contents.lr
-+++ b/content/project/projects/support/python-apple-support/contents.lr
-@@ -15,3 +15,7 @@ incomplete: yes
-description: A meta-package for building a version of Python that can be embedded into a macOS, iOS, tvOS or watchOS project.
----
-customlogo: yes
-+---
-+image: python-apple-support.png
-+---
-+github_repo: beeware/Python-Apple-support
-
-
-
-
-
-
-
-
-
+
@@ -323,7 +201,7 @@
- El contenido de esta página está incompleto, puedes ayudar expandiéndolo.
+ El contenido de esta página está incompleto, puedes ayudar expandiéndolo.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
diff --git a/it_IT/news/buzz/atom.xml b/it_IT/news/buzz/atom.xml
index 35341ebd33..b5b42429fa 100644
--- a/it_IT/news/buzz/atom.xml
+++ b/it_IT/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/it_IT/news/buzz/index.html b/it_IT/news/buzz/index.html
index 91fb2ca10d..f199756a74 100644
--- a/it_IT/news/buzz/index.html
+++ b/it_IT/news/buzz/index.html
@@ -188,6 +188,67 @@
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
-
-Postato da
-
-
- Katie McLaughlin
-
-
-il
- 1 February 2017
-
-
-
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
+
+Postato da
+
+
+ Katie McLaughlin
+
+
+il
+ 1 February 2017
+
+
+
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
diff --git a/ko/news/buzz/atom.xml b/ko/news/buzz/atom.xml
index dda53fdd5e..4297c4300e 100644
--- a/ko/news/buzz/atom.xml
+++ b/ko/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/ko_KR/bee/index.html b/ko_KR/bee/index.html
index 753b3acfcd..fb106995ba 100644
--- a/ko_KR/bee/index.html
+++ b/ko_KR/bee/index.html
@@ -175,12 +175,12 @@
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
diff --git a/news/buzz/atom.xml b/news/buzz/atom.xml
index d99fe169b4..2d7dbb3154 100644
--- a/news/buzz/atom.xml
+++ b/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/news/buzz/index.html b/news/buzz/index.html
index ae0d0e7782..3f01ced129 100644
--- a/news/buzz/index.html
+++ b/news/buzz/index.html
@@ -188,6 +188,67 @@
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
-Posted by
-
-
- Russell Keith-Magee
-
-
-on
- 2023-11-01
-
-
... more articles
diff --git a/pl/news/buzz/atom.xml b/pl/news/buzz/atom.xml
index d5876ee18f..e230308654 100644
--- a/pl/news/buzz/atom.xml
+++ b/pl/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-Nowinyurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+Nowinyurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/pl_PL/bee/index.html b/pl_PL/bee/index.html
index 5955ec1021..5f8f532c41 100644
--- a/pl_PL/bee/index.html
+++ b/pl_PL/bee/index.html
@@ -175,12 +175,12 @@
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
-
-Opublikowane przez
-
-
- Russell Keith-Magee
-
-
-dnia
- 1 November 2023
-
-
-
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
+
+Opublikowane przez
+
+
+ Russell Keith-Magee
+
+
+dnia
+ 1 November 2023
+
+
+
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
-
-Opublikowane przez
-
-
- Russell Keith-Magee
-
-
-dnia
- 26 November 2019
-
-
-
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
+
+Opublikowane przez
+
+
+ Russell Keith-Magee
+
+
+dnia
+ 26 November 2019
+
+
+
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
-
-Opublikowane przez
-
-
- Katie McLaughlin
-
-
-dnia
- 1 February 2017
-
-
-
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
+
+Opublikowane przez
+
+
+ Katie McLaughlin
+
+
+dnia
+ 1 February 2017
+
+
+
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
diff --git a/pr_BR/news/buzz/atom.xml b/pr_BR/news/buzz/atom.xml
index 9ffa07e053..0821fe0357 100644
--- a/pr_BR/news/buzz/atom.xml
+++ b/pr_BR/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/pt_BR/bee/index.html b/pt_BR/bee/index.html
index 563f5fe696..b5120b2241 100644
--- a/pt_BR/bee/index.html
+++ b/pt_BR/bee/index.html
@@ -175,12 +175,12 @@
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Alguns meses atrás, nós anunciamos que o projecto BeeWare tem recebido um auxílio da PSF para aumentar nosso suporte ao Android. Naquele momento, nós emitimos uma chamada de trabalhadores para nos ajudar a completar este trabalho.
-
Nós estamos muito felizes de anunciar que nós agora selecionamos um contratado: Asheesh Laroia
-
Alguns meses atrás, nós anunciamos que o projecto BeeWare tem recebido um auxílio da PSF para aumentar nosso suporte ao Android. Naquele momento, nós emitimos uma chamada de trabalhadores para nos ajudar a completar este trabalho.
-
Asheesh é um apresentador frequente em eventos Python, onde ele tem mergulhado em uma variedade de tópicos detalhados e complexos. Ele também nos impressionou com uma lista de projetos de integração de engenharia não convencionais que ele tem se envolvido com sua capacidade professional e casual.
-
Quando perguntado o motivo de ter aplicado para trabalhar com a BeeWare neste contrato, Asheesh falou: "Eu uso um telefone Android todo dia, e estou honrado em poder ajudar a implementar a visão BeeWare do uso do Python em aplicações nativas, primeira-classe."
-
Asheesh irá começar trabalhando no meio de Dezembro, e se tudo for bem, nós poderemos ver resultados significantes no meio para o final de Fevereiro. Se você gostaria de ficar de olho no progresso, você pode seguir o BeeWare no Twitter; nós iremos também postar grandes updates neste blog.
Alguns meses atrás, nós anunciamos que o projecto BeeWare tem recebido um auxílio da PSF para aumentar nosso suporte ao Android. Naquele momento, nós emitimos uma chamada de trabalhadores para nos ajudar a completar este trabalho.
+
Nós estamos muito felizes de anunciar que nós agora selecionamos um contratado: Asheesh Laroia
+
Alguns meses atrás, nós anunciamos que o projecto BeeWare tem recebido um auxílio da PSF para aumentar nosso suporte ao Android. Naquele momento, nós emitimos uma chamada de trabalhadores para nos ajudar a completar este trabalho.
+
Asheesh é um apresentador frequente em eventos Python, onde ele tem mergulhado em uma variedade de tópicos detalhados e complexos. Ele também nos impressionou com uma lista de projetos de integração de engenharia não convencionais que ele tem se envolvido com sua capacidade professional e casual.
+
Quando perguntado o motivo de ter aplicado para trabalhar com a BeeWare neste contrato, Asheesh falou: "Eu uso um telefone Android todo dia, e estou honrado em poder ajudar a implementar a visão BeeWare do uso do Python em aplicações nativas, primeira-classe."
+
Asheesh irá começar trabalhando no meio de Dezembro, e se tudo for bem, nós poderemos ver resultados significantes no meio para o final de Fevereiro. Se você gostaria de ficar de olho no progresso, você pode seguir o BeeWare no Twitter; nós iremos também postar grandes updates neste blog.
-
-Publicado por
-
-
- Katie McLaughlin
-
-
-em
- 1 February 2017
-
-
-
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
+
+Publicado por
+
+
+ Katie McLaughlin
+
+
+em
+ 1 February 2017
+
+
+
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
diff --git a/tr/news/buzz/atom.xml b/tr/news/buzz/atom.xml
index e62bf8ed58..55f8622190 100644
--- a/tr/news/buzz/atom.xml
+++ b/tr/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-Vızıltıurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+Vızıltıurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/tr_TR/bee/index.html b/tr_TR/bee/index.html
index a24e1847f7..2579180144 100644
--- a/tr_TR/bee/index.html
+++ b/tr_TR/bee/index.html
@@ -175,12 +175,12 @@
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
diff --git a/zh_CN/news/buzz/atom.xml b/zh_CN/news/buzz/atom.xml
index 65f3cae704..c228ddcbce 100644
--- a/zh_CN/news/buzz/atom.xml
+++ b/zh_CN/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/zh_CN/news/buzz/index.html b/zh_CN/news/buzz/index.html
index 50daef628f..42e158551f 100644
--- a/zh_CN/news/buzz/index.html
+++ b/zh_CN/news/buzz/index.html
@@ -188,6 +188,67 @@
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
+
Malcolm Smith
+
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
Malcolm is the creator of Chaquopy, which aims to make it as easy as possible to use Python in Android apps. With BeeWare, he's now looking forward to expanding that mission to all desktop and mobile platforms.
+
Russell Martin
+
Russell is a tinkerer and aspiring creator. He fell in love with python years ago and wants to see apps built with it everywhere. If he isn't writing code, he's probably falling down a Wikipedia rabbit hole or playing sys admin to his bloated home lab.
diff --git a/zh_TW/news/buzz/atom.xml b/zh_TW/news/buzz/atom.xml
index b7617952c4..2d4f6cc1a6 100644
--- a/zh_TW/news/buzz/atom.xml
+++ b/zh_TW/news/buzz/atom.xml
@@ -1,5 +1,44 @@
-The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-06-03T00:00:00ZBeeWare's official blogMay 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
+The Buzzurn:uuid:0f18b85e-c1d4-3086-935d-f801edebea162024-07-01T00:00:00ZBeeWare's official blogJune 2024 Status update2024-07-01T00:00:00ZRussell Keith-Mageeurn:uuid:d5c031ad-9918-3171-9ead-c576bfd1d711<p>In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.</p>
+<div class="section" id="what-we-ve-done">
+<h2>What we've done</h2>
+<ul class="simple">
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1781">added support for packaging console apps to Briefcase</a>. This involved adding a new <tt class="docutils literal">.pkg</tt> packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of <tt class="docutils literal">.pkg</tt> format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).</li>
+<li>We modified Briefcase to <a class="reference external" href="https://github.com/beeware/briefcase/pull/1849">distribute the stub binaries as standalone artefacts, rather than including them in the app template</a>. We also <a class="reference external" href="https://github.com/beeware/briefcase/pull/1855">significantly optimised how Briefcase uses templates</a>. Between these two changes, the download size required for a first project on macOS has been reduced from around 200MB, to less than 4MB.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1864">isolated Briefcase's use of Cookiecutter</a> so that all of Briefcase's cached content is contained in Briefcase's own cache folder.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/briefcase/pull/1856">added support for distribution certificates on macOS</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2585">modified Toga's APIs to use namedtuple types for Size and Position references</a>.</li>
+<li>We corrected a number of stability issues with Toga's testbed CI, and <a class="reference external" href="https://github.com/beeware/toga/pull/2670">added CI testing for Wayland on Linux</a>.</li>
+<li>We completed a <a class="reference external" href="https://github.com/beeware/toga/pull/2252">major overhaul of typing in Toga's API surface</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2642">added support for conditional coverage in Toga's testing</a>. It is now possible to get a clean coverage report without running the test suite on every Python version and every platform.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2636">added an official API for customizing the system-installed menu items</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/1930">added an API for detecting the screens available for an app to use, and for setting the position of windows relative to those screens</a>.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2649">added support for "simple" apps</a> - apps that don't have menu bars.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2651">added support for apps whose lifecycle isn't tied to a single "Main" window</a>, such as background apps (apps that don't have any windows) and document-based apps.</li>
+<li>We <a class="reference external" href="https://github.com/beeware/toga/pull/2669">added support for app modal dialogs</a>.</li>
+</ul>
+</div>
+<div class="section" id="what-s-next">
+<h2>What's next?</h2>
+<p>Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like <tt class="docutils literal">pip</tt>, <tt class="docutils literal">cibuildwheel</tt>, <tt class="docutils literal"><span class="pre">meson-python</span></tt> and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.</p>
+</div>
+<div class="section" id="want-to-get-involved">
+<h2>Want to get involved?</h2>
+<p>Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:</p>
+<ol class="arabic simple">
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2251">Update the Toga testbed test suite to use Pixel 7 Pro device sizes</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/780">Filter out a message generated after Xcode updates</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/808">Add the ability to configure the ABIs built by an Android project</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1099">Rationalise the application of adhoc signing on macOS</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1270">Add support for custom PyPI repositories</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1393">Document how to debug an application in popular IDEs</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/737">Add an option to select the Android base image when creating new emulators</a></li>
+<li><a class="reference external" href="https://github.com/beeware/toga/issues/2305">Add an API to entirely replace the style of a widget</a></li>
+<li><a class="reference external" href="https://github.com/beeware/briefcase/issues/1876">Correct the handling of quotation marks in Android apps</a></li>
+</ol>
+<p>Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a <a class="reference external" href="https://briefcase.readthedocs.io/en/latest/how-to/contribute-code.html">guide on setting up a Briefcase development environment</a>; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the <a class="reference external" href="https://beeware.org/bee/chat/">BeeWare Discord server</a>.</p>
+</div>
+May 2024 Status Update2024-06-03T00:00:00ZRussell Keith-Mageeurn:uuid:c66225fd-df0b-372a-acc0-cc3e41cd980e<p>BeeWare activity in May was dominated by preparing for and attending PyCon US in Pittsburgh. That event generated a lot of activity in the BeeWare project - but we've also added some other significant improvements.</p>
<div class="section" id="what-we-ve-done">
<h2>What we've done</h2>
<ul class="simple">
@@ -1765,58 +1804,4 @@ In practice this meant that I had to manually touch almost every widget of all b
<p>It's still early days for BeeWare. Financial support means faster progress. More widgets. Better documentation. More of everything you’ve seen so far from BeeWare. If I can find full time funding for myself - or better still, for myself and a small team - then I have no doubt that the BeeWare suite will become a viable alternative for commercial projects in very short order. Best of all, we will be able to do this without having to give up on the ideals of the open source movement.</p>
<p>I'm excited for what the future holds for BeeWare. I hope you'll join me on this journey.</p>
<p>(And if you’re contemplating signing up, and you’re coming to PyCon US in Portland this May, let me drop a gentle hint… sign up now. It will be worth it #cryptic)</p>
-Come sprint with us at PyCon US 20172017-02-01T00:00:00ZKatie McLaughlinurn:uuid:76dd3fba-dda2-350e-a0b0-3468ceced7c1<p><strong>The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!</strong></p>
-<hr class="docutils" />
-<p><em>Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!</em></p>
-<p>— PyBee (@PyBeeWare) January 30, 2017</p>
-<hr class="docutils" />
-<p><a class="reference external" href="https://us.pycon.org/2017/">PyCon US 2017</a> is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.</p>
-<p>For the second year in a row, the <a class="reference external" href="https://beeware.org">BeeWare team</a>
-will be on site with a <a class="reference external" href="https://twitter.com/PyBeeWare/status/737043373953978368">booth in the Exhibit
-Hall</a>, along
-with other Open Source projects from the Python world.</p>
-<p>With this booth, we get two tickets to the conference. This includes:</p>
-<ul class="simple">
-<li>access to the opening reception</li>
-<li>3 days of conference talks, expo hall / job fair</li>
-<li>breakfasts, breaks, lunches, and</li>
-<li>swag bag</li>
-</ul>
-<p>Thing is, both <a class="reference external" href="https://twitter.com/freakboy3742">Russell</a> and I have
-already registered.</p>
-<p>So, we want to give you the ticket.</p>
-<p>Yes, <strong>you.</strong></p>
-<p>If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.</p>
-<p>What do we want in return?</p>
-<p>Just a little bit of your time.</p>
-<p>The <a class="reference external" href="https://beeware.org/community/team/">Bee Team</a> will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-<a class="reference external" href="https://beeware.org/contributing/challenge-coins/">coin</a>)</p>
-<p>Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a <a class="reference external" href="https://twitter.com/PyBeeWare/status/738400648614449152">BeeWare
-sprint</a>
-where we will be mentoring and helping first time contributors earn
-their shiny <a class="reference external" href="https://twitter.com/PyBeeWare/status/738425474754314240">challenge
-coin</a></p>
-<p>Does this sound like something you'd be interested in?</p>
-<p>Please, <a class="reference external" href="mailto:contact@beeware.org">email us!</a></p>
-<p>Tell us about yourself! Who you are, what you do, why you want to go to
-PyCon and what makes you interested in Python.</p>
-<p>We need to allocate our tickets early, so please email us <strong>by February
-12, 2017</strong></p>
-<p>If you have any questions, just ask
-<a class="reference external" href="https://twitter.com/glasnt">myself</a> or
-<a class="reference external" href="https://twitter.com/freakboy3742">Russell</a>!</p>
-<p>We'd love to see you there! ✨</p>
-<p>[This article has been cross-posted on
-<a class="reference external" href="http://glasnt.com/blog/2017/02/01/come-sprint-with-beeware.html">glasnt.com/blog</a>]</p>
\ No newline at end of file
diff --git a/zh_TW/news/buzz/index.html b/zh_TW/news/buzz/index.html
index 6add7c3d58..c698f91fd1 100644
--- a/zh_TW/news/buzz/index.html
+++ b/zh_TW/news/buzz/index.html
@@ -188,6 +188,67 @@
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
-
-
What we've done
-
-
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
-
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
-
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
-
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
-
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
-
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In June, BeeWare made a lot of progress, landing lots of new features - many of which have been the subject of requests and discussions for a long time.
+
+
What we've done
+
+
We added support for packaging console apps to Briefcase. This involved adding a new .pkg packaging type for macOS, as well as a number of other improvements to the stub app and MSI packaging on Windows. In addition to providing a way to package console apps on macOS, the addition of .pkg format means it is now possible to distribute apps using centralised device management tooling (such as Kandji or FleetDM).
Work on Toga's App interface isn't quite finished - we're expecting to finalise the Document API in the near future. Once that work is complete, our focus will be the mobile Python binary packaging ecosystem. The work we've done so far this year has led to CPython 3.13 formally supporting iOS and Android as Tier 3 supported platforms; the next step is ensuring that the rest of the community can build iOS and Android packages. This will involve improvements to tools like pip, cibuildwheel, meson-python and more. We expect that this work will take most of the rest of the quarter to release; but there should be some initial signs of progress by the end of the month.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
In October, we've (finally!) reached a major milestone - but there's still lots of work to be done!
+
+
What we've done
+
+
We finally finished the Toga audit!!. We now have 100% test coverage of all Toga code on macOS, Windows, Linux/GTK, iOS and Android, with a consistent and fully documented API across all widgets. This has been a truly mammoth project, resolving countless bugs, adding dozens of new features, and improving platform support (especially on Windows and Android). Once we've finalised a couple of housekeeping issues, we will release Toga 0.4 incorporating all these changes. This will hopefully occur later this week.
+
We attended the Python Core Team Sprint at the RedHat offices in Brno, Czechia. As a result of this attendance, we produced a draft of PEP 730, which is the first step towards formalizing support for iOS in CPython. An analogous Android PEP will be drafted once we've sorted out the process around the iOS PEP (as this is the first time a platform has gone through a formal process to be added to PEP 11's Tier 3 list).
+
We reworked the build system for Apple support packages to separate the compilation of dependencies (like BZip2 and OpenSSL) from the compilation of Python itself. These libraries are updated infrequently, and on a completely different cadence to CPython itself, so treating them as re-usable resources rather than something that needs to be compiled at the same time as Python will significantly improve CPython build times.
+
We released Briefcase 0.3.16, formalizing our support for Python 3.12, and adding the new support for dynamic libraries on iOS. This release also formally downgrades our support for AppImage, following extended problems in supporting AppImage as an output format.
+
We released Rubicon ObjC 0.4.7, formalising our support for Python 3.12.
Now that we've finally finished the widget audit, we can finally release Toga 0.4, and start using the foundation that we've spent the last 12 months building.
+
In November, we'll start the work of upstreaming iOS patches to CPython core. The PEP we've drafted is nearing a form where it can be submitted to the Steering Council for approval, but the drafting process has raised a couple of technical issues that need to be investigated. However, while we wait for formal acceptance of the PEP, we will continue working on building continuous integration for our iOS CPython builds, and begin preparing patches that can be merged into CPython.
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
-
-
What we've done
-
-
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
-
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
-
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
-
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
-
Thanks to a community contribution, we added support for PyGame to Briefcase.
-
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
-
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
-
-
-
What's next?
-
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
-
-
-
Want to get involved?
-
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
March has been a month of slow but steady progress for BeeWare.
+
+
What we've done
+
+
Progress on GUI testing in Toga is continuing. We now have 7 widgets fully tested, with another 2 in progress. As with last month's update, getting these tests passing has required wrestling a lot of fundamentals, in particular around the simulation of events such as mouse clicks. We're also discovering (and fixing) lots of corner cases in widget implementations that only surface when you're doing rigorous and repeatable testing.
+
We've made some major changes to the way GTK widgets are rendered. This change significantly reduces the amount of re-rendering that is performed by GTK, as well as resolving a number of long standing issues related to resizing widgets.
We landed the implementation of a Linux system package backend for Briefcase, which can output DEB and RPM packages. Thanks to a community contribution, we were also able to add support for Arch packages
+
We modified the locations where Briefcase outputs build artefacts. This removes some sources of bugs associated with tools not supporting spaces in filenames, and makes Briefcase's output consistent with other tools in the Python ecosystem.
+
We made significant progress on modifying Briefcase's AppImage and Flatpak backends to use Indygreg's Standalone Python, rather than BeeWare's Linux support package. Standalone Python is becoming a de facto standard for pre-compiled Python builds (especially on Linux), so it makes sense for BeeWare to converge on this common standard. This change will also significantly speed up Flatpak builds, should be more stable on AppImage, allows us to switch to manylinux base images - and it reduces the number of projects that BeeWare is responsible for maintaining. We're currently waiting on a fix to the linuxdeploy GTK plugin to be merged before we can land this change.
+
Thanks to a community contribution, we added support for PyGame to Briefcase.
+
We migrated BeeWare's CI to use the new System packaging backend on Linux. This means that CI is significantly faster, as building system packages requires a lot less processing than an AppImage.
+
We released Travertino 0.2.0. Travertino is the library that underpins Toga's Pack layout algorithm. It's been several years since we last did a Travertino release, but some recent bug fixes warranted an update.
We also made a big change to our social media strategy: we started a Mastodon account. We've wound down our Twitter usage at the end of last year; going forward, you can get your bite size BeeWare updates from @beeware@fosstodon.org.
+
+
+
What's next?
+
In terms of technical goals, April will continue our push for GUI test coverage. However, we're expecting progress to be a little slower, because of one big event - PyCon US. We'll have a booth in the community section of the conference floor; the core team are presenting 2 talks; we're presenting at the Language Summit; and we'll be at the sprints for the first 3 days. Preparing for these talks will take up a lot of our time in April, as will the event itself - so progress is likely to be a little slower than normal. If you're going to be there, come by the booth and say hi! If you'd like to help us to staff the booth - get in touch on Discord, on Mastodon, or email!
+
+
+
Want to get involved?
+
Want to get involved? Here are some open issues that would be a great place to get started with contributing to a BeeWare project. They're all relatively minor changes, but would provide a big improvement to the lives of BeeWare users:
Pick one of these tickets, drop a comment on the ticket to let others know you're looking at it, and try your hand at a PR! We have a guide on setting up a Briefcase development environment; but if you need any additional assistance or guidance, you can ask on the ticket, or join us on the BeeWare Discord server.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
-
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
-
-
What we've done
-
During July:
-
-
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
-
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
-
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
-
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
-
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
-
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
-
We've started looking into binary dependencies on iOS apps.
-
-
-
-
What's next?
-
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
Another month of important updates to the BeeWare project! This month, our focus was on packaging improvements on Linux and Windows.
+
In addition the technical progress, we welcomed Malcolm Smith (@mhsmith on Github) to the Anaconda BeeWare team! Malcolm brings his considerable experience developing and maintaining Chaquopy, a set of tools and libraries for building Android applications that use Python. Chaquopy tackles the "Python on Android" problem from the perspective of adding Python to an existing Android Studio project rather than writing apps entirely with Python; as a result, it features much tighter integration with native Android Studio tooling. One particularly interesting feature of Chaquopy is that it supports binary dependencies on Android - a key feature that BeeWare's Android tooling currently lacks. Historically, Chaquopy was a closed source tool with licenses available for open source projects; however, as a result of joining Anaconda, Malcolm has released Chaquopy as an Open Source project!
+
+
What we've done
+
During July:
+
+
We added support for Linuxdeploy plugins for Linux AppImages. These plugins are an important part of making AppImages self-contained, as many libraries need to provide the Linuxdeploy tooling hints to help find all the resources needed at runtime. Adding support for these plugins should address most of the issues we've been seeing with moving AppImages between Linux versions.
+
We added a Flatpak backend for Linux packaging. Flatpak is an alternative packaging format to AppImage which has the support of a number of large Linux distributions. For now, AppImage continues to be the default Linux packaging format, but we may change this default in the future.
+
We improved the packaging of Windows apps by adding a stub binary. We're still hunting some bugs in this stub binary, but when those are resolved, the Windows apps generated by Briefcase will present to the operating system with consistent app naming and icons. The stub binary also enables us to catch runtime problems with the app in a way that makes diagnosing app problems much easier.
+
We presented a webinar about native application development. If you weren't able to attend the webinar live, a recording is available; register here to watch.
+
We got an initial proof of concept of a Toga app running on Android using Chaquopy as a base, accessing a binary library (matplotlib), deployed with Briefcase. Over the coming weeks, we're hoping this proof of concept will evolve into major improvement to BeeWare's Android tooling.
+
We modified Briefcase to use OS-appropriate directories for caching. While the ~/.briefcase location has served us well, it isn't a location that adheres to platform-native conventions for storing app resources, so we've moved Briefcase's cache of downloads, tools and templates to a platform-appropriate location.
We've started the process of making Toga widget APIs internally consistent. While we've aimed to keep naming of widgets' attributes and handlers consistent, there are a couple of annoying inconsistencies. We've started the process of cleaning up these inconsistencies.
+
We've started looking into binary dependencies on iOS apps.
+
+
+
+
What's next?
+
In August, our major focus will be binary dependencies on mobile. This is one of the biggest missing pieces of the BeeWare story at present. Being able to utilize Chaquopy as a base gives us a huge head start on Android, so it seems likely we'll have a working solution for Android in the near future. However, on iOS, we're still at the "we don't know what we don't know" stage. It's unclear if we'll have a fully working solution by the end of the month, but we should have at least some progress to report.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
-
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
-
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
-
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
-
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
A couple of months ago, we announced that the BeeWare project had received a grant from the PSF to improve our support for Android. At that time, we issued a call for contractors to help us complete this work.
+
We're very happy to announce that we've now selected a contractor: Asheesh Laroia.
+
Asheesh is a regular speaker at Python events, where he has delved into a range of detailed and complex topics. He also impressed us with the list of unconventional engineering integration projects he's been involved with in a professional and casual capacity.
+
When asked why he applied to work with BeeWare on this contract, Asheesh said: "I use an Android phone every day, and I'm honored to be able to help implement the BeeWare vision of using Python to build first-class, native applications."
+
Asheesh will be starting work in mid December, and if all goes well, we should start seeing significant results by mid to late February. If you'd like to keep track of progress, you can follow BeeWare on Twitter; we'll also post larger updates on this blog.
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
-
-
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
-away. Email contact@beeware.org and tell us why you want to bee there!
-
— PyBee (@PyBeeWare) January 30, 2017
-
-
PyCon US 2017 is running in Portland,
-Oregon from May 17 - 25, and it's bound to be another amazing
-conference.
-
For the second year in a row, the BeeWare team
-will be on site with a booth in the Exhibit
-Hall, along
-with other Open Source projects from the Python world.
-
With this booth, we get two tickets to the conference. This includes:
-
-
access to the opening reception
-
3 days of conference talks, expo hall / job fair
-
breakfasts, breaks, lunches, and
-
swag bag
-
-
Thing is, both Russell and I have
-already registered.
-
So, we want to give you the ticket.
-
Yes, you.
-
If you can get yourself to Portland on the conference days, we want to
-give you our free ticket.
-
What do we want in return?
-
Just a little bit of your time.
-
The Bee Team will be helping to
-staff our booth, but we'd also like to see (and give!) talks, so helping
-us out by running the booth would be lovely. (Plus, and I'm sure Russell
-would agree, just helping out on the booth earns you a
-coin)
-
Plus, we'd love for you to stick around for the famous coding Sprints.
-These are held in the four days after the event, while people are still
-in town. We get coffee, lunch, and a room full of tables, chairs and
-copious amount of power points, and we code on projects. We'll be
-running a BeeWare
-sprint
-where we will be mentoring and helping first time contributors earn
-their shiny challenge
-coin
-
Does this sound like something you'd be interested in?
The tickets for PyCon US 2017 have been given away. We look forward to seeing everyone who can make it to the conference at Booth 103!
+
+
Want to to go @PyCon, can’t afford it? @PyBeeWare has 2 tickets to give
+away. Email contact@beeware.org and tell us why you want to bee there!
+
— PyBee (@PyBeeWare) January 30, 2017
+
+
PyCon US 2017 is running in Portland,
+Oregon from May 17 - 25, and it's bound to be another amazing
+conference.
+
For the second year in a row, the BeeWare team
+will be on site with a booth in the Exhibit
+Hall, along
+with other Open Source projects from the Python world.
+
With this booth, we get two tickets to the conference. This includes:
+
+
access to the opening reception
+
3 days of conference talks, expo hall / job fair
+
breakfasts, breaks, lunches, and
+
swag bag
+
+
Thing is, both Russell and I have
+already registered.
+
So, we want to give you the ticket.
+
Yes, you.
+
If you can get yourself to Portland on the conference days, we want to
+give you our free ticket.
+
What do we want in return?
+
Just a little bit of your time.
+
The Bee Team will be helping to
+staff our booth, but we'd also like to see (and give!) talks, so helping
+us out by running the booth would be lovely. (Plus, and I'm sure Russell
+would agree, just helping out on the booth earns you a
+coin)
+
Plus, we'd love for you to stick around for the famous coding Sprints.
+These are held in the four days after the event, while people are still
+in town. We get coffee, lunch, and a room full of tables, chairs and
+copious amount of power points, and we code on projects. We'll be
+running a BeeWare
+sprint
+where we will be mentoring and helping first time contributors earn
+their shiny challenge
+coin
+
Does this sound like something you'd be interested in?
- 
+ 
+ 