2022-10-24 21:51:15 +00:00
|
|
|
"""Configuration file for the Sphinx documentation builder."""
|
|
|
|
# Configuration file for the Sphinx documentation builder.
|
|
|
|
#
|
|
|
|
# This file only contains a selection of the most common options. For a full
|
|
|
|
# list see the documentation:
|
|
|
|
# https://www.sphinx-doc.org/en/master/usage/configuration.html
|
|
|
|
|
|
|
|
# -- Path setup --------------------------------------------------------------
|
|
|
|
|
|
|
|
# If extensions (or modules to document with autodoc) are in another directory,
|
|
|
|
# add these directories to sys.path here. If the directory is relative to the
|
|
|
|
# documentation root, use os.path.abspath to make it absolute, like shown here.
|
|
|
|
#
|
|
|
|
# import os
|
|
|
|
# import sys
|
|
|
|
# sys.path.insert(0, os.path.abspath('.'))
|
|
|
|
|
2022-12-05 01:44:40 +00:00
|
|
|
import toml
|
|
|
|
|
2023-06-16 18:52:56 +00:00
|
|
|
with open("../../pyproject.toml") as f:
|
2022-12-05 01:44:40 +00:00
|
|
|
data = toml.load(f)
|
2022-10-24 21:51:15 +00:00
|
|
|
|
|
|
|
# -- Project information -----------------------------------------------------
|
|
|
|
|
Docs refactor (#480)
Big docs refactor! Motivation is to make it easier for people to find
resources they are looking for. To accomplish this, there are now three
main sections:
- Getting Started: steps for getting started, walking through most core
functionality
- Modules: these are different modules of functionality that langchain
provides. Each part here has a "getting started", "how to", "key
concepts" and "reference" section (except in a few select cases where it
didnt easily fit).
- Use Cases: this is to separate use cases (like summarization, question
answering, evaluation, etc) from the modules, and provide a different
entry point to the code base.
There is also a full reference section, as well as extra resources
(glossary, gallery, etc)
Co-authored-by: Shreya Rajpal <ShreyaR@users.noreply.github.com>
2023-01-02 16:24:09 +00:00
|
|
|
project = "🦜🔗 LangChain"
|
2023-03-19 02:55:05 +00:00
|
|
|
copyright = "2023, Harrison Chase"
|
2022-10-24 21:51:15 +00:00
|
|
|
author = "Harrison Chase"
|
|
|
|
|
2022-12-05 01:44:40 +00:00
|
|
|
version = data["tool"]["poetry"]["version"]
|
|
|
|
release = version
|
2022-10-24 21:51:15 +00:00
|
|
|
|
Docs refactor (#480)
Big docs refactor! Motivation is to make it easier for people to find
resources they are looking for. To accomplish this, there are now three
main sections:
- Getting Started: steps for getting started, walking through most core
functionality
- Modules: these are different modules of functionality that langchain
provides. Each part here has a "getting started", "how to", "key
concepts" and "reference" section (except in a few select cases where it
didnt easily fit).
- Use Cases: this is to separate use cases (like summarization, question
answering, evaluation, etc) from the modules, and provide a different
entry point to the code base.
There is also a full reference section, as well as extra resources
(glossary, gallery, etc)
Co-authored-by: Shreya Rajpal <ShreyaR@users.noreply.github.com>
2023-01-02 16:24:09 +00:00
|
|
|
html_title = project + " " + version
|
2023-03-11 17:18:35 +00:00
|
|
|
html_last_updated_fmt = "%b %d, %Y"
|
Docs refactor (#480)
Big docs refactor! Motivation is to make it easier for people to find
resources they are looking for. To accomplish this, there are now three
main sections:
- Getting Started: steps for getting started, walking through most core
functionality
- Modules: these are different modules of functionality that langchain
provides. Each part here has a "getting started", "how to", "key
concepts" and "reference" section (except in a few select cases where it
didnt easily fit).
- Use Cases: this is to separate use cases (like summarization, question
answering, evaluation, etc) from the modules, and provide a different
entry point to the code base.
There is also a full reference section, as well as extra resources
(glossary, gallery, etc)
Co-authored-by: Shreya Rajpal <ShreyaR@users.noreply.github.com>
2023-01-02 16:24:09 +00:00
|
|
|
|
2022-10-24 21:51:15 +00:00
|
|
|
|
|
|
|
# -- General configuration ---------------------------------------------------
|
|
|
|
|
|
|
|
# Add any Sphinx extension module names here, as strings. They can be
|
|
|
|
# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
|
|
|
|
# ones.
|
|
|
|
extensions = [
|
|
|
|
"sphinx.ext.autodoc",
|
|
|
|
"sphinx.ext.autodoc.typehints",
|
|
|
|
"sphinx.ext.autosummary",
|
|
|
|
"sphinx.ext.napoleon",
|
2022-11-14 04:13:23 +00:00
|
|
|
"sphinx.ext.viewcode",
|
2022-10-25 03:24:15 +00:00
|
|
|
"sphinxcontrib.autodoc_pydantic",
|
Docs refactor (#480)
Big docs refactor! Motivation is to make it easier for people to find
resources they are looking for. To accomplish this, there are now three
main sections:
- Getting Started: steps for getting started, walking through most core
functionality
- Modules: these are different modules of functionality that langchain
provides. Each part here has a "getting started", "how to", "key
concepts" and "reference" section (except in a few select cases where it
didnt easily fit).
- Use Cases: this is to separate use cases (like summarization, question
answering, evaluation, etc) from the modules, and provide a different
entry point to the code base.
There is also a full reference section, as well as extra resources
(glossary, gallery, etc)
Co-authored-by: Shreya Rajpal <ShreyaR@users.noreply.github.com>
2023-01-02 16:24:09 +00:00
|
|
|
"myst_nb",
|
2023-03-13 04:15:07 +00:00
|
|
|
"sphinx_copybutton",
|
2022-11-14 04:13:23 +00:00
|
|
|
"sphinx_panels",
|
Docs refactor (#480)
Big docs refactor! Motivation is to make it easier for people to find
resources they are looking for. To accomplish this, there are now three
main sections:
- Getting Started: steps for getting started, walking through most core
functionality
- Modules: these are different modules of functionality that langchain
provides. Each part here has a "getting started", "how to", "key
concepts" and "reference" section (except in a few select cases where it
didnt easily fit).
- Use Cases: this is to separate use cases (like summarization, question
answering, evaluation, etc) from the modules, and provide a different
entry point to the code base.
There is also a full reference section, as well as extra resources
(glossary, gallery, etc)
Co-authored-by: Shreya Rajpal <ShreyaR@users.noreply.github.com>
2023-01-02 16:24:09 +00:00
|
|
|
"IPython.sphinxext.ipython_console_highlighting",
|
2023-06-16 18:52:56 +00:00
|
|
|
"sphinx_tabs.tabs",
|
2022-10-24 21:51:15 +00:00
|
|
|
]
|
2023-06-16 18:52:56 +00:00
|
|
|
source_suffix = [".rst"]
|
2022-11-14 04:13:23 +00:00
|
|
|
|
2022-10-25 03:24:15 +00:00
|
|
|
autodoc_pydantic_model_show_json = False
|
|
|
|
autodoc_pydantic_field_list_validators = False
|
|
|
|
autodoc_pydantic_config_members = False
|
|
|
|
autodoc_pydantic_model_show_config_summary = False
|
|
|
|
autodoc_pydantic_model_show_validator_members = False
|
2023-06-16 18:52:56 +00:00
|
|
|
autodoc_pydantic_model_show_validator_summary = False
|
2022-10-25 03:24:15 +00:00
|
|
|
autodoc_pydantic_model_show_field_summary = False
|
|
|
|
autodoc_pydantic_model_members = False
|
|
|
|
autodoc_pydantic_model_undoc_members = False
|
2023-06-16 18:52:56 +00:00
|
|
|
autodoc_pydantic_model_hide_paramlist = False
|
|
|
|
autodoc_pydantic_model_signature_prefix = "class"
|
|
|
|
autodoc_pydantic_field_signature_prefix = "attribute"
|
|
|
|
autodoc_pydantic_model_summary_list_order = "bysource"
|
|
|
|
autodoc_member_order = "bysource"
|
|
|
|
autodoc_default_options = {
|
|
|
|
"members": True,
|
|
|
|
"show-inheritance": True,
|
|
|
|
"undoc_members": True,
|
|
|
|
"inherited_members": "BaseModel",
|
|
|
|
}
|
|
|
|
autodoc_typehints = "description"
|
2022-10-24 21:51:15 +00:00
|
|
|
|
|
|
|
# Add any paths that contain templates here, relative to this directory.
|
|
|
|
templates_path = ["_templates"]
|
|
|
|
|
|
|
|
# List of patterns, relative to source directory, that match files and
|
|
|
|
# directories to ignore when looking for source files.
|
|
|
|
# This pattern also affects html_static_path and html_extra_path.
|
|
|
|
exclude_patterns = ["_build", "Thumbs.db", ".DS_Store"]
|
|
|
|
|
|
|
|
|
|
|
|
# -- Options for HTML output -------------------------------------------------
|
|
|
|
|
|
|
|
# The theme to use for HTML and HTML Help pages. See the documentation for
|
|
|
|
# a list of builtin themes.
|
|
|
|
#
|
2023-06-16 18:52:56 +00:00
|
|
|
html_theme = "sphinx_rtd_theme"
|
2022-10-24 21:51:15 +00:00
|
|
|
|
2023-01-03 18:16:59 +00:00
|
|
|
html_theme_options = {
|
|
|
|
"path_to_docs": "docs",
|
|
|
|
"repository_url": "https://github.com/hwchase17/langchain",
|
|
|
|
"use_repository_button": True,
|
2023-06-16 18:52:56 +00:00
|
|
|
# "style_nav_header_background": "white"
|
2023-01-03 18:16:59 +00:00
|
|
|
}
|
|
|
|
|
2022-11-04 15:02:21 +00:00
|
|
|
html_context = {
|
|
|
|
"display_github": True, # Integrate GitHub
|
|
|
|
"github_user": "hwchase17", # Username
|
|
|
|
"github_repo": "langchain", # Repo name
|
|
|
|
"github_version": "master", # Version
|
2023-06-16 18:52:56 +00:00
|
|
|
"conf_py_path": "/docs/api_reference", # Path in the checkout to the docs root
|
2022-11-04 15:02:21 +00:00
|
|
|
}
|
|
|
|
|
2022-10-24 21:51:15 +00:00
|
|
|
# Add any paths that contain custom static files (such as style sheets) here,
|
|
|
|
# relative to this directory. They are copied after the builtin static files,
|
|
|
|
# so a file named "default.css" will overwrite the builtin "default.css".
|
2023-01-14 15:39:29 +00:00
|
|
|
html_static_path = ["_static"]
|
|
|
|
|
|
|
|
# These paths are either relative to html_static_path
|
|
|
|
# or fully qualified paths (eg. https://...)
|
|
|
|
html_css_files = [
|
|
|
|
"css/custom.css",
|
|
|
|
]
|
2023-04-14 04:52:25 +00:00
|
|
|
|
|
|
|
html_js_files = [
|
|
|
|
"js/mendablesearch.js",
|
|
|
|
]
|
|
|
|
|
Docs refactor (#480)
Big docs refactor! Motivation is to make it easier for people to find
resources they are looking for. To accomplish this, there are now three
main sections:
- Getting Started: steps for getting started, walking through most core
functionality
- Modules: these are different modules of functionality that langchain
provides. Each part here has a "getting started", "how to", "key
concepts" and "reference" section (except in a few select cases where it
didnt easily fit).
- Use Cases: this is to separate use cases (like summarization, question
answering, evaluation, etc) from the modules, and provide a different
entry point to the code base.
There is also a full reference section, as well as extra resources
(glossary, gallery, etc)
Co-authored-by: Shreya Rajpal <ShreyaR@users.noreply.github.com>
2023-01-02 16:24:09 +00:00
|
|
|
nb_execution_mode = "off"
|
|
|
|
myst_enable_extensions = ["colon_fence"]
|