Generate 11.0.0-snapshot client

[roycaihw]

Updated python-base submodule, collected CHANGELOG from python-base and 11.0.0a1, and generated 11.0.0-snapshot client

Added an alias package with deprecation message for the major breaking change as #974 (comment) suggested
/cc @oz123

TODO:

• wait for test to be green (our test code in master branch still imports the deprecated package)
• collect CHANGELOG for API changes since 11.0.0a1
• install locally and test the deprecation warning behavior

[roycaihw]

diff between 11.0.0-snapshot and 11.0.0a1:

$ git diff 11.0.0-snapshot..upstream/release-11.0 --stat | grep -v "|   2 +-" | grep -v "examples\/" | grep -v "e2e_test\/"
 .travis.yml                                        |   4 -
 CHANGELOG.md                                       |  18 ++-
 README.md                                          |  36 ++++--
 RELEASE.md                                         |   8 +-
 kubernetes/README.md                               |   4 +-
 kubernetes/client/__init__.py                      |   4 +-
 kubernetes/client/api/custom_objects_api.py        |  34 ++----
 kubernetes/client/api_client.py                    |   4 +-
 kubernetes/client/apis/__init__.py                 |  11 --
 kubernetes/client/configuration.py                 |   6 +-
 kubernetes/docs/CustomObjectsApi.md                |  28 ++---
 kubernetes/utils/__init__.py                       |   1 -
 kubernetes/utils/quantity.py                       |  75 ------------
 scripts/constants.py                               |   4 +-
 scripts/rest_client_patch.diff                     |   4 +-
 scripts/swagger.json                               |  36 +-----
 scripts/update-client.sh                           |   7 ++
 setup.py                                           |   7 +-
 test-requirements.txt                              |   1 -
 tox.ini                                            |  29 ++++-

[oz123]

@roycaihw nicely done.
I thought it would be more work ...
You forgot to update the examples.
examples/pod_exec.py has one import line that needs to be updated. Can you please update this?

The warning work fine though, here is how this example output looks like when running Python with warnings enabled:

 $ python -W all  examples/pod_exec.py 
/home/oznn/Software/k8s-python/kubernetes/client/apis/__init__.py:10: DeprecationWarning: The package kubernetes.client.apis is renamed and deprecated, use kubernetes.client.api instead (please note that the trailing s was removed).
  DeprecationWarning
Response: This message goes to stderr
This message goes to stdout

Running command... echo This message goes to stdout

STDOUT: This message goes to stdout

Running command... echo "This message goes to stderr" >&2

STDERR: This message goes to stderr

Server date command returns: Tue Oct 29 20:53:47 UTC 2019
Server user is: root
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.1.108', 60596), raddr=('213.95.155.51', 6443)>
sys:1: ResourceWarning: unclosed <ssl.SSLSocket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('192.168.1.108', 60594), raddr=('213.95.155.51', 6443)>

Notice: I am actively enabling a flag in Python. Which means not all the users are going to see these warnings. Let's hope everyone has good tests :-) Pytest runs all the tests with warnings enable by default.

[roycaihw]

@oz123 Ah I didn't enable the flag so I didn't see the warning message when I tested. Thanks for verifying it! I'm curious if the log level is configurable to make the warning visible all the time.

[roycaihw]

Okay with 950df11 the deprecation warning is printed by default when the old module gets imported. @oz123 WDYT?

The warning filters are defined here.

[oz123]

@roycaihw I think it's a good idea to enable the warning per default.

[oz123]

/LGTM

[roycaihw]

@oz123 Thanks for the review!

/assign @yliaog

[drolando]

If I understand the docs correctly I think 950df11 is turning warnings on for everything. That means that if my code uses both the kubernetes client and other libraries, you're turning on the warnings also for those entirely unrelated libraries.
I didn't try this, but I think you should specify also module and make that apply only to the kubernetes module

[roycaihw]

@drolando You're right. It turns on warning for unrelated paths. E.g.

import kubernetes.client.apis
import warnings
warnings.warn(
    "another warning.",
    DeprecationWarning
)

.../kubernetes/client/apis/__init__.py:13: DeprecationWarning: The package kubernetes.client.apis is renamed and deprecated, use kubernetes.client.api instead (please note that the trailing s was removed).
  DeprecationWarning
example.py:5: DeprecationWarning: another warning.
  DeprecationWarning

I didn't try this, but I think you should specify also module and make that apply only to the kubernetes module

could you explain a bit more?

[drolando]

I was looking at https://docs.python.org/3/library/warnings.html#the-warnings-filter and it says you can pass in a module argument to limit the scope.

So you'd probably want something like warnings.filterwarnings('default', module='kubernetes')

[roycaihw]

@drolando Thanks for the suggestion. I verified that the example worked with b316493.

[roycaihw]

/hold cancel
/cc @yliaog
This pull is ready for review.

[roycaihw]

@yliaog gentle ping

[yliaog]

so you're releaseing a1 and b1 together?

[roycaihw]

no. This is copying the a1 release note from the release branch, since we didn't updated the release note in the master branch when we did a1 release.

[yliaog]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: roycaihw, yliaog

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [roycaihw,yliaog]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment