[PATCH v3 0/8] nmbug-status: Python-3-compatibility and general refactoring

2014-02-13 Thread Tomi Ollila
On Thu, Feb 13 2014, "W. Trevor King" wrote: > The only changes since v2 [1] are related to our discussion of > locale-based encodings vs. hardcoded UTF-8 [2,3,and descendants]. > This iteration addresses those concerns by rebasing the controversial > commit (nmbug-status: Encode output using

[PATCH v3 0/8] nmbug-status: Python-3-compatibility and general refactoring

2014-02-13 Thread W. Trevor King
The only changes since v2 [1] are related to our discussion of locale-based encodings vs. hardcoded UTF-8 [2,3,and descendants]. This iteration addresses those concerns by rebasing the controversial commit (nmbug-status: Encode output using the user's locale) to the end of the series. In order to

[PATCH v3 0/8] nmbug-status: Python-3-compatibility and general refactoring

2014-02-13 Thread W. Trevor King
The only changes since v2 [1] are related to our discussion of locale-based encodings vs. hardcoded UTF-8 [2,3,and descendants]. This iteration addresses those concerns by rebasing the controversial commit (nmbug-status: Encode output using the user's locale) to the end of the series. In order to

Re: [PATCH v3 0/8] nmbug-status: Python-3-compatibility and general refactoring

2014-02-13 Thread Tomi Ollila
On Thu, Feb 13 2014, W. Trevor King wk...@tremily.us wrote: The only changes since v2 [1] are related to our discussion of locale-based encodings vs. hardcoded UTF-8 [2,3,and descendants]. This iteration addresses those concerns by rebasing the controversial commit (nmbug-status: Encode