[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

R. David Murray added the comment: Thanks, Michael. -- resolution: -> fixed stage: -> resolved status: open -> closed type: -> behavior versions: +Python 3.5 ___ Python tracker __

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

Roundup Robot added the comment: New changeset c969413584cf by R David Murray in branch 'default': #18128: use standard + timezone format in POT-Creation-Date header. https://hg.python.org/cpython/rev/c969413584cf -- nosy: +python-dev ___ Python t

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

Barry A. Warsaw added the comment: @rdm: I'm pretty sure you're right about nobody noticing. :) Make it so! -- ___ Python tracker ___ ___

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

R. David Murray added the comment: Oh, I forgot to say that the patch looks good to me. -- ___ Python tracker ___ ___ Python-bugs-list

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

R. David Murray added the comment: Barry, would you be OK with just applying this to 3.5? We can add a porting note to whatsnew. My guess, though, is that no one is going to notice. -- nosy: +r.david.murray ___ Python tracker

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

Michael McFadden added the comment: Post-review - new patch -- Added file: http://bugs.python.org/file39050/issue18128.patch ___ Python tracker ___ __

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

Michael McFadden added the comment: Patch File iss18128.patch adds test_i18n to start testing the entire Tools/i18n package, and has a very simple fix. -- keywords: +patch Added file: http://bugs.python.org/file39024/iss18128.patch ___ Python tracker

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

Michael McFadden added the comment: I'm going to be adding some tests around pygettext tool and then tackling this. -- nosy: +flipmcf ___ Python tracker ___ _

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

Barry A. Warsaw added the comment: It's probably worth changing. My only concern would be backwards compatibility issues. -- ___ Python tracker ___

[issue18128] pygettext: non-standard timestamp format in POT-Creation-Date

New submission from Jakub Wilk: pygettext uses non-standard timestamp format in the POT-Creation-Date field. For example: POT-Creation-Date: 2013-06-03 22:31+CEST whereas xgettext uses this format: POT-Creation-Date: 2013-06-03 22:31+0200 You could use this code to generate timestamps in the