You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repo and believe that this is not a duplicate.
I have searched the documentation and believe that my question is not covered.
Feature Request
Hi,
I've looked for something like this in the documentation, and didn't find it. I'd like to have the same feature as the --no-dev flag when running poetry install, declared as an envvar.
The use case for this is for docker, where I'd like to tell the build step not to install dev dependencies when building the production image. An envvar is a trivial thing to implement in a CI setup, compared to bash my way inside the dockerfile.
The text was updated successfully, but these errors were encountered:
I would like to refer you to #2458 and this comment in particular. This looks like a valid feature request, but it most likely won't happen until after the code handling configurations (poetry.toml, poetry config, environment variables, CLI flags, etc.) is rewritten.
I'm closing this as unplanned for now -- it's tangentially related to #1132, but not the same thing. There is an intention to generally support more ergonomic defaults for different scenarios.
However, this is pretty unique -- CI is better when it's explicit instead of implicit, and I would generally assert that you're better off modifying your invocation of Poetry directly, versus complicating your environment to do things indirectly.
Without a concrete example of how this is in-scope and desirable to many users, I'm going to close this as unplanned for now.
Feature Request
Hi,
I've looked for something like this in the documentation, and didn't find it. I'd like to have the same feature as the
--no-dev
flag when runningpoetry install
, declared as an envvar.A very quick suggestion of how this could be implemented is by checking how pipenv does it with PIP_INSTALL_OPTION envvar, where command line options are passed in an env var.
The use case for this is for docker, where I'd like to tell the build step not to install dev dependencies when building the production image. An envvar is a trivial thing to implement in a CI setup, compared to bash my way inside the dockerfile.
The text was updated successfully, but these errors were encountered: