# PEP 660 and setuptools

**URL:** <https://discuss.python.org/t/pep-660-and-setuptools/14855>\
**Category:** Packaging\
**Created:** [April 5, 2022, 6:46pm UTC](https://discuss.python.org/t/pep-660-and-setuptools/14855 "2022-04-05T18:46:22Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![pf\_moore](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pf_moore/32/35_2.png) [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Post date:** [April 29, 2022, 4:50pm UTC](https://discuss.python.org/t/pep-660-and-setuptools/14855/21 "2022-04-29T16:50:28Z")

</div>

> [@pf\_moore](#):
>
> OK, so what I’ll do is:
> 
> 1. pip will collect config\_settings as with any other option (including the possibility of per-requirement overrides from a requirements file).
> 2. pip will supply the config settings to every backend hook call.
> 3. I’ll dump the problem of handling this behaviour on backends 🙂 I did a quick check of the flit and poetry source code, and both seem to ignore the config\_settings parameter altogether, so I don’t believe they will have a problem here. Hopefully, the same will be true of other backends.

OK, the PR for this has just landed in pip, and should be in the next release. Have fun with it 🙂

[Previous page](https://discuss.python.org/t/pep-660-and-setuptools/14855.md?page=1)