unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <bremner@debian.org>
To: "W. Trevor King" <wking@tremily.us>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v3] nmbug: Translate to Python
Date: Sun, 24 Aug 2014 13:39:23 -0700	[thread overview]
Message-ID: <871ts5ei6c.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <20140806232131.GH31313@odin.tremily.us>

"W. Trevor King" <wking@tremily.us> writes:
>
>> > +__version__ = '0.2'
>> 
>> Do we need/want a version distinct from that of notmuch?
>
> nmbug is very loosely bound to the notmuch core.  To me it feels like
> a separate project that happens to share the same version control
> repository.  I'm happy to synchronize versions, but then we have to
> remember to bump the nmbug version for each notmuch release.

Unless/until we split nmbug from notmuch I'd rather keep the versions
the same to avoid confusion.  I guess the "right way" (TM) would be
share the hackery used in doc/conf.py to parse the version file and use
it from python.

>> as a non-native speaker of python, I find this a bit hard to read.
>> How about adding some parens to make the multiple return more clear,
>> so
>> 
>>     (status, tree, stderr) = _git(
>
> That's legal, but I rarely see the parenthesized version in the wild.
> For examples showing the unparenthesized version, see [2,3].
> Parentheses are optional for Python tuples [4], so you'd only want
> them if ‘=’ had a higher precedence than ‘,’.  That's my argument for
> the unparenthesized version, but feel free to overrule me ;).

I'd rather go with readability (which I admit is subjective) then try to
minimize parens. We're lisp programmers, after all ;).

      reply	other threads:[~2014-08-24 20:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-20 22:59 [PATCH v3] nmbug: Translate to Python W. Trevor King
2014-07-20 23:11 ` W. Trevor King
2014-07-20 23:34 ` W. Trevor King
2014-07-21  0:21 ` W. Trevor King
2014-08-05  0:14 ` David Bremner
2014-08-06  1:16   ` David Bremner
2014-08-06 23:28     ` W. Trevor King
2014-08-24 20:02       ` David Bremner
2014-08-06  1:24   ` David Bremner
2014-08-06 23:38     ` W. Trevor King
2014-08-24 20:07       ` David Bremner
2014-08-06 23:21   ` W. Trevor King
2014-08-24 20:39     ` David Bremner [this message]

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871ts5ei6c.fsf@maritornes.cs.unb.ca \
    --to=bremner@debian.org \
    --cc=notmuch@notmuchmail.org \
    --cc=wking@tremily.us \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).