python-poetry / python-poetry/install.python-poetry.org
Provide some lever for controlling installer error logging in CI environments
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 255
- Forks
- 65
- Avg merge
- 2h 48m
- Merged PRs (30d)
- 1
Description
- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the FAQ and general documentation and believe that my question is not already covered.
Feature Request
Provide some kind of environment variables to control the Poetry installer's logging. The installer script installs to a poetry-installer-error*.log file, but in CI environments this can be painful to debug. There should be some kind of lever to pull to get poetry to output the installation errors directly to stderr.
Many packages automatically detect the CI variable (standard among the CI providers from what I can tell) to automatically change configuration parameters.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the installer script and the code that writes poetry-installer-error*.log. Review how installer failures are currently reported, then check the project's existing environment-variable handling. Done means CI users have a documented way to route installer errors to stderr instead of relying only on the log file, with coverage for the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100