Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 16/16] bitbake: bb: Drop deprecated functions
Date: Tue, 17 Sep 2013 10:42:12 +0100	[thread overview]
Message-ID: <1379410932.32201.97.camel@ted> (raw)
In-Reply-To: <1379368413-9808-16-git-send-email-richard.purdie@linuxfoundation.org>

On Mon, 2013-09-16 at 22:53 +0100, Richard Purdie wrote:
> These functions in the main bb module have long been deprecated
> and moved to other modules. Finally remove the compatibility links.
> 
> (Bitbake rev: ccd181c3ed4852e2b9169cf19aaf18aeacddcc18)
> 
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
>  lib/bb/__init__.py | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/lib/bb/__init__.py b/lib/bb/__init__.py
> index 018b744..8a23a0f 100644
> --- a/lib/bb/__init__.py
> +++ b/lib/bb/__init__.py
> @@ -140,6 +140,3 @@ def deprecate_import(current, modulename, fromlist, renames = None):
>  
>          setattr(sys.modules[current], newname, newobj)
>  
> -deprecate_import(__name__, "bb.fetch", ("MalformedUrl", "encodeurl", "decodeurl"))
> -deprecate_import(__name__, "bb.utils", ("mkdirhier", "movefile", "copyfile", "which"))
> -deprecate_import(__name__, "bb.utils", ["vercmp_string"], ["vercmp"])

I should be clear with this one that now isn't the ideal time to merge
this and that isn't my intention. 

It is a reminder to people that this API *will* go away soon in the 1.6
cycle though.

Cheers,

Richard




      reply	other threads:[~2013-09-17  9:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-16 21:53 [PATCH 01/16] cooker: Allow profiling of the parser in profile mode Richard Purdie
2013-09-16 21:53 ` [PATCH 02/16] data: Be explicit in data_db check Richard Purdie
2013-09-16 21:53 ` [PATCH 03/16] siggen: Use lookup cache exclusively Richard Purdie
2013-09-16 21:53 ` [PATCH 04/16] data_smart: Improve variable expansion regexp Richard Purdie
2013-09-16 21:53 ` [PATCH 05/16] data_smart: use the expand_cache in VariableParse Richard Purdie
2013-09-16 21:53 ` [PATCH 06/16] data: Use direct iteration, not keys() Richard Purdie
2013-09-16 21:53 ` [PATCH 07/16] data: Cache an list of export variables Richard Purdie
2013-09-16 21:53 ` [PATCH 08/16] data_smart: Add explict None checks Richard Purdie
2013-09-16 21:53 ` [PATCH 09/16] data_smart: Allow expansion of flags in getVarFlags Richard Purdie
2013-09-16 21:53 ` [PATCH 10/16] data_smart: Allow flags to use the expand cache Richard Purdie
2013-09-16 21:53 ` [PATCH 11/16] data_smart: Cache the fact a variable accesses another even if its unset Richard Purdie
2013-09-16 21:53 ` [PATCH 12/16] data: Optimise build_dependencies a little Richard Purdie
2013-09-16 21:53 ` [PATCH 13/16] data: Optimise flag lookup in build_dependencies Richard Purdie
2013-09-16 21:53 ` [PATCH 14/16] data: Optimise flag exclusion list handling Richard Purdie
2013-09-16 21:53 ` [PATCH 15/16] bitbake: bb.fatal: Raise a BBHandledException instead of exiting Richard Purdie
2013-09-16 21:53 ` [PATCH 16/16] bitbake: bb: Drop deprecated functions Richard Purdie
2013-09-17  9:42   ` Richard Purdie [this message]

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=1379410932.32201.97.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@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