Python V1 Release #522

Activity

1. federicobond commented on Jan 5, 2026

   

   federicobond

   on Jan 5, 2026

   Member

   More actions

   I think we are almost ready to ship. I've opened an issue to remove the deprecated openfeature.provider.provider module which is the only remaining deprecation we are still carrying.

   One last thing I’d like to revisit before shipping V1 is the from openfeature import api entrypoint.

   api is a very common identifier in real projects (routers/clients), so it collides with existing conventions. For example in Django Ninja (from their docs):

   from ninja import NinjaAPI
   
   api = NinjaAPI()

   If someone also does:

   from openfeature import api
   
   client = api.get_client()

   They either end up aliasing (from openfeature import api as openfeature) or, worse, accidentally shadowing one api with the other.

   The OpenTelemetry’s Python API, for example, avoids this by exporting a domain-specific module name:

   from opentelemetry import trace
   
   tracer = trace.get_tracer(__name__)

   What do you think about renaming the module to something more specific/collision-resistant (e.g. flags or feature_flags) and keep openfeature.api as a backward-compatible alias for now?

   from openfeature import feature_flags
   
   client = feature_flags.get_client()

   If this feels like bikeshedding, I’m happy to let it go. I just wanted to raise it before v1 locks it in.

   cc/ @gruebel