Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

If there's no objections, will finish adding tests, etc.

I think, we are open for this setting. Please also create a downstream (draft) PR that shows the usage of this setting. (You can replace the poetry-core dependency with a git dependency pointing to your branch in a temporary commit that will be dropped before merging.)

Hello @earonesty
Any updates here?
Maybe do you need help with this PR?

@earonesty apologies for getting to this sooner. Really appreciate your effort in getting this proposed. I have proposed python-poetry/poetry#10129 which will close this out unfortunately.

While I can see the value add in having this configurable in the dependency spec, I do not think this is the appropriate solution for this as things stand. By the nature of these config settings, they are not universal in most cases. A configuration that works for a user on linux machine might not work for someone on an osx machine (or vice-versa) etc.

This is why python-poetry/poetry#10129 proposes the introduction of a configuration setting instead of an addition to the pyproject.toml file.

Yes, there are some cases where it might make sense to have a "default" config for every developer (think corporate environment with uniform developer environments). For these cases, I propose that users simply commit a poetry.toml with the config to their project until we stablise the config and maybe propose a "standard" way to provide project specific configuration without compromising the ability for users to override their local and/or project local config.

Please also let me know if there are areas that the proposal falls short on for your original use case.

Once again, thank you for your contributions.