Description:
Both databricks-tools-core/pyproject.toml and databricks-mcp-server/pyproject.toml reference a license file that doesn't exist at the package level:
license = {file = "LICENSE.md"}
LICENSE.md only exists at the repository root, not inside either package directory. Per PEP 621, the file path is always resolved relative to the pyproject.toml location. When a user tries to install either package directly from the repo as a library dependency, Poetry enforces this strictly and fails.
Who is affected:
Users who want to use databricks-tools-core or databricks-mcp-server as a Python library dependency in their own project, installed directly from the GitHub repo. This is a valid use case for customers who want to build their own applications on top of the Databricks helpers in these packages. Users who install via the standard ai-dev-kit installer, or from PyPI, are not affected. PIP and UV seem to be less stringent and treat the missing file as a non-fatal warning.
How to reproduce:
poetry add "git+https://github.com/databricks-solutions/ai-dev-kit.git#subdirectory=databricks-tools-core"
Error:
Poetry: license file '.../databricks-tools-core/LICENSE.md' not found
Potential Fix:
Copy LICENSE.md into both databricks-tools-core/ and databricks-mcp-server/ so each publishable package has its own copy of the license file alongside its pyproject.toml.
Description:
Both databricks-tools-core/pyproject.toml and databricks-mcp-server/pyproject.toml reference a license file that doesn't exist at the package level:
license = {file = "LICENSE.md"}LICENSE.md only exists at the repository root, not inside either package directory. Per PEP 621, the file path is always resolved relative to the pyproject.toml location. When a user tries to install either package directly from the repo as a library dependency, Poetry enforces this strictly and fails.
Who is affected:
Users who want to use databricks-tools-core or databricks-mcp-server as a Python library dependency in their own project, installed directly from the GitHub repo. This is a valid use case for customers who want to build their own applications on top of the Databricks helpers in these packages. Users who install via the standard ai-dev-kit installer, or from PyPI, are not affected. PIP and UV seem to be less stringent and treat the missing file as a non-fatal warning.
How to reproduce:
poetry add "git+https://github.com/databricks-solutions/ai-dev-kit.git#subdirectory=databricks-tools-core"Error:
Poetry: license file '.../databricks-tools-core/LICENSE.md' not foundPotential Fix:
Copy LICENSE.md into both databricks-tools-core/ and databricks-mcp-server/ so each publishable package has its own copy of the license file alongside its pyproject.toml.