-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Replace vendored toml
with tomli
for TOML v1.0.0 compat
#10035
Conversation
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've got a few questions/notes here myself!
You should run The CI job for vendoring runs it as well, and shows how what you've made in the patch is different from what the automation generates. |
Thanks! For reasons unknown to me, nox failed to install ERROR: No matching distribution found for vendoring>=0.3.0 But |
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.
Let's hold off on merging this until tomli stabilises. I don't think there's a hurry in vendoring this, and given the current frequency of enhancements being made to tomli's error reporting and edge case handling, it can't hurt to wait until closer to our release to update and merge 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.
One nit, otherwise LGTM.
Makes sense. At this stage the parser passes all tests by BurntSushi and iarna plus a good amount of extra tests specially crafted for cases the aforementioned test suites did not cover. So I'm fairly confident and have stopped actively searching for bugs now. That said, the parser is still brand new...
Thanks, commited! |
@hukkin Could you squash the commits in this PR, to be something like the following?
This would separate manual changes from automation-driven changes which is basically always a good idea -- that'll make it easier to manage this PR, making it easier to ensure that the individual changes are accurate. |
Just pushed an improved commit history @pradyunsg |
@pypa/pip-committers do we want this in 21.2? |
I like how that sounds! The sooner we adopt TOML 1.0, the sooner the rest of the ecosystem can start adopting it. |
Let’s do it then. I’ll merge as soon as @hukkin confirms this is good to go. |
@uranusjr This is ready to merge from my side |
Awesome! |
Closes #10034