Merge pull request #290604 from mrm9084/PythonFMRemovePreview

Python fm remove preview

Author: prmerger-automator[bot]

articles/azure-app-configuration/feature-management-python-reference.md

@@ -9,24 +9,12 @@ ms.service: azure-app-configuration
 ms.devlang: python
 ms.custom: devx-track-python
 ms.topic: tutorial
-ms.date: 09/10/2024
-zone_pivot_groups: feature-management
+ms.date: 11/15/2024
 #Customer intent: I want to control feature availability in my app by using the Feature Management library.
 ---
 
 # Python feature management
 
-:::zone target="docs" pivot="stable-version"
-
-[![Feature Management](https://img.shields.io/pypi/v/FeatureManagement?color=blue)](https://pypi.org/project/FeatureManagement/)<br>
-:::zone-end
-
-:::zone target="docs" pivot="preview-version"
-
-[![Feature Management](https://img.shields.io/pypi/v/FeatureManagement/2.0.0b2?color=blue)](https://pypi.org/project/FeatureManagement/2.0.0b2/)<br>
-
-:::zone-end
-
 Python feature management library provides a way to develop and expose application functionality based on feature flags. Once a new feature is developed, many applications have special requirements, 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.
 
 Feature flags provide a way for Python applications to turn features on or off dynamically. Developers can use feature flags in simple use cases like conditional statements.
@@ -313,8 +301,6 @@ When defining an audience, users and groups can be excluded from the audience. E
 
 In the above example, the feature is enabled for users named `Jeff` and `Alicia`. It's also enabled for users in the group named `Ring0`. However, if the user is named `Mark`, the feature is disabled, regardless of if they are in the group `Ring0` or not. Exclusions take priority over the rest of the targeting filter.
 
-:::zone target="docs" pivot="preview-version"
-
 ## Variants
 
 When new features are added to an application, there may come a time when a feature has multiple different proposed design options. A common solution for deciding on a design is some form of A/B testing. A/B testing involves providing a different version of the feature to different segments of the user base and choosing a version based on user interaction. In this library, this functionality is enabled by representing different configurations of a feature with variants.
@@ -602,8 +588,6 @@ When a feature flag is evaluated and telemetry is enabled, the feature manager c
 | `Variant` | The assigned variant. |
 | `VariantAssignmentReason` | The reason why the variant is assigned. |
 
-:::zone-end
-
 ## Next steps
 
 To learn how to use feature flags in your applications, continue to the following quickstarts.