-
Notifications
You must be signed in to change notification settings - Fork 480
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
README: unclarity to do with 'pyproject.toml' #3493
Comments
Indeed, that's a convoluted sentence. Could you suggest a better alternative? |
I am afraid that I cannot. For, I do not know what the original sentence means. If you were to convey to me the various things that the sentence intends, then I could rewrite it. Yet, if you do that, then you yourself have gone part of the way already to rewriting the sentence! |
I think it means:
|
Exactly. If you think about it, that's the only interpretation that makes sense. |
bwitt's formulation is an improvement. Further improvement is possible and desirable. How then about the following?
Still: the plethora of configuration methods is making things complex. Perhaps what is really needful is a set of subheadings, one per type of file, and, under each subheading, a table presenting each type of file. Each table would have fields that include:
|
The following is very hard to parse.
The main problem is a scope-ambiguity (or at least something like that). For, what does the 'only if' clause qualify? For instance, if I have Python <3.11, can I use a .toml file at all?
The text was updated successfully, but these errors were encountered: