Skip to content

Commit 1cf21fc

Browse files
Apply suggestions from code review
Co-authored-by: Malcolm Smith <[email protected]>
1 parent 4c7f568 commit 1cf21fc

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/news/buzz/2024q3-roadmap/contents.lr

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Q2 progress
1111

1212
The biggest news for the quarter is that iOS is now officially a Tier 3 supported platform in CPython. All the patches required for iOS compatibility have been landed, and a buildbot is in place; as of 3.13.0b1, CPython will build for iOS without any patching. Android support is close behind; the only missing piece is the buildbot.
1313

14-
We made some major improvements to the BeeWare tutorial, adding sections on customization of the packaged app, and handling permissions for apps. We were able to use these changes as part of well-received tutorial at PyCon US. We also ran a very successful booth and sprint at PyCon US.
14+
We made some major improvements to the BeeWare tutorial, adding sections on customization of the packaged app, and handling permissions for apps. We were able to use these changes as part of a well-received tutorial at PyCon US. We also ran a very successful booth and sprint at PyCon US.
1515

1616
We also completed a lot of improvements in Briefcase and Toga, expanding the types of apps that can be supported. Briefcase can now package console apps; and Toga now has an official API for apps that don't have menu bars, background apps, and apps that aren't governed by the lifecycle of a single "main" window. These have been the subject of long-standing feature requests (some of them almost as old as Toga itself), so it's great to be able to finally address these limitations.
1717

@@ -20,16 +20,16 @@ The one area where we weren't able to make an progress was in packaging for mobi
2020
Q3 priorities
2121
--------------
2222

23-
The highest priority for Q3 is to get ready for the Python 3.13 release in early October. This involves finalising the work on the Android buildbot so that Android is officially Tier 3; preparing Briefcase and the support packages that BeeWare supports to be ready for the 3.13 release; and doing as much work as we can on the packaging ecosystem so that package maintainers can publish wheels for iOS and Android.
23+
The highest priority for Q3 is to get ready for the Python 3.13 release in early October. This involves finalising the work on the Android buildbot so that Android is officially Tier 3; preparing Briefcase and the Python builds that BeeWare supports to be ready for the 3.13 release; and doing as much work as we can on the packaging ecosystem so that package maintainers can publish wheels for iOS and Android.
2424

2525
We'll also be attending `Kiwi PyCon <https://kiwipycon.nz>`__ in August, and attending the Python Core Team summit in September.
2626

2727
Longer term goals
2828
-----------------
2929

30-
Getting the Python ecosystem to support iOS and Android is requires a lot more than just adding patches to CPython and some related tools. There will be a lot of education and support work required to help the community adopt iOS and Android; ; and there is certain to be ongoing maintenance as Python and the platforms evolve. There's also many ways that Python support could be made even better, including the publication of official iOS and Android binaries, and potentially getting to Tier 2 (or even Tier 1) support.
30+
Getting the Python ecosystem to support iOS and Android is requires a lot more than just adding patches to CPython and some related tools. There will be a lot of education and support work required to help the community adopt iOS and Android; and there is certain to be ongoing maintenance as Python and the platforms evolve. There are also many ways that Python mobile support could be made even better, including the publication of official iOS and Android binaries, and potentially getting to Tier 2 (or even Tier 1) support.
3131

32-
There's also a lot of work that can be done to Toga to make iOS and Android compelling platforms to support. Toga is still missing some key widgets to support navigation and data organization; and even when these widgets exist, there will be a need for documentation and examples to demonstrate how to build apps for these platforms. We anticipate we'll be looking at these towards the end of the year. We also anticipate that we'll start looking more seriously at Toga's web backend, attempting to bring it to a level of support comparable to the desktop and mobile platforms.
32+
There's also a lot of work that can be done to Toga to make iOS and Android compelling platforms to develop for. Toga is still missing some key widgets to support navigation and data organization; and even when these widgets exist, there will be a need for documentation and examples to demonstrate how to build apps for these platforms. We anticipate we'll be looking at these towards the end of the year. We also anticipate that we'll start looking more seriously at Toga's web backend, attempting to bring it to a level of support comparable to the desktop and mobile platforms.
3333

3434
Summary
3535
---------

0 commit comments

Comments
 (0)