Re: makemessages management command should not touch POT-Creation-Date

As the won't fixer person 11 years ago, I'm also more in favour of the change now, even if it changes a bit the meaning of POT-Creation-Date from "last time the pot file was updated" to "last time a change was detected in the pot file". -- You received this message because you are subscribed

Re: makemessages management command should not touch POT-Creation-Date

Hi all, I'm also in favour of the change, I also find the current behaviour annoying. Paolo ‪On Tue, Aug 31, 2021 at 1:10 PM ‫אורי‬‎ wrote:‬ > > I also find it annoying that one line changes always even if there are no > changes in translations. I prefer the file not to change at all if

Re: makemessages management command should not touch POT-Creation-Date

I also find it annoying that one line changes always even if there are no changes in translations. I prefer the file not to change at all if nothing has changed. אורי u...@speedy.net On Tue, Aug 31, 2021 at 11:03 AM 'Adam Johnson' via Django developers (Contributions to Django itself) wrote:

Re: makemessages management command should not touch POT-Creation-Date

I'm in favour of the change. Leaving the file as-is when no actual data changed just makes sense to me. The original discussion didn't touch upon the --update flag, so maybe it didn't exist then, or the participants didn't know about it. Its existence really weakens the argument that “we

makemessages management command should not touch POT-Creation-Date

Hi I was recently working on some git hooks with the makemessages command and I noticed that the "POT-Creation-Date" was always updated even if no strings were added, removed or relocated. I created a ticket (#33056 ) and was redirected to #6106