├── .github ├── scripts │ └── build_sdist_and_wheel.sh └── workflows │ ├── build_docs.yml │ ├── publish_docs.yml │ └── tests.yml ├── .gitignore ├── .pre-commit-config.yaml ├── LICENSE ├── README.md ├── docs ├── assets │ └── images │ │ ├── logo.png │ │ └── logo.svg ├── index.md └── reference │ ├── dispatch.md │ ├── index.md │ ├── special_tokens.md │ └── template.md ├── mkdocs.yml ├── prompts ├── __init__.py └── templates.py ├── pyproject.toml ├── setup.cfg └── tests └── test_templates.py /.github/scripts/build_sdist_and_wheel.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # Build sdist and wheel 4 | python -m pip install -U pip 5 | python -m pip install build 6 | python -m build 7 | 8 | # Check sdist install and imports 9 | mkdir -p test-sdist 10 | cd test-sdist 11 | python -m venv venv-sdist 12 | venv-sdist/bin/python -m pip install ../dist/prompts-*.tar.gz 13 | venv-sdist/bin/python -c "import prompts" 14 | cd .. 15 | 16 | # Check wheel install and imports 17 | mkdir -p test-wheel 18 | cd test-wheel 19 | python -m venv venv-wheel 20 | venv-wheel/bin/python -m pip install ../dist/prompts-*.whl 21 | venv-wheel/bin/python -c "import prompts" 22 | cd .. 23 | -------------------------------------------------------------------------------- /.github/workflows/build_docs.yml: -------------------------------------------------------------------------------- 1 | name: Build the documentation 2 | 3 | on: 4 | pull_request: 5 | branches: [master] 6 | 7 | jobs: 8 | build: 9 | name: Build 10 | runs-on: ubuntu-latest 11 | steps: 12 | - uses: actions/checkout@v4 13 | - uses: actions/setup-python@v4 14 | with: 15 | python-version: "3.10" 16 | 17 | - name: Build the documentation 18 | run: | 19 | python -m pip install --upgrade pip 20 | pip install .[docs] 21 | mkdocs build 22 | -------------------------------------------------------------------------------- /.github/workflows/publish_docs.yml: -------------------------------------------------------------------------------- 1 | name: Publish the documentation 2 | 3 | on: 4 | push: 5 | branches: 6 | - master 7 | 8 | permissions: 9 | contents: write 10 | 11 | jobs: 12 | deploy: 13 | runs-on: ubuntu-latest 14 | steps: 15 | - uses: actions/checkout@v4 16 | - uses: actions/setup-python@v4 17 | with: 18 | python-version: 3.x 19 | - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV 20 | - uses: actions/cache@v3 21 | with: 22 | key: mkdocs-material-${{ env.cache_id }} 23 | path: .cache 24 | restore-keys: | 25 | mkdocs-material- 26 | - run: | 27 | python -m pip install --upgrade pip 28 | pip install .[docs] 29 | - name: Build documentation 30 | run: | 31 | mkdocs gh-deploy --force 32 | -------------------------------------------------------------------------------- /.github/workflows/tests.yml: -------------------------------------------------------------------------------- 1 | name: Tests 2 | 3 | on: 4 | pull_request: 5 | branches: [master] 6 | push: 7 | branches: [master] 8 | 9 | jobs: 10 | style: 11 | name: Check the code style 12 | runs-on: ubuntu-latest 13 | steps: 14 | - uses: actions/checkout@v3 15 | - uses: actions/setup-python@v4 16 | with: 17 | python-version: "3.10" 18 | - uses: pre-commit/action@v3.0.0 19 | 20 | tests: 21 | name: Run the tests 22 | runs-on: ubuntu-latest 23 | strategy: 24 | matrix: 25 | python-version: ["3.8", "3.10"] 26 | steps: 27 | - uses: actions/checkout@v3 28 | - name: Set up Python ${{ matrix.python-version }} 29 | uses: actions/setup-python@v4 30 | with: 31 | python-version: ${{ matrix.python-version }} 32 | - name: Set up test environment 33 | run: | 34 | python -m pip install --upgrade pip 35 | pip install .[test] 36 | - name: Run tests 37 | run: | 38 | pytest 39 | 40 | build-wheel: 41 | name: Build Wheel and Test SDist 42 | runs-on: ubuntu-latest 43 | steps: 44 | - uses: actions/checkout@v3 45 | - name: Build SDist and Wheel 46 | run: bash ./.github/scripts/build_sdist_and_wheel.sh 47 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # pixi environments 2 | .pytest_cache 3 | *.egg-info 4 | __pycache__ 5 | _version.py 6 | .cache 7 | -------------------------------------------------------------------------------- /.pre-commit-config.yaml: -------------------------------------------------------------------------------- 1 | repos: 2 | - repo: https://github.com/pre-commit/pre-commit-hooks 3 | rev: v4.6.0 4 | hooks: 5 | - id: check-merge-conflict 6 | - id: debug-statements 7 | - id: end-of-file-fixer 8 | - id: trailing-whitespace 9 | - repo: https://github.com/pycqa/isort 10 | rev: 5.13.2 11 | hooks: 12 | - id: isort 13 | args: [--profile, black] 14 | - repo: https://github.com/asottile/pyupgrade 15 | rev: v3.16.0 16 | hooks: 17 | - id: pyupgrade 18 | args: [--py37-plus] 19 | - repo: https://github.com/pycqa/flake8 20 | rev: 7.1.0 21 | hooks: 22 | - id: flake8 23 | - repo: https://github.com/psf/black 24 | rev: 24.4.2 25 | hooks: 26 | - id: black 27 | - repo: https://github.com/pre-commit/mirrors-mypy 28 | rev: v1.11.0 29 | hooks: 30 | - id: mypy 31 | args: [--allow-redefinition] 32 | exclude: ^examples/ 33 | additional_dependencies: [types-tqdm] 34 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 |
2 | 3 | Prompts Logo 4 | 5 | [![.txt Twitter][dottxt-twitter-badge]][dottxt-twitter] 6 | 7 | [![Contributors][contributors-badge]][contributors] 8 | [![Discord][discord-badge]][discord] 9 | 10 | 11 | *A prompting library.* 12 | 13 | Made with ❤👷️ by the team at [.txt](https://dottxt.co). 14 | 15 |
16 | 17 | 18 | ## Prompt functions 19 | 20 | The `template` decorator takes a function as an argument whose docstring is a Jinja template, and returns a `Template` object: 21 | 22 | ```python 23 | from prompts import template 24 | 25 | @template 26 | def few_shots(instructions, examples, question): 27 | return """{{ instructions }} 28 | 29 | Examples 30 | -------- 31 | {% for example in examples %} 32 | Q: {{ example.question }} 33 | A: {{ example.answer }} 34 | {% endfor %} 35 | Q: {{ question}} 36 | A: """ 37 | ``` 38 | 39 | Calling the `Template` object renders the Jinja template: 40 | 41 | ```python 42 | instructions = "Please answer the following question following the examples" examples = [ 43 | {"question": "2+2=?", "answer":4}, 44 | {"question": "3+3=?", "answer":6}, 45 | ] 46 | question = "4+4 = ?" 47 | 48 | prompt = few_shots(instructions, examples, question) 49 | ``` 50 | 51 | 52 | [contributors]: https://github.com/dottxt-ai/prompts/graphs/contributors 53 | [contributors-badge]: https://img.shields.io/github/contributors/dottxt-ai/prompts?style=flat-square&logo=github&logoColor=white&color=ECEFF4 54 | [dottxt-twitter]: https://twitter.com/dottxtai 55 | [discord]: https://discord.gg/R9DSu34mGd 56 | [discord-badge]: https://img.shields.io/discord/1182316225284554793?color=81A1C1&logo=discord&logoColor=white&style=flat-square 57 | [dottxt-twitter-badge]: https://img.shields.io/twitter/follow/dottxtai?style=social 58 | -------------------------------------------------------------------------------- /docs/assets/images/logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dottxt-ai/prompts/3d2689ad7c388af3ab603aa374a51ca66d9eb915/docs/assets/images/logo.png -------------------------------------------------------------------------------- /docs/assets/images/logo.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | prompts 288 | -------------------------------------------------------------------------------- /docs/index.md: -------------------------------------------------------------------------------- 1 | # Prompts 2 | -------------------------------------------------------------------------------- /docs/reference/dispatch.md: -------------------------------------------------------------------------------- 1 | # Model-based prompt dispatching 2 | 3 | 4 | Different models often require different prompts to achieve a given task. They are, in essence, not different prompts in the sense that they are supposed to perform the same operation. In the same way we use `functools.singledispatch` to dispatch a functionality on the type of the first 5 | argument, it can be useful to dispatch the prompt on the model that is being used. 6 | 7 | `prompts` provides a way to dispatch the prompt on the model: 8 | 9 | 10 | ```python 11 | import prompts 12 | 13 | 14 | @prompts.template 15 | def a_simple_prompt(query: str): 16 | """{{ query }}""" 17 | 18 | @a_simple_prompt.register("google/gemma-2-9b") 19 | def a_simple_prompt_gemma(query: str): 20 | """{{ query }}""" 21 | ``` 22 | 23 | !!! note 24 | Choosing BOS and EOS based on the model is better achieved by using [special variables](special_tokens.md). 25 | -------------------------------------------------------------------------------- /docs/reference/index.md: -------------------------------------------------------------------------------- 1 | # Reference 2 | -------------------------------------------------------------------------------- /docs/reference/special_tokens.md: -------------------------------------------------------------------------------- 1 | # Handle special tokens 2 | 3 | Tokens that indicate the beginning of a sequence, an end of sequence, that 4 | delineate user and assistant turns in a conversation, etc. are model-specific. 5 | This means that one needs to write a new prompt each time they use a new model, 6 | only replacing these special tokens. This is error-prone and leads to duplicated 7 | work. 8 | 9 | 10 | ## Beginning and end of sequences 11 | 12 | `prompts` provides special variables in its templates that allows user to use special tokens in their prompts in a model-agnostic way: 13 | 14 | ```python 15 | import prompts 16 | 17 | 18 | @prompts.template 19 | def a_simple_prompt(query: str): 20 | """{{ bos + query + eos }}""" 21 | 22 | 23 | print(a_simple_prompt["mistralai/Mistral-7B-v0.1"]("question")) 24 | # question 25 | 26 | print(a_simple_prompt["google/gemma-2-9b"]("question")) 27 | # question 28 | ``` 29 | 30 | 31 | !!! note "Registry" 32 | 33 | The registry is currently limited to a few models. Please [open an issue](https://github.com/outlines-dev/prompts/issues) if you 34 | want to use `prompts` with a model that is not currently in the registry. 35 | 36 | 37 | ## Chat and Instruct models 38 | 39 | `prompts` also provides special variables `user`, `assistant` and `system` that are related to chat workflows, so you can design prompts with a chat format in a model-agnostic way: 40 | 41 | ```python 42 | import prompts 43 | 44 | 45 | @prompts.template 46 | def simple_prompt(favorite: str): 47 | """{{ bos + user.begin}} What is your favorite {{favorite + '? ' + user.end}} 48 | {{ assistant.begin }} 49 | """ 50 | ``` 51 | 52 | Chat templates are so idiosyncratic, however, that we recommend using the `Chat` class to format according to chat templates. 53 | -------------------------------------------------------------------------------- /docs/reference/template.md: -------------------------------------------------------------------------------- 1 | # Prompt templating 2 | 3 | Prompts provides a powerful domain-specific language to write and manage 4 | prompts, via what we call *prompt functions*. Prompt functions are Python 5 | functions that contain a template for the prompt in their docstring, and their 6 | arguments correspond to the variables used in the prompt. When called, a prompt 7 | function returns the template rendered with the values of the arguments. 8 | 9 | The aim of prompt functions is to solve several recurrent problems with prompting: 10 | 11 | 1. **Building complex prompts quickly leads to messy code.** This problem has 12 | already been solved in the web development community by using templating, so 13 | why not use it here? 14 | 2. **Composing prompts is difficult.** Why not just compose functions? 15 | 3. **Separating prompts from code.** Encapsulation in functions allows a clean 16 | separation between prompts and code. Moreover, like any function, prompt 17 | functions can be imported from other modules. 18 | 19 | Prompts uses the [Jinja templating 20 | engine](https://jinja.palletsprojects.com/en/3.1.x/) to render prompts, which 21 | allows to easily compose complex prompts. 22 | 23 | !!! warning "Prompt rendering" 24 | 25 | Prompt functions are opinionated when it comes to prompt rendering. These opinions are meant to avoid common prompting errors, but can have unintended consequences if you are doing something unusual. We advise to always print the prompt before using it. You can also [read the 26 | reference](#formatting-conventions) section if you want to know more. 27 | 28 | 29 | !!! note "Performance" 30 | 31 | Prompt templates introduce some overhead compared to standard Python functions, although the rendering time is still very reasonable. In the unlikely scenario where rendering templates are a bottleneck you can replace them with functions that use standard string manipulation. 32 | 33 | ## Your first prompt 34 | 35 | The following snippet showcases a very simple prompt. The variables between 36 | curly brackets `{{ }}` are placeholders for the values of the arguments you 37 | will pass to the prompt function. 38 | 39 | === "Code" 40 | 41 | ```python 42 | import prompts 43 | 44 | @prompts.template 45 | def greetings(name, question): 46 | return """Hello, {{ name }}! 47 | {{ question }} 48 | """ 49 | 50 | prompt = greetings("user", "How are you?") 51 | print(prompt) 52 | ``` 53 | 54 | === "Output" 55 | 56 | ```text 57 | Hello, user! 58 | How are you? 59 | ``` 60 | 61 | If a variable is missing in the function's arguments, Jinja2 will throw an `UndefinedError` exception: 62 | 63 | === "Code" 64 | 65 | ```python 66 | import prompts 67 | 68 | @prompts.template 69 | def greetings(name): 70 | return """Hello, {{ surname }}!""" 71 | 72 | prompt = greetings("user") 73 | ``` 74 | 75 | === "Output" 76 | 77 | ```text 78 | Traceback (most recent call last): 79 | File "", line 9, in 80 | File "/home/remi/projects/normal/prompts/prompts.templates.py", line 38, in __call__ 81 | return render(self.template, **bound_arguments.arguments) 82 | File "/home/remi/projects/normal/prompts/prompts.templates.py", line 213, in render 83 | return jinja_template.render(**values) 84 | File "/home/remi/micromamba/envs/prompts/lib/python3.9/site-packages/jinja2/environment.py", line 1301, in render 85 | self.environment.handle_exception() 86 | File "/home/remi/micromamba/envs/prompts/lib/python3.9/site-packages/jinja2/environment.py", line 936, in handle_exception 87 | raise rewrite_traceback_stack(source=source) 88 | File "