Support PEP 517 config settings

[yajo]

• 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

PEP517 declares support for something called "config settings", which allows passing arbitrary parameters to the build backend, allowing to specify custom logic for it.

Pip doesn't support it yet, but there's a proposal.

Build supports it.

Poetry should support it.

[finswimmer]

Hello @yajo,

pip, build and poetry have very different goals. Saying tool X provides function Y and so poetry should do as well, doesn't help much. Can you provide a use case / user story to show what you expect from poetry here?

fin swimmer

[yajo]

Yes, I would like to be able to produce one single pip package that, with those config settings, allows installing different portions of the repo.

For example, for OCA (odoo) addons, currently each repo has a setup folder with a specific structure that is autogenerated and allows installing addons separately.

Example: this directory should be installable with:

poetry add git+https://github.com/OCA/project.git#subdirectory=setup/project_task_personal_stage_auto_fold

(It is not AFAIK; see #755).

Instead, I'd like to be able to have a single setup.py file that generates installation scripts automatically for each addon, and makes them installable with:

poetry add git+https://github.com/OCA/project.git --config-settings addon=project_task_personal_stage_auto_fold

I'm not sure if poetry itself would serve for generating such dynamic package, but at least it should work for installing it.

[neimad1985]

@yajo I kindly think that you should stop telling people what they should do or not. No pun intended. This would prevent you from getting a stalling issue.

[yajo]

Sorry I didn't mean to offend anyone 😔

I'll close the issue so maintainers can focus on whatever they think it's better for the project.

Thanks everybody!

[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.