mirror of https://github.com/hwchase17/langchain.git synced 2026-04-04 03:14:33 +00:00

Files

Mason Daugherty faadc1f3ce ci: suppress pytest streaming output in CI (#36092 )

Reduce CI log noise by suppressing pytest's per-test dot/verbose
streaming output. The `_test.yml` workflow now passes `PYTEST_EXTRA=-q`
to `make test`, which overrides the default verbosity with quiet mode —
failures still print in full, but the thousands of `.......` progress
lines are gone. Local `make test` is unaffected since `PYTEST_EXTRA`
defaults empty.

## Changes
- Add `PYTEST_EXTRA ?=` variable to all 21 package Makefiles and inject
it into each `test` target's pytest invocation
- Pass `PYTEST_EXTRA=-q` in `_test.yml` for both the main test step and
the min-version retest step

2026-03-18 21:24:47 -04:00

langchain_text_splitters

ci: avoid unnecessary dep installs in lint targets (#36046 )

2026-03-17 21:23:29 -04:00

scripts

ci: avoid unnecessary dep installs in lint targets (#36046 )

2026-03-17 21:23:29 -04:00

tests

fix(text-splitters): prevent JSFrameworkTextSplitter from mutating self._separators on each split_text() call (#35316 )

2026-02-18 17:51:42 -05:00

extended_testing_deps.txt

fix: support python 3.14 in various projects (#33575 )

2025-10-17 11:06:23 -04:00

Makefile

ci: suppress pytest streaming output in CI (#36092 )

2026-03-18 21:24:47 -04:00

pyproject.toml

ci: avoid unnecessary dep installs in lint targets (#36046 )

2026-03-17 21:23:29 -04:00

README.md

chore: update twitter URLs (#34736 )

2026-01-13 01:54:11 -05:00

uv.lock

chore: bump orjson from 3.11.5 to 3.11.6 in /libs/text-splitters (#35856 )

2026-03-17 00:03:35 -04:00

README.md

🦜✂️ LangChain Text Splitters

Looking for the JS/TS version? Check out LangChain.js.

Quick Install

pip install 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.