# Integrated Tools

> **TL;DR**
> `File | Settings | Tools | Python Integrated Tools` for Windows and Linux
>
>
>
> `CLion | Settings | Tools | Python Integrated Tools` for macOS
>
>
>
> `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `⌘ Comma` (Xcode), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (ReSharper), `⌘ Comma` (ReSharper (macOS)), `Ctrl+Alt+S` (QtCreator), `⌘ Comma` (QtCreator (macOS)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) ![](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.general.settings.svg)

Use this page to configure requirements management file, default test runner, and documentation strings treatment.

| Item | Description |
| --- | --- |
| Default test runner | Select the test run/debug configuration that CLion will suggest every time you choose `Run` on the context menu of a test case.   The possible options are:       * Unittests    * pytest    * Nosetests    * Twisted Trial    |
|  Detect tests in Jupyter Notebooks  |  Select this checkbox if you want to include Jupyter Notebook files in the scope of unit test detection.  |
| Docstring format | Select the format of the documentation strings to be recognized by CLion.   Depending on the selected docstring format, CLion will generate the stub documentation comments and render text in the [Quick Documentation](viewing-inline-documentation.html) :       * Plain: on pressing `Enter` (Windows), `⏎` (macOS), `⏎` (IntelliJ IDEA Classic (macOS)), `⏎` (macOS System Shortcuts), `Enter` (XWin), `Enter` (GNOME), `Enter` (KDE), `Enter` (Emacs), `Enter` (Sublime Text), `⏎` (Sublime Text (macOS)), `⏎` (Xcode), `Enter` (Visual Studio), `⏎` (Visual Studio (macOS)), `Enter` (ReSharper), `⏎` (ReSharper (macOS)), `Enter` (QtCreator), `⏎` (QtCreator (macOS)), `Enter` (NetBeans), `Enter` (Eclipse), `⏎` (Eclipse (macOS)) or Space after opening quotes, an empty stub is generated; quick documentation shows as plain text.    * reStructuredText: on pressing `Enter` (Windows), `⏎` (macOS), `⏎` (IntelliJ IDEA Classic (macOS)), `⏎` (macOS System Shortcuts), `Enter` (XWin), `Enter` (GNOME), `Enter` (KDE), `Enter` (Emacs), `Enter` (Sublime Text), `⏎` (Sublime Text (macOS)), `⏎` (Xcode), `Enter` (Visual Studio), `⏎` (Visual Studio (macOS)), `Enter` (ReSharper), `⏎` (ReSharper (macOS)), `Enter` (QtCreator), `⏎` (QtCreator (macOS)), `Enter` (NetBeans), `Enter` (Eclipse), `⏎` (Eclipse (macOS)) or Space after opening quotes, stub doc comment is generated according to [reStructuredText](http://docutils.sourceforge.net/rst.html) format; the quick documentation is rendered by Docutils.    * NumPy: on pressing `Enter` (Windows), `⏎` (macOS), `⏎` (IntelliJ IDEA Classic (macOS)), `⏎` (macOS System Shortcuts), `Enter` (XWin), `Enter` (GNOME), `Enter` (KDE), `Enter` (Emacs), `Enter` (Sublime Text), `⏎` (Sublime Text (macOS)), `⏎` (Xcode), `Enter` (Visual Studio), `⏎` (Visual Studio (macOS)), `Enter` (ReSharper), `⏎` (ReSharper (macOS)), `Enter` (QtCreator), `⏎` (QtCreator (macOS)), `Enter` (NetBeans), `Enter` (Eclipse), `⏎` (Eclipse (macOS)) or Space after opening quotes, stub doc comment is generated according to the [NumPy](http://sphinxcontrib-napoleon.readthedocs.org/en/latest/example_numpy.html) format; the quick documentation is rendered by [Napoleon](https://sphinxcontrib-napoleon.readthedocs.org/en/latest/) and Docutils.    * Google: on pressing `Enter` (Windows), `⏎` (macOS), `⏎` (IntelliJ IDEA Classic (macOS)), `⏎` (macOS System Shortcuts), `Enter` (XWin), `Enter` (GNOME), `Enter` (KDE), `Enter` (Emacs), `Enter` (Sublime Text), `⏎` (Sublime Text (macOS)), `⏎` (Xcode), `Enter` (Visual Studio), `⏎` (Visual Studio (macOS)), `Enter` (ReSharper), `⏎` (ReSharper (macOS)), `Enter` (QtCreator), `⏎` (QtCreator (macOS)), `Enter` (NetBeans), `Enter` (Eclipse), `⏎` (Eclipse (macOS)) or Space after opening quotes, stub doc comment is generated according to [Google](http://sphinxcontrib-napoleon.readthedocs.org/en/latest/example_google.html) format; the quick documentation is rendered by [Napoleon](https://sphinxcontrib-napoleon.readthedocs.org/en/latest/) and Docutils.     All types of docstrings feature:       * Proper generation of docstrings    * Updates after applying intention actions and quick-fixes    * Coding assistance    * Autocompletion for section headers     > **Note:** > The information provided in the docstrings is used for code insight.    |
|  Analyze Python code in docstrings | If this checkbox is selected, CLion highlights the code examples and performs syntax checks and code inspections.   If this checkbox is not selected, the code fragments inside docstrings are not analyzed.   |
|  Render external documentation for `stdlib`.  |  Enables showing documentation for standard library functions from [http://docs.python.org](http://docs.python.org) in `View \| Quick Documentation`.  |
| Sphinx working directory |    Specify the path to the folder that contains `.rst` files and the `conf.py` configuration. CLion uses it to recognize custom roles and provide accurate highlighting and rendering for Sphinx documentation.    |
| Treat `.txt` files as reStructuredText | If this checkbox is selected, the files with `.txt` extension will be highlighted same way, as the files with `.rst` extension.  |

## See also

### Reference

[Smart Keys](settings-smart-keys.html) [Run/debug configurations dialog](run-debug-configurations-dialog.html)

### External Links

[Python docstrings](http://www.python.org/dev/peps/pep-0257/) [Sphinx](https://www.sphinx-doc.org/en/master/index.html) [epydoc](http://epydoc.sourceforge.net/) [reStructuredText](http://docutils.sourceforge.net/rst.html) [Google](http://sphinxcontrib-napoleon.readthedocs.org/en/latest/example_google.html) [NumPy](http://sphinxcontrib-napoleon.readthedocs.org/en/latest/example_numpy.html) [Napoleon](https://sphinxcontrib-napoleon.readthedocs.org/en/latest/) [Defining custom roles in Sphinx](http://www.doughellmann.com/articles/how-tos/sphinx-custom-roles/index.html)