-
Notifications
You must be signed in to change notification settings - Fork 130
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
pytoml is deprecated. Repalce with toml #255
Comments
When I compared these some time ago, I thought pytoml seemed significantly better structured, though I've no idea if that's still true. Pip also uses pytoml at present, and is considering switching to another library called tomlkit (pypa/pip#6136 pypa/pip#6120). pytoml being unmaintained doesn't stop it working, so I'm not going to jump for any change straight away. |
Hi, just adding another voice to support sticking with whatever pip depends on, changing when pip changes, which will probably be to tomlkit. Thanks for maintaining flit, btw! |
FYI -- pip has now switched to using |
Strangely pytoml has had more maintenance than toml even after putting up the 'not maintained' flag. I feel like packaging should adopt a toml library. |
I'm personally invested enough to pick up maintenance of whichever package we all end up depending on. |
👍 for tomlkit. It is even made for packaging (same author as Poetry). |
I don't know what the best choice is for |
I chose pytoml for the same reason as @takluyver . Small, easy to understand. PyPA should adopt -> take over maintenance for a toml package. It's not like it is a fast moving or complicated standard. |
Toml seems to be used more widely, e.g., by
https://libraries.io/pypi/toml/usage vs. https://libraries.io/pypi/tomlkit/usage |
I am a mercurial user. Don't care for the most popular or "picked the name of what it's implementing first".
…On Wed, Apr 15, 2020, at 3:39 PM, Stefan Scherfke wrote:
Toml seems to be used more widely, e.g., by
* black
* coverage
* tornado
* hypothesis
* pipenv
* requests
* trio
* dynaconf
* box
https://libraries.io/pypi/toml/usage vs. https://libraries.io/pypi/tomlkit/usage
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#255 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABSZEQNUDWENAVACKCUDK3RMYEOPANCNFSM4G6OJ6HQ>.
|
FYI, pip switched to toml in the latest release. |
Popularity isn't a great argument in general, but flit's needs for a toml parser are pretty small & standard, so I'm inclined to go with both the most popular, and the one that pip uses. Although the I agree with @dholth's idea that PyPA adopt a TOML parser. I've started a discussion about it on Discourse: https://discuss.python.org/t/adopting-recommending-a-toml-parser/4068 |
Hello. Fedora maintainer here, just wanted to pitch in. We would like to drop pytoml from Fedora and apparently, flit is the only thing we have that depends on it. Looking forward to see the result of the decision here as well as the PyPA decision. |
3rd May:
TOML 0.10.1 was released on 14th May: |
Pytoml is no longer being maintained: https://github.com/avakar/pytoml
The author suggest switching to toml.
This seems to be straight forward:
tox
says: py36: commands succeeded 👍The text was updated successfully, but these errors were encountered: