DomainKey-Signature: a=rsa-sha1; c=nofws; d=SSpaeth.de; h=from:to:subject
	:in-reply-to:references:date:message-id:mime-version:
	content-type; q=dns; s=sspaeth.de; b=eEUK59oFajmmDoyFZKZaPuW0F9T
	ETB8SDYp+gqFizn/CmktEnTxjYNKNxO6jA9hJIsIj9hGqTwNTGULvfAyVRS2urgw
	IF1u5yWIHPtsXpWCvYvlCF8Xw2Y9uBUcwZ0ZIcDs7NT0uPRRDODlFN7HFGymusCn
	OUbDNLThLMAgvzlY=
From: Sebastian Spaeth <Sebastian@SSpaeth.de>
To: Patrick Totzke <patricktotzke@googlemail.com>, notmuch@notmuchmail.org
Subject: Re: [python] documentation & TODO list
In-Reply-To: <4edd4759.ce7d0e0a.38e2.79bb@mx.google.com>
References: <4edd4759.ce7d0e0a.38e2.79bb@mx.google.com>
User-Agent: Notmuch/0.10+58~g935365d (http://notmuchmail.org) Emacs/23.3.1
	(x86_64-pc-linux-gnu)
Date: Tue, 06 Dec 2011 13:10:17 +0100
Message-ID: <87ehwh7vfa.fsf@SSpaeth.de>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Mon, 05 Dec 2011 22:36:06 +0000, Patrick Totzke wrote:
> These are the things I noticed when going through the code today:
> 1) in filenames.py,  __str__ of Filenames: should the return value be
>    '\n'.join(self._files)? alternatively, define __iter__ to make this ob=
ject
>    behave as iterator.

To be honest, I don't remember why the code looks the way it looks, but
it certainly is not right like this. Defining __iter__ sounds like a
correct thing to me, but it could be that there was some reason why I
don't have it...
Feel free to implement a working __iter__ and provide a patch :-).

> 2) in message.py:  tags_to_maildir_flags and maildir_flags_to_tags never =
return a
>    :class:`STATUS` as advertised.

But it has been doing that for, ...., 1 minute :-)
[master ecf8da3] python: Return a STATUS value in tags_to_flags and flags_t=
o_tags

(thanks)

> I would like to see up-to-date API docs online, even if only the
> version string changed.
> Sebastian suggested using readthedocs.org for building and hosting APIdoc=
s.

I currently manually upload a generated API doc to the
packages.python.org website. I kind of like that address because it
sounds official ;-), but it is manual work. I am currently not looking
into expending the efforts I have to do on python notmuch. So setting

> I tested this recently for alot and it looks quite promising.
> A simple http get and their build-host checks out the new sources from gi=
t and builds
> them. This could be easily integrated into notmuch the release process.
> Comments on this?

I think that it would be cool to have that automatically been done on
notmuchmail.org. But given that it takes some work to set that up and
readthedocs.org is already there, I am all for using that for now.
=20
> Lastly, does anyone have an opinion on how to share a TODO list/issue tra=
cker
> for the bindings? I'm OK with github, we could move all this to the list
> and use David's nmbug..

Ohh, there is already notmuch::python in nmbug :-)

Sebastian

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk7eBikACgkQVYX1jMgnoGJIqQCfYcjv0W01/V+VuaVaRkaB0qcH
Q8wAn2700Dckbjn7FWALsNT2GU1TD0XC
=TWR6
-----END PGP SIGNATURE-----
--=-=-=--