Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Asselstine <mark.asselstine@windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] python: don't include -tests with modules
Date: Thu, 27 Jul 2017 22:39:07 +0100	[thread overview]
Message-ID: <1501191547.22282.176.camel@linuxfoundation.org> (raw)
In-Reply-To: <1500912616-8012-1-git-send-email-mark.asselstine@windriver.com>

On Mon, 2017-07-24 at 12:10 -0400, Mark Asselstine wrote:
> Although 'test' is listed in the python module list
> (https://docs.python.org/3/py-modindex.html) it is meant only to be
> used 'internally' by folks developing python itself. Per the
> documentation:
> 
>   Note The test package is meant for internal use by Python only. It
>   is documented for the benefit of the core developers of Python. Any
>   use of this package outside of Python’s standard library is
>   discouraged as code mentioned here can change or be removed without
>   notice between releases of Python.
> 
> Per the above it is best not to include this module to discourage
> folks who might not head the above warnings. Additionally this module
> is one of the largest py modules going, by dropping this unneeded
> module from the 'modules' package we can reduce overall image size,
> something which is important for many embedded deployments.
> 
> Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
> ---
>  meta/recipes-devtools/python/python-2.7-manifest.inc | 2 +-
>  meta/recipes-devtools/python/python-3.5-manifest.inc | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

As per the comments at the top of these files, the generator scripts
need to be fixed too?

Cheers,

Richard


  reply	other threads:[~2017-07-27 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 16:10 [PATCH] python: don't include -tests with modules Mark Asselstine
2017-07-27 21:39 ` Richard Purdie [this message]
2017-07-28 12:12   ` Mark Asselstine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1501191547.22282.176.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mark.asselstine@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox