From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [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:14:33 -0600 [thread overview]
Message-ID: <20100305141433.2403abc6@gentoo.org> (raw)
In-Reply-To: 4B90E724.8040504@gentoo.org
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
On Fri, 05 Mar 2010 13:12:36 +0200
Petteri Räty <betelgeuse@gentoo.org> wrote:
> Because there is so little benefit from removing old functions. What is
> so bad about having them grouped at the bottom of the file inside a
> deprecated section?
Because then people use them. Don't ask me why. I have things I deprecated
over two years ago still being used by a dozen ebuilds bumped within the last
three months. You should be familiar with this behaviour wrt.
built_with_use. So, when I'm making changes I still have to maintain the
deprecated stuff.
If I really want to get rid of it, then I have to break it. Replace the
whole thing with a eerror like any of our deprecated eclasses. At that
point, I would rather just remove the function or eclass than curate a museum
of dead interfaces. But I suppose that's a personal quirk -- I hate having
old unused code around.
--
fonts, by design, by neglect
gcc-porting, for a fact or just for effect
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-05 20:12 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 ` Ryan Hill [this message]
2010-03-05 21:00 ` [gentoo-dev] " Mike Frysinger
2010-03-06 5:42 ` Petteri Räty
2010-03-05 18:40 ` Duncan
2010-03-05 19:16 ` Mike Frysinger
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=20100305141433.2403abc6@gentoo.org \
--to=dirtyepic@gentoo.org \
--cc=gentoo-dev@lists.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