-
Notifications
You must be signed in to change notification settings - Fork 17
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
docs: prepare for 0.9.0b4 #163
Conversation
Signed-off-by: Henry Schreiner <[email protected]>
@frostming, @dnicolodi, @pradyunsg, and myself, as backend maintainers: I'm planning to do another beta release on Friday with the metadata changes. I might tackle multi-error reporting (but probably not), otherwise, that will likely end the development cycle for this release. Once we've verified that it works (and I plan to try adding PEP 639 support for scikit-build-core using the beta), we should be ready for a full release, maybe next week. I can roll back any of the changes if needed before then. Most notably, it's now an attribute error to set a value that's not dynamic after you've loaded a pyproject.toml, but if that's an issue for any of the backends, we can make it a warning instead, for instance. |
Also, if any of you have a use for #128, we could add that, I just don't see a way to use it at the moment; it would be useful in the internals, but we lose static typing by wrapping the dict access. It's not useful as the type of |
I haven't seen anything that may be problematic for meson-python in the merged PRs. However, I'll be traveling and it is likely that I'll not be able to integrate support for metadata 2.4 or to do integration tests for the next two weeks. |
I don't think there's a rush, unless another backend (that doesn't embed it) needs it quickly. And some people are testing with |
FYI, this is stuck with:
I think PyPI might be at fault here. |
Manually uploaded for now. We can drop |
After #162, so backends can test the dynamic metadata changes.