Re: [Rest2web-develop] Problem with keywords in python source

[Grzegorz A. H. <gr...@ti...>]

On 2006-12-06, Michael Foord <fuz...@vo...> wrote:
> Grzegorz Adam Hankiewicz wrote:
> > Looking at the culprit, it is the expanded svn keyword
> > LastChangedDate which expands on my sistem to "2006-10-11 00:50:49
> > +0200 (mi=C3=A9, 11 oct 2006)".
>
> Aargh... :-)
>
> Hmmm... I find these useful. It is useful to be able to look at
> a file and see when it was last changed and by whom. Can I change
> this to a different date format that doesn't screw you up ?

AFAICS you can't fix the problem because it is a client side problem.
The same would happen with the Id keyword, since that puts the name of
the file. On my system this disallows me to use the
keyword in an ascii python script if I decided to rename the file to
something using 8-bit characters, or just utf-8, that would again creep
into the source, making it invalid.

And while you may not find it necessary for rest2web, I can tell you
keywords are a pain in the ass just for making patches between developmen=
t
branches. Also at some point a coworker wanted to write a verification to=
ol to
make sure that the svn import from cvs was good, and he couldn't because
keywords screwed up the md5sum: they even get expanded in different ways
depending on your locale, cvs version and conversion switches.

I suggested on the mailing lists for keywords to always expand to english
words, which is also fair since the keywords themselves are only availabl=
e
in English, but svn developers are just too overwhelmed with work to
care about little details.

  http://svn.haxx.se/users/archive-2005-06/1306.shtml

I myself see the easy solution: keywords should just burn in hell. Any
feature of a source control system that modifies the source in a
non-deterministic way is just wrong, because you stop controlling
the source.

Anyway it doesn't bother me, I can always add the encoding myself or
remove the line, svn won't put it back for me in future updates.