Deprecate langhchain community ucfunctiontoolkit in favor for databricks_langchain

[sunishsheth2009]

Thank you for contributing to LangChain!

• PR title: "package: description"

  • Where "package" is whichever of langchain, community, core, etc. is being modified. Use "docs: ..." for purely docs changes, "infra: ..." for CI changes.
  • Example: "community: add foobar LLM"

• PR message: Delete this entire checklist and replace with

  • Description: a description of the change
  • Issue: the issue # it fixes, if applicable
  • Dependencies: any dependencies required for this change
  • Twitter handle: if your PR gets announced, and you'd like a mention, we'll gladly shout you out!

• Add tests and docs: If you're adding a new integration, please include

  1. a test for the integration, preferably unit tests that do not rely on network access,
  2. an example notebook showing its use. It lives in docs/docs/integrations directory.

• Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

Additional guidelines:

• Make sure optional dependencies are imported within a function.
• Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests.
• Most PRs should not touch more than one package.
• Changes should be backwards compatible.
• If you are adding something to community, do not re-import it in langchain.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
langchain	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 12, 2025 5:52pm

[serena-ruan]

Can we use unitycatalog-langchain package? databricks_langchain.uc_ai imports from it and it doesn't seem needed to rely on another package (databricks-langchain) here

[sunishsheth2009]

According to Eric, we wanted all the imports to be from one place so its easier for users to just install and know about 1 package. That is why we re-exported from databricks-ai-bridge package. So I guess documenting only one package makes sense. What do you think?

[BenWilson2]

+1 to the direction of a single package interface. In the backend, we're using unitycatalog-langchain for the toolkit implementation. Having everything all go through a unified namespace of databricks.ai makes a ton of sense to me.

[serena-ruan]

After switching to unitycatalog-langchain package it's all good!