Log file Viewer

[18:22:22] <nanonyme> Does the =~ operator work in setup.py as well, btw?

[19:42:06] <dstufft> nanonyme: if you're using a new enough setuptools it should yes

[21:45:50] <nanonyme> Right

[21:57:28] <nZac> If I have a folder next to my setup.py that has package data that needs to be installed with the package, how do I tell setuptools to include it? I tried putting "graft <foldername>" in a MANIFEST.in file, but that didn't seem to work.

[22:02:00] <ronny> nZac: does that folder contain a python package and do you list it as such in setup.py?

[22:02:29] <ronny> and do you set include_package_data (might be called different, i dont recall the exact name)

[22:02:49] <nZac> ronny: That folder isn't a package with an __init__.py but it does have some python modules in it.

[22:03:11] <nZac> ... along with a bunch of other stuff

[22:07:09] <ronny> nZac: then you dont use a normal/good layout, without more knowledge of the layout novody has an idea on what you need to do

[22:07:25] <ronny> nZac: i stongly suggest to switch from a possible layout to a good layout tho

[22:08:03] <nZac> ronny: The layout is bad? Let's say I have images that I need to include with the package, where would I put them?

[22:08:45] <ronny> nZac: usual location is a folder within a python package

[22:09:37] <nZac> Ohhh... I mean, I can do that if that is what is supposed to happen. In this case it was already outside of the main package and I hoped I could convince setup to just include it with the distribution.

[22:10:13] <ronny> nZac: its easy to put stuff into a sdist, but its harder to get things to work with wheels

[22:10:47] <ronny> also its good practice not to litter site-packages, but instead to put things into your own package

[22:10:58] <nZac> What do you mean?

[22:11:17] <nZac> Ohhh, NVM I see what you are saying

[22:11:51] <nZac> It would put the folder directly into site-packages/data (or whatever the name is) instead of site-packages/my-package/data