Skip to content
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

[feature-proposal] never mind #1364

Closed
orgua opened this issue Jan 23, 2024 · 2 comments
Closed

[feature-proposal] never mind #1364

orgua opened this issue Jan 23, 2024 · 2 comments
Assignees

Comments

@orgua
Copy link

orgua commented Jan 23, 2024

No description provided.

@Nytelife26
Copy link
Member

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?

@Nytelife26 Nytelife26 self-assigned this Feb 5, 2024
@Nytelife26
Copy link
Member

Nytelife26 commented Feb 18, 2024

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.

Then, we'll just be able to do this in the code:

import sys

if sys.version_info >= (3, 11):
    import tomllib
else:
    import tomli as tomllib

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.

@Nytelife26 Nytelife26 added this to the 1.0.0 milestone Apr 23, 2024
@orgua orgua changed the title [feature-proposal] improve config - switch to toml & more [feature-proposal] never mind May 28, 2024
@orgua orgua closed this as completed May 28, 2024
@Nytelife26 Nytelife26 removed this from the Refactoring (launch of 1.0.0) milestone May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants