Skip to content

Add option to prevent poetry from touching pyproject.toml #10554

@acampove

Description

@acampove

Issue Kind

Brand new capability

Description

Hi,

I see that poetry does things like:

  -rx_common                   = { git = 'ssh://git@gitlab.cern.ch:7999/rx_run3/rx_common.git'    , optional = true, branch = 'master'}                                              
  -ap_utilities                = { git = 'ssh://git@gitlab.cern.ch:7999/rx_run3/ap_utilities.git' , optional = true, branch = 'master'}                                              
  -data-manipulation-utilities = { git = 'ssh://git@gitlab.cern.ch:7999/rx_run3/dmu.git'          , optional = true, branch = 'master'}                                              
  +rx_common                   = { git = 'ssh://git@gitlab.cern.ch:7999/rx_run3/rx_common.git',     optional = true, branch = 'master'}                                              
  +ap_utilities                = { git = 'ssh://git@gitlab.cern.ch:7999/rx_run3/ap_utilities.git',  optional = true, branch = 'master'}                                              
  +data-manipulation-utilities = { git = 'ssh://git@gitlab.cern.ch:7999/rx_run3/dmu.git',           optional = true, branch = 'master'} 

i.e. it normalizes my config and it seems that there is no way to turn this behavior off. Could you please add something like that? I deally something that we could put in the .config/poetry.ini.

Cheers

Impact

This is an undexpected behavior and tools should not go ahead and do stuff that was not explicitly requested by the user.

Workarounds

I cannot think of any.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureFeature requests/implementationsstatus/triageThis issue needs to be triaged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions