public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH 1/4] catalyst: Specify python2 rather than the generic python
Date: Fri, 11 Oct 2013 12:28:40 -0700	[thread overview]
Message-ID: <CAEdQ38GuQ0-j=QU7LkZo_y8d=UUvnwZAmSbgawGuL1277NjxTA@mail.gmail.com> (raw)
In-Reply-To: <1381515339.24205.73.camel@big_daddy.dol-sen.ca>

On Fri, Oct 11, 2013 at 11:15 AM, Brian Dolbec <dolsen@gentoo.org> wrote:
> On Fri, 2013-10-11 at 10:38 -0700, Dylan Baker wrote:
>> This allows catalyst to work regardless of whether a user prefers that
>> usr/bin/python be python 2.x or 3.x.
>> ---
>>  catalyst | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/catalyst b/catalyst
>> index 4550d05..11560fb 100755
>> --- a/catalyst
>> +++ b/catalyst
>> @@ -1,4 +1,4 @@
>> -#!/usr/bin/python -OO
>> +#!/usr/bin/python2 -OO
>>
>>  # Maintained in full by:
>>  # Catalyst Team <catalyst@gentoo.org>
>
>
> I'll reply to all 4 patches from this one.
>
> This is not needed due to the way python apps are wrapped during
> install.  bin/catalyst is renamed to bin/catalyst-python2.x and a
> python-exec script replaces the original bin/catalyst.

What do we gain by doing this in the ebuild's src_install() over doing
it in? Because...

> This is only
> good for running the code directly from the git checkout.

actually seems useful. We've had clearly broken commits go upstream,
and if the author had been able to test from a git checkout we
probably could have avoided that.

> Also, we plan
> to make the code python-3 capable as soon as a few more main code
> changes are done.

This isn't a reason to not specify the correct version of python.

> As for the other patches, that work is already done in my rewrite and
> will be taking over the master branch soon.  It is the 3.0 branch which
> has been rebased to the rewrite-on-master branch.  There are a couple
> rebase errors to fix on it still.
>
> http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git

Sounds like it shouldn't be any trouble to rebase on top of Dylan's
patches, which are (pending the v2 of patch 2) read to be applied to
master.

What I mean is that I don't want to turn down contributions from new
developers because there's a big backlog of work that hasn't gone
upstream.


  reply	other threads:[~2013-10-11 19:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 17:38 [gentoo-catalyst] [PATCH 1/4] catalyst: Specify python2 rather than the generic python Dylan Baker
2013-10-11 17:38 ` [gentoo-catalyst] [PATCH 2/4] Catalyst: use a more pythonic method to import modules Dylan Baker
2013-10-11 18:00   ` [gentoo-catalyst] " Dylan Baker
2013-10-11 17:38 ` [gentoo-catalyst] [PATCH 3/4] catalyst: split combined import Dylan Baker
2013-10-11 17:38 ` [gentoo-catalyst] [PATCH 4/4] catalyst: Remove commented sections of code Dylan Baker
2013-10-11 18:15 ` [gentoo-catalyst] [PATCH 1/4] catalyst: Specify python2 rather than the generic python Brian Dolbec
2013-10-11 19:28   ` Matt Turner [this message]
2013-10-11 21:11     ` Brian Dolbec
2013-10-11 21:58       ` Matt Turner
2013-10-13  9:19         ` Dylan Baker
2013-10-13 16:33         ` Brian Dolbec
2013-10-13 20:52           ` Dylan Baker

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='CAEdQ38GuQ0-j=QU7LkZo_y8d=UUvnwZAmSbgawGuL1277NjxTA@mail.gmail.com' \
    --to=mattst88@gentoo.org \
    --cc=gentoo-catalyst@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