unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: "W. Trevor King" <wking@tremily.us>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 00/17] nmbug-status: Python-3-compabitility and general refactoring
Date: Tue, 04 Feb 2014 12:30:30 +0200	[thread overview]
Message-ID: <m2fvnzp3uh.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <20140204005331.GQ14197@odin.tremily.us>

On Tue, Feb 04 2014, "W. Trevor King" <wking@tremily.us> wrote:

> On Mon, Feb 03, 2014 at 11:10:23PM +0200, Tomi Ollila wrote:
>>     data['message-id-term'] = 'id:"{}"'.format(value)
>> ValueError: zero length field name in format
>
> Oops, Python 2.6 still needs explicit indexes ('{0}', not '{}').  It's
> an easy fix, so I'll queue it for v2.  You're still going to need
> Python 2.7 or greater for collections.OrderedDict().  We could word
> around that too, but do we really care about 2.6?  I don't expect that
> the installed nmbug-status userbase is so large and backward that
> upgrading to 2.7 will be that hard ;).  2.6 isn't even getting
> security fixes anymore [1], so I think it's time to migrate :p.

Probably not many cares about 2.6; I already use argparse and I can add
that OrderedDict() too. Still {0} is easy enough to do :D. I am running
this notmuch & nmbug in Scientific Linux 6.2 machine which has python 2.6
-- and this is the only machine where I can review your nmbug-status
changes ;)

>>   File "devel/nmbug/nmbug-status", line 197, in _write_threads
>>     ).format(**message_display_data))
>>   File "/usr/lib64/python2.6/codecs.py", line 351, in write
>>     data, consumed = self.encode(object, self.errors)
>> UnicodeEncodeError: 'ascii' codec can't encode character u'\u017b' in
>>   position 176: ordinal not in range(128)
>
> Hmm.  __future__'s unicode_literals should be giving us a Unicode
> target, so I'm not sure why we'd have trouble injecting Unicode.  This
> works fine for me on Python 2.7 and 3.3.  Maybe you just have a funky
> encoding?  What is your:
>
>   $ locale
>   LANG=en_US.UTF-8
>   …
>   $ python -c 'import locale, sys; print(locale.getpreferredencoding() or sys.getdefaultencoding())'
>   UTF-8

LANG=en_US.UTF-8
all other LC_* variables en_US.UTF-8 except
LC_TIME=en_GB.utf8
LC_ALL empty (naturally)

python -c 'import locale; print(locale.getpreferredencoding())'
UTF-8
python -c 'import sys; print(sys.getdefaultencoding())'
ascii


anyway, if this doesn't resolve out and there is no resistance to require
python 2.7 (that means from David) I can hack around this to get this
reviewed.

>
> Cheers,
> Trevor

Tomi

>
> [1]: http://www.python.org/download/releases/2.6.9/

  reply	other threads:[~2014-02-04 10:30 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 10:59 [PATCH 00/17] nmbug-status: Python-3-compabitility and general refactoring W. Trevor King
2014-02-03 10:59 ` [PATCH 01/17] nmbug-status: Convert to Python-3-compatible print functions W. Trevor King
2014-02-03 10:59 ` [PATCH 02/17] nmbug-status: Use email.utils instead of rfc822 W. Trevor King
2014-02-03 10:59 ` [PATCH 03/17] nmbug-status: Decode Popen output using the user's locale W. Trevor King
2014-02-03 10:59 ` [PATCH 04/17] nmbug-status: Factor config-loading out into read_config W. Trevor King
2014-02-03 10:59 ` [PATCH 05/17] nmbug-status: Add metavars for --config and --get-query W. Trevor King
2014-02-03 10:59 ` [PATCH 06/17] nmbug-status: Consolidate functions and main code W. Trevor King
2014-02-03 10:59 ` [PATCH 07/17] nmbug-status: Don't require write access W. Trevor King
2014-02-03 10:59 ` [PATCH 08/17] nmbug-status: Consolidate HTML header printing W. Trevor King
2014-02-03 10:59 ` [PATCH 09/17] nmbug-status: Add a Python-3-compatible urllib.parse.quote import W. Trevor King
2014-02-03 10:59 ` [PATCH 10/17] nmbug-status: Add Page and HtmlPage for modular rendering W. Trevor King
2014-02-03 10:59 ` [PATCH 11/17] nmbug-status: Normalize table HTML indentation W. Trevor King
2014-02-03 10:59 ` [PATCH 12/17] nmbug-status: Convert from XHTML 1.0 to HTML 5 W. Trevor King
2014-02-03 10:59 ` [PATCH 13/17] nmbug-status: Encode output using the user's locale W. Trevor King
2014-02-03 10:59 ` [PATCH 14/17] nmbug-status: Anchor with h3 ids instead of a names W. Trevor King
2014-02-03 10:59 ` [PATCH 15/17] nmbug-status: Quote the title when using it as an id W. Trevor King
2014-02-08 23:18   ` W. Trevor King
2014-02-09  9:34     ` Tomi Ollila
2014-02-03 10:59 ` [PATCH 16/17] nmbug-status: Use <code> and <p> markup where appropriate W. Trevor King
2014-02-03 10:59 ` [PATCH 17/17] nmbug-status: Color threads in HTML output W. Trevor King
2014-02-03 21:10 ` [PATCH 00/17] nmbug-status: Python-3-compabitility and general refactoring Tomi Ollila
2014-02-04  0:53   ` W. Trevor King
2014-02-04 10:30     ` Tomi Ollila [this message]
2014-02-04 13:07       ` David Bremner
2014-02-04 15:50         ` W. Trevor King
2014-02-04 17:39           ` W. Trevor King
2014-02-04 16:11       ` W. Trevor King
2014-02-04 18:40         ` Tomi Ollila
2014-02-04 19:14           ` W. Trevor King
2014-02-04 20:06             ` Tomi Ollila
2014-02-05 15:00               ` Tomi Ollila
2014-02-05 15:24                 ` Tomi Ollila
2014-02-05 15:31                   ` W. Trevor King
2014-02-07 22:15                     ` W. Trevor King
2014-02-05 15:27                 ` W. Trevor King
2014-02-05 22:54                   ` Tomi Ollila
2014-02-06 18:14                     ` W. Trevor King
2014-02-08 16:11                       ` David Bremner
     [not found]                       ` <87ob2hogkr.fsf@zancas.localnet>
2014-02-08 17:16                         ` W. Trevor King
2014-02-08 18:29                           ` Tomi Ollila
2014-02-08 19:09                             ` W. Trevor King
2014-02-08 19:37                               ` Tomi Ollila
2014-02-08 22:19                                 ` W. Trevor King
2014-02-04 17:48       ` W. Trevor King
2014-02-04 18:34         ` Tomi Ollila

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=m2fvnzp3uh.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --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).