-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uv_build Error when the folder name is capitalized #12187
Comments
It looks like we expect you to use the normalized name here. You could set: [tool.uv.build-backend]
module-name = "Transcriber" Somewhat undecided on whether this should work out of the box -- I think it probably should? What do you think @konstin? |
your solution worked, but isn't the expected to work without adding it like when using hatchling? |
It probably should, yeah. |
Match the module name to its module directory with potentially different casing. We want to support all sorts of normalization, e.g., a package may have the dist-info-normalized package name `pil_util`, but the module name `PIL_util`. We get the module either as dist-info-normalized package name, or explicitly from the user. For dist-info-normalizing a package name, the rules are lowercasing, replacing `.` with `_` and replace `-` with `_`. Since `.` and `-` are not allowed in module names, we can check whether a directory name matches our expected module name by lowercasing it. Fixes #12187
Match the module name to its module directory with potentially different casing. For example, a package may have the dist-info-normalized package name `pil_util`, but the importable module is named `PIL_util`. We get the module either as dist-info-normalized package name, or explicitly from the user. For dist-info-normalizing a package name, the rules are lowercasing, replacing `.` with `_` and replace `-` with `_`. Since `.` and `-` are not allowed in module names, we can check whether a directory name matches our expected module name by lowercasing it. Fixes #12187
Summary
when i run
and the
pyproject.toml
the code for the package is in in
src\Transcriber
terminal output
but if i changed the package folder to
src\transcriber
it worksalso this is works when and folder =
src\Transcriber
Platform
Microsoft Windows 11 Pro x86_64
Version
uv 0.6.5 (bcbcd0a 2025-03-06)
Python version
Python 3.11.10
The text was updated successfully, but these errors were encountered: