[17:23:47] <gnomeza> Is there a good way to refactor complex build_ext Extensions?
[17:24:23] <gnomeza> A package I'm working on is responsible for converting its dependencies' package_data (.ymls) to C headers using a custom preprocessor (in another package)
[17:25:23] <gnomeza> But I'm struggling to figure out how I can make this work if the package's own configuration decides how (or where) these headers are generated
[17:26:05] <gnomeza> it's all just sitting in setup.py for now
[17:28:11] <gnomeza> I thought I could forego the magic install-time yml->h and instead have the end-user call some function or script of the package (post-install) to do the generation.
[17:28:37] <gnomeza> At that point the package would be fully installed so its resources, classes, scripts, etc would all be accessible to the user
[17:41:50] <Celelibi> Where is the documentation of setuptools.setup? The details of its arguments and what they mean.
[17:57:11] <GothAlice> Celelibi: https://setuptools.readthedocs.io/en/latest/setuptools.html?highlight=setup%20tools.setup#new-and-changed-setup-keywords — that references the changes from the base/core "distutils" setup() call: https://docs.python.org/3/distutils/apiref.html#distutils.core.setup
[19:17:08] <Celelibi> I've seen the first one, but it doesn't explain cmdclass.
[20:20:08] <Celelibi> Hm. scikit-learn actually uses some numpy extension to distutils / setuptools. That's why some parts weren't documented at all.