This repository contains code for the Python version of the Microsoft Bot Framework SDK, which is part of the Microsoft Bot Framework - a comprehensive framework for building enterprise-grade conversational AI experiences.
This SDK enables developers to model conversation and build sophisticated bot applications using Python. SDKs for JavaScript, .NET and Java (preview) are also available.
To get started building bots using the SDK, see the Azure Bot Service Documentation.
For more information jump to a section below.
- Build status
- Packages
- Getting started
- Getting support and providing feedback
- Contributing and our code of conduct
- Reporting security issues
| Branch | Description | Build Status | Coverage Status | Code Style |
|---|---|---|---|---|
| Main | 4.15.0 Builds |  |
 |
| Build | Released Package |
|---|---|
| botbuilder-ai |  |
| botbuilder-applicationinsights |  |
| botbuilder-azure |  |
| botbuilder-core |  |
| botbuilder-dialogs |  |
| botbuilder-schema |  |
| botframework-connector |  |
|
To get started building bots using the SDK, see the Azure Bot Service Documentation.
The Bot Framework Samples includes a rich set of samples repository.
If you want to debug an issue, would like to contribute, or understand how the Bot Builder SDK works, instructions for building and testing the SDK are below.
Python "Virtual Environments" allow Python packages to be installed in an isolated location for a particular application, rather than being installed globally, as such it is common practice to use them. Click here to learn more about creating and activating Virtual Environments in Python.
Clone a copy of the repo:
git clone https://github.com/Microsoft/botbuilder-python.gitChange to the SDK's directory:
cd botbuilder-pythonTo use a local copy of the SDK you can link to these packages with the pip -e option.
pip install -e ./libraries/botbuilder-schema
pip install -e ./libraries/botframework-connector
pip install -e ./libraries/botframework-streaming
pip install -e ./libraries/botbuilder-core
pip install -e ./libraries/botbuilder-ai
pip install -e ./libraries/botbuilder-applicationinsights
pip install -e ./libraries/botbuilder-dialogs
pip install -e ./libraries/botbuilder-azure
pip install -e ./libraries/botbuilder-integration-applicationinsights-aiohttp
pip install -e ./libraries/botbuilder-adapters-slack
pip install -e ./libraries/botbuilder-integration-aiohttp
pip install -e ./libraries/botbuilder-testingFirst execute the following command from the root level of the repo:
pip install -r ./libraries/botframework-connector/tests/requirements.txt
pip install -r ./libraries/botbuilder-core/tests/requirements.txt
pip install -r ./libraries/botbuilder-ai/tests/requirements.txtThen enter run pytest by simply typing it into your CLI:
pytestThis is the expected output:
============================= test session starts =============================
platform win32 -- Python 3.8.2, pytest-3.4.0, py-1.5.2, pluggy-0.6.0
rootdir: C:\projects\botbuilder-python, inifile:
plugins: cov-2.5.1
...Below are the various channels that are available to you for obtaining support and providing feedback. Please pay carful attention to which channel should be used for which type of content. e.g. general "how do I..." questions should be asked on Stack Overflow, Twitter or Gitter, with GitHub issues being for feature requests and bug reports.
Github issues should be used for bugs and feature requests.
Stack Overflow is a great place for getting high-quality answers. Our support team, as well as many of our community members are already on Stack Overflow providing answers to 'how-to' questions.
If you issues relates to Azure Bot Service, you can take advantage of the available Azure support options.
We use the @msbotframework account on twitter for announcements and members from the development team watch for tweets for @msbotframework.
The Gitter Channel provides a place where the Community can get together and collaborate.
We welcome contributions and suggestions. Please see our contributing guidelines for more information.
This project has adopted the Microsoft Open Source Code of Conduct.
For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
In order to create pull requests, submitted code must pass pylint and black checks. Run both tools on every file you've changed.
For more information and installation instructions, see:
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT License.