You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2021. It is now read-only.
I'm having an issue with including a couple of files that I explicitly mention in my pyproject.toml but that don't end up in the package_data list of the converted setup.py
After a lot of trial and error, I started looking into how dephell actually identifies the files to be included. It appears that you're making the assumption that files without an extension are to be ignored.
Would you consider adapting this behavior? As far as I know, it's not bad practice to allow for files without an extension to be packaged up.
Can someone give me some feedback? It's easy enough to create a PR that fixes this, but I suppose that there might be a reason that it was implemented like this initially?
I'm having an issue with including a couple of files that I explicitly mention in my pyproject.toml but that don't end up in the package_data list of the converted setup.py
After a lot of trial and error, I started looking into how dephell actually identifies the files to be included. It appears that you're making the assumption that files without an extension are to be ignored.
Would you consider adapting this behavior? As far as I know, it's not bad practice to allow for files without an extension to be packaged up.
dephell_discover/dephell_discover/_root.py
Line 68 in 2ca2890
The text was updated successfully, but these errors were encountered: