-
-
Notifications
You must be signed in to change notification settings - Fork 735
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Dec 2023 status update. #545
Conversation
Visit the preview URL for this PR (updated for commit b975ef3): https://beeware-org--pr545-dec-2023-evjiiy0e.web.app (expires Sun, 07 Jan 2024 02:44:56 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: b0da44bc067e7d9a4255c77cb2c5fce572218cec |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy New Year!
|
||
* The `first patch to CPython that explicitly mentions iOS <https://github.com/python/cpython/pull/112738>`__ has been merged. This is a relatively minor change that is required for building cross-platform binary modules; we'll start submitting more substantial patches in the new year. | ||
|
||
* `PEP738 <https://peps.python.org/pep-0738/>`__, formalizing the introduction of Android as a Tier 3 platform in CPython, has been drafted, and is `currently under discussion <https://discuss.python.org/t/pep-738-adding-android-as-a-supported-platform/40975>`__. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This returns a 404 currently... not clear how long that should be the case though...
The same URL is used a bit further down as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like whatever problem you were having, it was transient; the URL is working for me now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PEP still 404s for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh bother... Github's UI FTW. I thought you were referring to the discussion link.
And yes, the PEP can't possibly resolve (at least, not yet) because the PEP hasn't been merged. When it is merged, that's the link that will exist.
Unfortunately, I've now published the post... given that the link will be valid in a week or two, my inclination is to leave it.
What's weird is that I thought I had a link checker enabled on Lektor...
|
||
* The `ability to define platform-specific icons <https://github.com/beeware/toga/pull/2260>`__ was added to Toga. | ||
|
||
* `Toga 0.4.1 was released <https://pypi.org/project/toga/0.4.1/>`__, incorporating the features and bug fixes from the last 2 months. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might the GitHub release be a better hyperlink candidate for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I consider the PyPI release to be canonical, as that's the source of the release (including the fact that the artefact can't be modified). Honestly, I'd rather there wasn't a Github release page, but it's required for the release process, so I can live with it.
Co-authored-by: Russell Martin <[email protected]>
Just in time for the new year...
PR Checklist: