From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] did python-r1 improve user experience?
Date: Sun, 27 Oct 2013 15:53:56 -0400 [thread overview]
Message-ID: <CAJ0EP41W1a4KciBcc8jq9BdNdoNKDCawzsgh92qJy0tEkQWMMQ@mail.gmail.com> (raw)
In-Reply-To: <526C8B62.9040905@iinet.net.au>
On Sat, Oct 26, 2013 at 11:41 PM, William Kenworthy <billk@iinet.net.au> wrote:
> On 27/10/13 09:30, Mike Gilbert wrote:
>> On Wed, Oct 23, 2013 at 9:13 AM, hasufell <hasufell@gentoo.org> wrote:
>>> Since I maintain blender I have come across quite a few frustrated
>>> users already: https://bugs.gentoo.org/show_bug.cgi?id=488976#c7
>>>
>>> I am not sure myself. On one hand we don't need python-updater anymore
>>> and have very tight dependencies that ensure that all needed modules
>>> are always available for the desired implementation.
>>>
>>> On the other hand it seems to give a lot of users trouble with
>>> blockers, general configuration and mass-updates on things like
>>> removing python:2.5.
>>>
>>> What are your opinions? Did it improve user experience? What could be
>>> improved?
>>
> ...
>
> The python user experience is less than overwhelming for a user.
>
> 1. if python-update is no longer needed (first I have heard of this) why
> is it still rebuilding many packages after an upgrade ...
>
To clarify: python-updater will no longer be needed at some point in
the future when we are no longer using the old python.eclass.
> 2. I have python 2.7 installed and python 3.x is being asked to be
> installed ... isnt that enough? - shorely it can work out what it needs
> from whats been asked for/removed and whats already on the system ...
> instead we need to add these cryptic, poorly explained lines that one
> only finds out from emails etc. The elog message for the one exception
> asks that the line be added to make.conf without telling the user what
> happens if he upgrades later (as it lists specific versions) or makes
> changes - does that line have any effect, especially if he makes a
> mistake (which I did and I am not sure what it did in the background)?
>
Making things "just work" is complex when trying to juggle 6 or more
supported versions/implementations of python.
We have tried to explain the magic make.conf lines in the Python user guide.
https://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml
We also try to make sure that most users never have to touch
PYTHON_TARGETS, etc; the default values provided by your profile are
set up to allow *stable* python2.7 and python3.2 to work properly.
~arch users are expected to read the docs. ^_^
next prev parent reply other threads:[~2013-10-27 19:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 13:13 [gentoo-user] did python-r1 improve user experience? hasufell
2013-10-27 1:30 ` Mike Gilbert
2013-10-27 2:18 ` Walter Dnes
2013-10-27 2:22 ` Bruce Hill
2013-10-27 2:48 ` Mike Gilbert
2013-10-27 3:41 ` William Kenworthy
2013-10-27 19:53 ` Mike Gilbert [this message]
2013-11-01 2:11 ` gottlieb
2013-11-01 13:41 ` gottlieb
2013-11-01 14:01 ` Alan McKinnon
2013-11-01 15:43 ` gottlieb
2013-11-01 20:17 ` Alan McKinnon
2013-11-01 21:56 ` gottlieb
2013-11-02 1:22 ` Alan McKinnon
2013-11-01 20:30 ` Bruce Hill
2013-10-27 12:03 ` hasufell
2013-10-27 19:43 ` Mike Gilbert
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=CAJ0EP41W1a4KciBcc8jq9BdNdoNKDCawzsgh92qJy0tEkQWMMQ@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-user@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