From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-python <gentoo-python@lists.gentoo.org>
Cc: Gentoo Python Project <python@gentoo.org>
Subject: Re: [gentoo-python] Re: The future of parallel phases?
Date: Sun, 23 Nov 2014 13:02:29 -0500 [thread overview]
Message-ID: <CAJ0EP439YPmVCEEBkeM8B0=QrTNSCnZCFb+f3x-5WdS=6Zt0hg@mail.gmail.com> (raw)
In-Reply-To: <CAHgY3qff7L0X=AiSxWY_tkmDPDZcw4XTxzCZcb42c870xFUzYw@mail.gmail.com>
On Sat, Nov 22, 2014 at 6:02 PM, Rafael Goncalves Martins
<rafaelmartins@gentoo.org> wrote:
> On Sat, Nov 22, 2014 at 8:54 PM, Alex Brandt <alunduil@gentoo.org> wrote:
>> On Saturday, November 22, 2014 23:06:29 Michał Górny wrote:
>>> Hello, Python team and other nice people.
>>>
>>> I'd like to discuss the topic of parallel runs again. While it
>> sounded
>>> like a good idea at first, I have my doubts now. I'll try to
>> shortly
>>> describe the implementation, then recollect the advantages
>>> and disadvantages of it.
>>>
>>> What are your thoughts?
>>
>> Based on your excellent set of points (dropped for length) I'd
>> vote for dropping the parallel phases and making things work as
>> expected rather than faster.
>>
>
> +1
>
> I agree with dropping parallel phases.
>
It was an interesting experiment, but I agree that we should aim to
simplify things here. As a developer, I usually find my self disabling
it when trying to reproduce bugs anyway.
next prev parent reply other threads:[~2014-11-23 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 22:06 [gentoo-python] The future of parallel phases? Michał Górny
2014-11-22 22:54 ` [gentoo-python] " Alex Brandt
2014-11-22 23:02 ` Rafael Goncalves Martins
2014-11-22 23:50 ` Patrice Clement
2014-11-23 18:02 ` Mike Gilbert [this message]
2014-11-23 22:00 ` [gentoo-python] " 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='CAJ0EP439YPmVCEEBkeM8B0=QrTNSCnZCFb+f3x-5WdS=6Zt0hg@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=python@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