[10:55:31] <Xelnor> is there a way to tell setup.py or setup.cfg to include a whole subtree as package_data? the glob patterns seem only to apply to the basename
[11:20:30] <lazka> Xelnor, I'm using "foo/*/*.png" here so I don't think it's just the basename
[11:21:31] <Xelnor> yeah that works indeed; but you need to know the exact hierarchy. My goal is to include the (compiled) assets for a Django application, without including them in the sdist tree
[11:21:45] <Xelnor> so I only know the root of the statics tree, not each path in turn
[11:22:36] <Xelnor> I guess I'll have to override `build_py.find_data_files` :)
[11:58:54] <lazka> Xelnor, looks like it just uses glob, and glob can handle "**" since Python 3.5, so maybe try that
[12:01:24] <lazka> ah, ** only works with recursive glob, which isn't the default, never mind
[13:03:58] <toad_polo> Xelnor: Why override find files instead of writing a script to generate the list?
[13:05:09] <Xelnor> toad_polo: because I like the idea of declarative configuration in setup.cfg :)
[13:06:44] <toad_polo> So do I, but it's hardly declarative if you're overriding the build machinery.
[13:07:49] <toad_polo> By the way you may want to look into include_package_data.
[13:08:30] <toad_polo> Exactly what it does I'm not entirely clear, but I think the idea is generally that it will include stuff that's covered by your MANIFEST.in
[15:24:01] <Xelnor> yes, but files generated by the build process shoudln't be part of the MANIFEST.in, which describes what goes into a "source" distribution :)