Poetry should provide a way to move the configuration easily

[hughperkins]

• 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

Poetry should provide an option to move the configuration to the new location, without having to google around.
couple of options:

• ask 'Do you want me to move this for you? Y/n' , or
• have a command like poetry self config upgrade, or poetry self move-config or similar.

(this relates to the 'closed' issue #6854, which asks how to move the configuration. This new issue asserts that poetry should provide a way to avoid having to read through that loooonnnggg thread....)

[dimbleby]

not convinced this is worthwhile, especially now that this has been settled for several months - most everyone who should have moved their config has already done so by now.

also I'm not honestly sure what the confusion is. The message says "found configuration files <here>, consider moving them <there>" - is it not clear that the action to take is simply to move the configuration files from here to there?

suggest that if this is indeed not obvious then a more cost-effective approach is just to improve that message

I'm guessing you're not intending to submit a merge request for the thing that you've asked for, but perhaps you could manage an improved message?

[hughperkins]

I mean, I already moved my config, after reading through that long thread...

I suppose you can make the argument that anyone who installed the old version of poetry most likely by now has already decided what they think about poetry, and isn't someone who will just walk off on a whim...

[dimbleby]

If you don't care about this enough to do anything about it then I expect nor does anyone else - might as well close it.

[hughperkins]

Alright. Go ahead...

…

On Wed, Dec 27, 2023, at 7:21 PM, David Hotham wrote: If you don't care about this enough to do anything about it then I expect nor does anyone else - might as well close it. — Reply to this email directly, view it on GitHub <#8818 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA6FKD47YD7FXLDDPAPWP3YLS3SBAVCNFSM6AAAAABBBMU2H6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQG4YTAMZZHA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[dimbleby]

You have the power to close this, I don't

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.