From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Tomáš Chvátal" <scarabeus@gentoo.org>
Subject: Re: [gentoo-dev] Re: Deprecation of python_version(), python_mod_exists(), python_tkinter_exists(), distutils_python_version() and distutils_python_tkinter() in EAPI <=2
Date: Fri, 5 Mar 2010 14:16:35 -0500 [thread overview]
Message-ID: <201003051416.36040.vapier@gentoo.org> (raw)
In-Reply-To: <4B8E2229.3010408@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 1642 bytes --]
On Wednesday 03 March 2010 03:47:37 Tomáš Chvátal wrote:
> Dne 3.3.2010 08:52, Ryan Hill napsal(a):
> > On Wed, 03 Mar 2010 08:52:55 +0200 Petteri Räty wrote:
> >> On 03/02/2010 08:27 PM, Arfrever Frehtes Taifersar Arahesis wrote:
> >>> Members of Gentoo Python Project have agreed to deprecate the following
> >>> functions
> >>>
> >>> in EAPI <=2:
> >>> - python_version()
> >>> - python_mod_exists()
> >>> - python_tkinter_exists()
> >>> - distutils_python_version()
> >>> - distutils_python_tkinter()
> >>>
> >>> These functions are already banned in EAPI >=3.
> >>>
> >>> 1. In this week, these functions will start printing deprecation
> >>> warnings in older EAPIs. 2. On 2010-07-01, these functions will start
> >>> calling die().
> >>>
> >>> (If any ebuilds in gentoo-x86 still call any of these functions on
> >>> 2010-07-01,
> >>>
> >>> then addition of calls to die() will be delayed.)
> >>>
> >>> 3. On 2011-01-01, these functions will be removed.
> >>
> >> Removing eclass functions like this is not allowed by current policy. If
> >> you want to do it, you should discuss about changing policy.
> >
> > ?!
> >
> > since when?
>
> Since ever.
> If you change eclass abi you need to rename it.
erm, no. being anal about eclass removal is only because of the breakage that
occurred with installed packages. functions that get used at build time are
free to be deprecated on the fly. Arfrever has a sane set of steps that
should ease transition of everything in tree. anything out of tree (overlays)
that dont adapt deserve to die anyways.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-03-05 19:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 18:27 [gentoo-dev] Deprecation of python_version(), python_mod_exists(), python_tkinter_exists(), distutils_python_version() and distutils_python_tkinter() in EAPI <=2 Arfrever Frehtes Taifersar Arahesis
2010-03-03 6:52 ` Petteri Räty
2010-03-03 7:52 ` [gentoo-dev] " Ryan Hill
2010-03-03 8:47 ` Tomáš Chvátal
2010-03-03 9:23 ` Nirbheek Chauhan
2010-03-03 11:09 ` Petteri Räty
2010-03-03 12:40 ` Ryan Hill
2010-03-03 15:55 ` Petteri Räty
2010-03-03 21:39 ` Ryan Hill
2010-03-04 7:13 ` Petteri Räty
2010-03-04 7:39 ` Ulrich Mueller
2010-03-04 7:55 ` Petteri Räty
2010-03-04 9:43 ` Ulrich Mueller
2010-03-05 3:19 ` Ryan Hill
2010-03-03 12:47 ` Ciaran McCreesh
2010-03-03 15:08 ` Duncan
2010-03-03 15:46 ` Petteri Räty
2010-03-05 9:54 ` [gentoo-dev] " Peter Hjalmarsson
2010-03-05 11:12 ` Petteri Räty
2010-03-05 20:14 ` [gentoo-dev] " Ryan Hill
2010-03-05 21:00 ` Mike Frysinger
2010-03-06 5:42 ` Petteri Räty
2010-03-05 18:40 ` Duncan
2010-03-05 19:16 ` Mike Frysinger [this message]
2010-03-03 14:02 ` [gentoo-dev] " Jeremy Olexa
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=201003051416.36040.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=scarabeus@gentoo.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