'bzr status' crash if .bzrignore containts Latin-2 chars

Hello, thanks for the bug report.
Could you attach the .bzrignore file so we can look into it a bit more?

Thanks!

.bzrignore supposed to be in utf-8 encoding. To achieve this is better to add new ignore patterns with `bzr ignore PATTERN` command.

bzr itself should not fails with traceback in this case though. I think it's enough to print warning in this case and go on.
Should be easy to fix.

As suggested fix is:

* Print warning. include line number?
* Carry on

I have modified "ignores.py" as follows. But I would like to use the warning call, must I move my code into "builtin.py" and catch the exception there? In which case should I make a custom exception and include the line number within it?

def parse_ignore_file(f):
    """Read in all of the lines in the file and turn it into an ignore list"""
    ignored = set()
    line_number = 0 # Line counting to report character decode errors
    for line in f.read().split('\n'):
        line_number +=1
        # Decode the line here, and catch any decoding errors
        try:
            line = line.decode('utf8').rstrip('\r\n')
            if not line or line.startswith('#'):
                continue
            ignored.add(globbing.normalize_pattern(line))
        except UnicodeDecodeError:
            print('ignore file: Line %d, malformed utf8 character. ignoring line.'
                  ' please ensure file is utf8 encoded' % (line_number))
    return ignored

---------- output example. (msg TBD) ---------------
C:\bzr\bazaar\183504_latin_2_ignore_file>python bzr st
ignore file: Line 68, malformed utf8 character. ignoring line. please ensure file is utf8 encoded
modified:
  .bzrignore
  bzr*
  bzrlib/ignores.py
unknown:
  .pydevproject
  .settings/
  src/

I've read the developer docs, and it seems a custom exception may be appropriate. If that's the case then the first and/or last line number of the decode error can be stored in the exception, and it would be raised on exit from parse_ignore_file (ignores.py) and caught in get_ignore_list (workingtree.py) which already imports "mutter, note" and i'd add "warning" to that.

Perhaps this should not be an exception thowing event? Advice welcomed.

2009/9/26 Jason Spashett <email address hidden>:
> I've read the developer docs, and it seems a custom exception may be
> appropriate. If that's the case then the first and/or last line number
> of the decode error can be stored in the exception, and it would be
> raised on exit from parse_ignore_file (ignores.py) and caught in
> get_ignore_list (workingtree.py) which already imports "mutter, note"
> and i'd add "warning" to that.
>
> Perhaps this should not be an exception thowing event? Advice welcomed.

I think probably not; you should give a warning through trace.warning.

--
Martin <http://launchpad.net/~mbp/>