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

docs: explain default of --min-py-version #231

Closed
wants to merge 1 commit into from

Conversation

Cube707
Copy link

@Cube707 Cube707 commented Mar 15, 2024

After our earlier discussion on #230 I now understood why the default is that way and why it makes sense to update require_python.

To avoid this problem in the future, I suggest to add a explanation to the README about the default behavior.

I hope this matches the conses reached on #207, where the mention of the specific default version was removed to reduce maintenance burdon

@asottile
Copy link
Owner

no thanks, you can check --help

@asottile asottile closed this Mar 15, 2024
@Cube707
Copy link
Author

Cube707 commented Mar 15, 2024

sorry for the maybe stupid question, but how does checking --help do that?

running setup-cfg-fmt --help on a v2.5.0 install results in:

usage: setup-cfg-fmt [-h] [--include-version-classifiers] [--min-py-version MIN_PY_VERSION] [--max-py-version MAX_PY_VERSION] [filenames ...]

positional arguments:
  filenames

options:
  -h, --help            show this help message and exit
  --include-version-classifiers
  --min-py-version MIN_PY_VERSION
  --max-py-version MAX_PY_VERSION

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

Successfully merging this pull request may close these issues.

2 participants