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
I just ran the example hatch-demo. When attempting to import the .whl into python, it throws an error that the package doesn't appear to be a python package: neither pyproject.toml nor setup.py is present. I find that I can force including the README.md, pyproject.toml, and LICENSE.txt, but then an error "no file src/pkg/about.py exists" results. This is from the dynamic versioning callout in the .toml file. If I use static versioning, everything works out fine. The issue appears to be that hatch changes the source tree to eliminate the "src" directory so that if the same .toml file is included in the .whl, python will fail to find about.py. How should I get around this issue?
The text was updated successfully, but these errors were encountered:
I just ran the example hatch-demo. When attempting to import the .whl into python, it throws an error that the package doesn't appear to be a python package: neither pyproject.toml nor setup.py is present. I find that I can force including the README.md, pyproject.toml, and LICENSE.txt, but then an error "no file src/pkg/about.py exists" results. This is from the dynamic versioning callout in the .toml file. If I use static versioning, everything works out fine. The issue appears to be that hatch changes the source tree to eliminate the "src" directory so that if the same .toml file is included in the .whl, python will fail to find about.py. How should I get around this issue?
The text was updated successfully, but these errors were encountered: