Directory Listing should not include tests in production, shown in help

[codevulture]

dir(kubernetes.config)
['ConfigException', 'builtins', 'doc', 'file', 'name', 'package', 'path', 'config_exception', 'incluster_config', 'kube_config', 'list_kube_config_contexts', 'load_incluster_config', 'load_kube_config', 'new_client_from_config']

help(kubernetes.config)
Help on package kubernetes.config in kubernetes:

NAME
kubernetes.config

FILE
/usr/local/lib/python2.7/dist-packages/kubernetes/config/init.py

DESCRIPTION
# Copyright 2016 The Kubernetes Authors.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

PACKAGE CONTENTS
config_exception
incluster_config
incluster_config_test
kube_config
kube_config_test

As general tests dir in Kubernetes module is not included in production.So i think either we can include all tests or exclude all. But please see if that is valid.

[mbohlool]

incluster_config_test and kube_config_test should definitely be excluded from final package.

[pokoli]

I'm wondering if it will be better to create a tests package that include all the tests cases there and don't include this package in the released version.

[codevulture]

@mbohlool 👍

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.