public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New eclass for Python
Date: Wed, 29 Feb 2012 08:49:38 +0100	[thread overview]
Message-ID: <4F4DD892.10707@gentoo.org> (raw)
In-Reply-To: <4F4D4380.9070909@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

On 2/28/12 10:13 PM, Krzysztof Pawlik wrote:
> Highlights:
>  - <400 lines of code including documentation
>  - should work for >95% of packages (my educated guess)
>  - did I mention it's *SIMPLE*?
>  - easy to maintain & read so it's also easy to use

This is awesome! Compare that to over 3000 LOC of python.eclass. :)

> Important thing: I'm not aiming at having 100% functionality of current
> python.eclass+distutils.eclass in the new one, I think that simplicity is more
> important that supporting every possible, obscure case that's out there.

Exactly.

> If there are no objections then during the weekend (March 3, 4) I will add this
> to portage (after finishing remaining TODO items, PyPy requires 4G of RAM(!!)).

I second this so much (didn't review the eclass in detail, but it's
obviously better than python.eclass).

What's the plan to retire python.eclass?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

  parent reply	other threads:[~2012-02-29  7:50 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 21:13 [gentoo-dev] New eclass for Python Krzysztof Pawlik
2012-02-29  3:21 ` Sergei Trofimovich
2012-02-29 17:34   ` Krzysztof Pawlik
2012-02-29  5:13 ` [gentoo-dev] Re: [gentoo-python] " Mike Gilbert
2012-02-29 17:35   ` Krzysztof Pawlik
2012-02-29  7:49 ` "Paweł Hajdan, Jr." [this message]
2012-02-29 17:38   ` [gentoo-dev] " Krzysztof Pawlik
2012-02-29 18:03     ` Jeroen Roovers
2012-02-29  8:11 ` [gentoo-dev] Re: [gentoo-python] " Dirkjan Ochtman
2012-02-29 17:39   ` Krzysztof Pawlik
2012-02-29 18:39     ` Mike Gilbert
2012-02-29  8:17 ` [gentoo-dev] " Fabian Groffen
2012-02-29 17:34   ` Krzysztof Pawlik
2012-02-29 19:51 ` Alexandre Rostovtsev
2012-02-29 20:24   ` Krzysztof Pawlik
2012-02-29 21:08     ` Andreas K. Huettel
2012-02-29 21:19       ` Krzysztof Pawlik
2012-02-29 21:57     ` Alexandre Rostovtsev
2012-03-01 18:42       ` Krzysztof Pawlik
2012-03-03  7:59 ` [gentoo-dev] Re: [gentoo-python] " Arfrever Frehtes Taifersar Arahesis
2012-03-03  8:18   ` Zac Medico
2012-03-25 18:56 ` [gentoo-dev] " Krzysztof Pawlik
2012-03-25 19:08   ` Luca Barbato
2012-03-26  7:20   ` justin
2012-03-26 16:11     ` Krzysztof Pawlik
2012-03-26 16:23       ` Krzysztof Pawlik
2012-04-04  8:50         ` Corentin Chary
2012-04-04 14:22           ` Mike Gilbert
2012-04-04 14:29             ` Corentin Chary
2012-04-04 14:41           ` Mike Gilbert
2012-04-05  0:07             ` Brian Harring
2012-04-05  0:36               ` Mike Gilbert
2012-04-05  0:45                 ` Brian Harring
2012-03-26  7:21   ` justin
2012-03-26 16:02     ` Krzysztof Pawlik

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=4F4DD892.10707@gentoo.org \
    --to=phajdan.jr@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