public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Campbell <zlg@gentoo.org>
To: gentoo-python <gentoo-python@lists.gentoo.org>
Subject: [gentoo-python] Re: [gentoo-dev-announce] Updates from Python team: python.eclass gone, gpyutils updates, incoming PYTHON_SINGLE_TARGET change
Date: Wed, 19 Apr 2017 18:21:36 -0700	[thread overview]
Message-ID: <f774218a-524f-334c-11ad-d238161fe551@gentoo.org> (raw)
In-Reply-To: <1492461568.12095.2.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 2325 bytes --]

On 04/17/2017 01:39 PM, Michał Górny wrote:
> Hi, everyone.
> 
> Here's a quick summary of the recent events in the Python ecosystem
> in Gentoo, and quick note of what's to come.
> 
> 
> python.eclass is gone, next things to come
> ==========================================
> 
> As you probably learned already, python.eclass and distutils.eclass were
> removed almost a month ago. This concluded a long effort of many
> developers; once again, I would like to thank all of them for their help
> and continued support.
> 
> With python.eclass gone, there are still many things to do. A few years
> ago, Arfrever has been filing bugs requesting developers to improve
> the use of python.eclass in their ebuilds -- today, we need to ask
> developers to improve their use of python-r1.
> 
> The most important tasks at the moment are:
> 
> a. working on improving test suite statuses of Python packages -- good
> and reliable test suites make all other work much easier;
> 
> b. working on porting Python packages to newer versions of CPython 3.5
> and 3.6 -- we really ought to stabilize at least 3.5 soon;
> 
> c. fixing common mistakes in using python-r1 -- missing REQUIRED_USE,
> dependencies, partial USE conditionals;
> 
> d. converting the few remaining packages that depend on python directly
> to use one of the eclasses.
> [snip]

First, thanks a lot for the announcement. It's good to see Python
support improving across the board.

I originally had a question about item (d) in the above list, but
managed to find some documentation regarding this. [1] If changes like
this need documentation, don't you think it's best to make sure that
documentation effort doesn't go to waste (i.e. it gets linked to where
relevant)? I don't intend to be rude, in fact I really appreciate the
fact it was documented. It would cut down on questions to include such a
link, however, and might even accelerate the conversion in the long run.
Just a suggestion.

Thanks again for the continued effort, and the quality documentation
that accompanies it.

[1]: https://wiki.gentoo.org/wiki/Project:Python/Python.eclass_conversion

-- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6


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

  reply	other threads:[~2017-04-20  1:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 20:39 [gentoo-python] Updates from Python team: python.eclass gone, gpyutils updates, incoming PYTHON_SINGLE_TARGET change Michał Górny
2017-04-20  1:21 ` Daniel Campbell [this message]
2017-04-20  6:28 ` grozin
2017-04-20  6:47   ` Michał Górny

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=f774218a-524f-334c-11ad-d238161fe551@gentoo.org \
    --to=zlg@gentoo.org \
    --cc=gentoo-python@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