Log file Viewer

[00:05:02] <techalchemy> lol 'solve' debian breaking python

[00:05:02] <techalchemy> gl

[18:33:38] <gnomeza> hi #pypa. How do I get generated data files included in a wheel when PEP517 is enabled?

[18:34:40] <gnomeza> I've extended setuptools build_py command and implemented the run() method to generate some files. I think perhaps I'm supposed to extend the find_data_files() method too?

[18:45:38] <gnomeza> `pip wheel --no-deps .` also fails to find the input file, returning ENOENT for a file which should be under _vendor/pep517/<my_package>/<source_file>

[18:46:48] <gnomeza> So it seems like I also need to extend build_py to copy the source file (which is within a package) into the isolated build dir...

[18:54:24] <tos9> gnomeza: that sounds... suspicious, though I don't know what you're trying to do more broadly?

[18:54:34] <tos9> gnomeza: But the point of PEP517 is that setuptools may not be involved at all?

[18:54:52] <tos9> Or are you saying you have a PEP517 project that uses setuptools' PEP517 backend and are just trying to make that one project work here?

[19:06:37] <gnomeza> Correct. The repo contains some yaml (package data) files, an external tool generates some C headers and I'm trying to install the C headers to /usr/include...

[19:07:47] <gnomeza> In the process of surveying every project I can find on Github that imports build_py as _build_py so see if autogeneration of data files with PEP517 has been done before...

[19:12:49] <gnomeza> To be clear the tool converts the yamls to C headers. But I imagine any build_py extension taking package data and producing data files would have the same issue.

[19:14:15] <gnomeza> I'm aware that getting data_files installed is a bit of a thorny area...

[19:21:17] <gnomeza> This is a cut-down representation: https://pastebin.com/MgP50rhp

[20:44:52] <lazka> yay, pip with pep517 in Debian works again

[20:45:21] <lazka> techalchemy, do you think I should bother filing a bug in Ubuntu to get this synced into 20.04?

[20:45:40] <techalchemy> lazka, yes

[20:45:41] <techalchemy> definitely

[20:46:02] <techalchemy> can you link me to the debian issue

[20:49:05] <lazka> techalchemy, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955414, there was one more release after the one marking it as fixed though

[20:50:32] <techalchemy> thanks

[20:51:01] <lazka> I'll create a bug tomorrow, if there isn't one already.. need some sleep first :)

[20:54:18] <techalchemy> i nudged some people to see if I can find out how to report it internally

[20:59:10] <techalchemy> lazka, https://launchpad.net/ubuntu/+source/pep517 <- you can file here and i can escalate