Mason Daugherty
9cd9684136
`langchain-core` and a few other packages under `libs/` build their PyPI
sdists without a LICENSE file, so downstream redistributors have to
supply their own copy (the conda-forge `langchain-core` feedstock, for
example, keeps a manual `recipe/LICENSE` as a workaround).
Packages like `langchain-classic` and `langchain-anthropic` already ship
the license correctly because they have a `LICENSE` file in the package
directory that hatchling picks up by default. This brings the remaining
packages in line with that pattern by copying the repo-root MIT
`LICENSE` (verified byte-identical to the existing
`libs/langchain/LICENSE`) into the four package directories that lacked
one:
- `langchain-core`
- `langchain-model-profiles`
- `langchain-tests` (standard-tests)
- `langchain-text-splitters`
No `pyproject.toml` or build-config changes were needed — hatchling
includes a root-level `LICENSE` in the sdist automatically once the file
exists. All other package dirs (both `langchain` packages and every
`libs/partners/*`) already have one and were left untouched.
Verified by building each sdist with `uv build --sdist` and confirming
the file is in the tarball:
- `langchain_core-1.5.3.tar.gz` → `langchain_core-1.5.3/LICENSE`
- `langchain_model_profiles-0.0.6.tar.gz` →
`langchain_model_profiles-0.0.6/LICENSE`
- `langchain_tests-1.1.9.tar.gz` → `langchain_tests-1.1.9/LICENSE`
- `langchain_text_splitters-1.1.2.tar.gz` →
`langchain_text_splitters-1.1.2/LICENSE`
## Release note
The PyPI sdists for `langchain-core`, `langchain-model-profiles`,
`langchain-tests`, and `langchain-text-splitters` now include the MIT
`LICENSE` file.
---
🤖 This description was written with assistance from an AI agent.
🦜✂️ LangChain Text Splitters
Looking for the JS/TS version? Check out LangChain.js.
Quick Install
uv add langchain-text-splitters
🤔 What is this?
LangChain Text Splitters contains utilities for splitting into chunks a wide variety of text documents.
📖 Documentation
For full documentation, see the API reference.
📕 Releases & Versioning
See our Releases and Versioning policies.
We encourage pinning your version to a specific version in order to avoid breaking your CI when we publish new tests. We recommend upgrading to the latest version periodically to make sure you have the latest tests.
Not pinning your version will ensure you always have the latest tests, but it may also break your CI if we introduce tests that your integration doesn't pass.
💁 Contributing
As an open-source project in a rapidly developing field, we are extremely open to contributions, whether it be in the form of a new feature, improved infrastructure, or better documentation.
For detailed information on how to contribute, see the Contributing Guide.
Resources
- LangChain Academy — comprehensive, free courses on LangChain libraries and products, made by the LangChain team
- Code of Conduct — community guidelines and standards