Microsoft Feature Management for Python
Feature management provides a way to develop and expose application functionality based on features. Many applications have special requirements when a new feature is developed such as when the feature should be enabled and under what conditions. This library provides a way to define these relationships, and also integrates into common Python code patterns to make exposing these features possible.
Get Started
Quickstart: A quickstart guide is available to learn how to integrate feature flags from Azure App Configuration into your Python applications.
API Reference: This API reference details the API surface of the libraries contained within this repository.
Examples
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
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.
Documentation
With your Python virtual environment activated, install the development dependencies and build the API reference:
python -m pip install -e ".[dev]"
python -m sphinx -b html -W --keep-going -d docs/_build/doctrees docs docs/_build/html
Open docs/_build/html/index.html to preview it. The documentation version comes from the installed package.
SDK documentation should follow the Azure SDK Python Design Guidelines.
Publishing remains manual. GitHub Pages serves the gh-pages branch’s /docs folder.
Build from the current source, then replace docs/html on gh-pages with the generated docs/_build/html output.
Keep docs/index.html as the landing-page redirect and docs/.nojekyll to serve Sphinx assets.
Remove obsolete generated builds under docs/_build on that branch, then commit and push the updated documentation.
This preserves the existing /html/ API reference URLs and requires no new Actions secrets or Pages settings changes.
Trademarks
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party’s policies.