-
Notifications
You must be signed in to change notification settings - Fork 191
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
1.0 release? #300
Comments
At this point, an rc1 release candidate for TOML is out, but v1.0.0 proper is not yet released. This library could move to attain full compliance with v1.0.0rc1 early on, then the rest would be easy. |
Oh, I didn't realise it was only a release candidate. |
https://github.com/toml-lang/toml/projects/1 is where you can track the progress to 1.0:
|
TOML 1.0 is out https://twitter.com/mojombo/status/1349133804137447425 (thanks @pradyunsg!) |
I'll reiterate my offer to comaintain this project (#267 (comment)). |
Ok, I have write access to this repository now and have triaged through the entire backlog of issues and labelled them. I still don't have access to PyPI though, so I'm not quite sure if I should invest in trying to fix the various bugs and lack of TOML 1.0 support in this library. None the less, if there's folks who want to move away from this library they can use |
@pradyunsg I'd be happy to help with what you need to get TOML 1.0 support in this library and then do a new release. |
The API seems pretty stable by now, and TOML itself has reached 1.0, so can we get a 1.0 release? It would help with adoption of PEP 518 (
pyproject.toml
) by some particularly stubborn projects. There is #134, but that was closed silently a while ago.The text was updated successfully, but these errors were encountered: