Figure out how to get a release in Pypi

[kubernetes-client]

Figure out how to get a release in Pypi

[mbohlool]

I like that:

pip install kubernetes

import kubernetes
v1 = kubernetes.CoreV1Api()

[mbohlool]

Just released "kubernetes" package in Pypi.

[mbohlool]

yeah, I think we should not upload it with our personal accounts, unless there is no other way. I will figure this out. Thanks.

[mbohlool]

@lavalamp Do you know what account we should use? Or do you know who we should ask?

[lavalamp]

Good question. I will have to ask around.

[lavalamp]

@sarahnovotny This sounds like something you (or the CNCF) could figure out?

[sarahnovotny]

@mbohlool, let's create a generic K8s account (named something appropriate to the pypi forum) and use that for any kubernetes-incubator or kubernetes project. Thanks for taking this on!

[mbohlool]

I've created an account on pypi, username: kubernetes. Will release the package there when we released 1.0. Also added this to umbrella issue #25

[mbohlool]

I will start releasing 0.1.0 version and upload it to pypi. We are going to follow semver.org versioning and major version 0 means development version and things may change without notice.

[mbohlool]

Any suggestion for pypi package name?

mine:

• kubernetes
• k8s-python-client

There are a number of packages with kubernetes name in them already exists: https://pypi.python.org/pypi?%3Aaction=search&term=kubernetes&submit=search

[sarahnovotny]

i prefer

k8s-python-client or kubernetes-python-client

[mbohlool]

I like kubernetes-python-client.

[mbohlool]

@sarahnovotny python can be inferred from the context right? can we call it k8s-client or kubernetes-client? or even without dash, k8sclient?

[lavalamp]

Or even just plain 'kubernetes'?

On Mon, Nov 21, 2016 at 3:34 PM, mbohlool [email protected] wrote:

@sarahnovotny https://github.com/sarahnovotny python can be inferred
from the context right? can we call it k8s-client or kubernetes-client? or
even without dash, k8sclient?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#23 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAngllTOTBtlPzk-2eEz-fJT9M7HV798ks5rAiqAgaJpZM4K25eQ
.

[yuvipanda]

+1 to kubernetes :)

On Mon, Nov 21, 2016 at 6:11 PM, mbohlool [email protected] wrote:

I like that:

pip install kubernetes

import kubernetes
v1=kubernetes.CoreV1Api()

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#23 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB23mMjCXGFskXMZvzpFriAspo0Q2jdks5rAk9lgaJpZM4K25eQ
.

Yuvi Panda T
http://yuvi.in/blog

[danielfrg]

+1 for plain kubernetes as well :)

[mbohlool]

ok, I've send the PR for changing name to kubernetes. Now that we are on the topic of naming, there is a utility package that I put all non-generated utilities such as load config, watch class, etc. I called it k8sutil. It could be kubernetes_util, k8s_util, etc. too. Any suggestion here?

[sebgoa]

imho it should be something like:

from kubernetes import k8sclient
from kubernetes import k8sutil

don't break up the client and the util into separate pypi's

[mbohlool]

Hmm, I may need to look at python packaging again. Right now, if you look at examples, we have k8sclient and k8sutil imported directly, and I assumed if I package it, it would work the same thus I renamed k8sclient. let me look into this. The plan is not to separate these to in two packages for sure.

[mbohlool]

I've did some digging and testing. Assuming python setup.py install is the way pip install packages (that I am 99% sure it is), we can achieve both options:

1. No top level package:

import kubernetes
import k8sutil # or better name

k8sutil.load_kube_config()
v1 = kubernetes.CoreV1Api()

2. A top level package called kubernetes then rename internal packages:

from kubernetes import client    # or import kubernetes.client
from kubernetes import util        # or import kubernetes.util

util.load_kube_config()
v1 = client.CoreV1Api()

Second option looks better to me, I need to do some restructuring but it should work.