This month has seen BeeWare reach one major milestone, almost reach a second, as well as landing several smaller improvements.

What we've done

What's next?

The bulk of May will be taken up by preparing for and attending PyCon US. We're presenting a talk and a tutorial; we're also presenting at the Language Summit, we will have a booth in the community section of the Expo Hall, and we'll be there for the first 3 days of the sprints. If you're coming to Pittsburgh and you'd like to attend that tutorial session, ticket sales are open!. We're also hoping that we'll be able to wrap up the work on Android support in CPython, and start work on supporting command line applications in Briefcase.

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:

  1. Update the Toga testbed test suite to use Pixel 7 Pro device sizes
  2. Filter out a message generated after Xcode updates
  3. Add the ability to configure the ABIs built by an Android project
  4. Rationalise the application of adhoc signing on macOS
  5. Add support for custom PyPI repositories
  6. Document how to debug an application in popular IDEs
  7. Correctly handle incomplete project deletions
  8. Add an option to select the Android base image when creating new emulators
  9. Print notarisation log failures when building macOS apps
  10. Add an API to replace a child of a widget
  11. Add an API to entirely replace the style of a widget
  12. Add the ability to define content when creating a window

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.

Poprzedni wpis
2024Q2 Roadmap