You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would approve switching from JSON to TOML, especially since the standard library for Python 3.11 upwards includes tomllib, which means we're already guaranteed future support. Should we use toml from PyPI for earlier versions?
I would approve switching from JSON to TOML, especially since the standard library for Python 3.11 upwards includes tomllib, which means we're already guaranteed future support. Should we use toml from PyPI for earlier versions?
As a follow-on to this, I found out that tomli now maintains a backport of tomllib, so they should have the same interface. Additionally, poetry (although we're not planning to keep using it for long) does support Python-dependent versions, which is convenient.
I suppose the new filename should be .proselint.toml. I'm not sure why we kept it as proselintrc in the first place, honestly, given that it isn't a command file.
advantages of toml:
per project config allows more control over lint-process. Projects like codespell or ruff demonstrate good usability:
update:
The text was updated successfully, but these errors were encountered: