-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[document] Mention poetry.toml #5492
Conversation
Would be really, really convenient if you could put |
I was also a one who thought it is convenient, but after reading finswimmer's comment, the current behavior seems perfectly reasonable, except that this is not documented well. |
Deploy preview for website ready! ✅ Preview Built with commit 6356cf5. |
Co-authored-by: Arun Babu Neelicattu <[email protected]>
docs/configuration.md
Outdated
{{% note %}} | ||
Your local configuration of Poetry application is stored in `poetry.toml` file, | ||
which is separate from `pyproject.toml`. | ||
You should not check-in this file into your repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not entirely true or enforced. I'd reword it to suggest it is recommended not to commit it as it may contain user specific configuration or sensitive information.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reworded!
@majiang just a gentle bump ;) This would be nice addition to our docs. |
There was no reply to my previous comment, so I'm unsure if anyone saw it. I'd like to make one more plea for changing the wording. Currently, the PR adds:
When working in a shared code base, I find it extremely useful to have a
I have a small FastAPI project which provides an example of this configuration: https://github.com/b-long/mooseblog . As I said before, the |
Hi. We ask for rewording to avoid people showing up and claiming that we are recommending something not secure. |
Co-authored-by: Bartosz Sokorski <[email protected]>
committed @Secrus 's suggestion since it is better in that we clearly warn. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
See #2937 (comment)
Pull Request Check List
Resolves: #issue-number-here