What happened (please include outputs or screenshots):
Installing kubernetes@36.0.0 overwrites the existing installation of kubernetes-asyncio
What you expected to happen:
With the inclusion of an async version of the client in 36.0.0, I expected the client to be made available as a submodule, e.g. at kubernetes.kubernetes_asyncio. Instead, when installed after kubernetes-asyncio it overwrites some files from kubernetes-asyncio, causing various errors (the same can happen in reverse as well, where installing kubernetes and then kubernetes-asyncio can cause errors).
How to reproduce it (as minimally and precisely as possible):
Install kubernetes-asyncio and then kubernetes with pip or another python package manager
Anything else we need to know?:
I'm not sure if there's planned coordination between the asyncio client included in this repo and the one at https://github.com/tomplus/kubernetes_asyncio, but it seems very odd to me that this one would overwrite files in the other's installation. If kubernetes-asyncio was not already an existing package on pypi this would be more understandable, but currently it's not mentioned on the changelog that this installs to kubernetes_asyncio (it is on the readme as of #2548, but not in the changelog for v36.0.0).
Environment:
- Kubernetes version (
kubectl version)
- OS (e.g., MacOS 10.13.6):
- macOS 15.7.5 (24G624) and debian 13 slim (via
docker.io/library/python:3.12-slim)
- Python version (
python --version)
- Python client version (
pip list | grep kubernetes)
-
kubernetes 36.0.0
kubernetes-asyncio 35.0.1
What happened (please include outputs or screenshots):
Installing
kubernetes@36.0.0 overwrites the existing installation ofkubernetes-asyncioWhat you expected to happen:
With the inclusion of an async version of the client in 36.0.0, I expected the client to be made available as a submodule, e.g. at
kubernetes.kubernetes_asyncio. Instead, when installed afterkubernetes-asyncioit overwrites some files fromkubernetes-asyncio, causing various errors (the same can happen in reverse as well, where installingkubernetesand thenkubernetes-asynciocan cause errors).How to reproduce it (as minimally and precisely as possible):
Install
kubernetes-asyncioand thenkuberneteswith pip or another python package managerAnything else we need to know?:
I'm not sure if there's planned coordination between the asyncio client included in this repo and the one at https://github.com/tomplus/kubernetes_asyncio, but it seems very odd to me that this one would overwrite files in the other's installation. If
kubernetes-asynciowas not already an existing package on pypi this would be more understandable, but currently it's not mentioned on the changelog that this installs tokubernetes_asyncio(it is on the readme as of #2548, but not in the changelog for v36.0.0).Environment:
kubectl version)Client Version: v1.36.0docker.io/library/python:3.12-slim)python --version)pip list | grep kubernetes)