Inconsistent header treatment for csv tables

[textualize]

Inconsistent header treatment for csv tables

[willmcgugan]

It’s a heuristic used by the Python CSV library, which is imperfect as you have noticed. In the future I’ll expose a way to adjust the via an option.

[AndydeCleyre]

Thanks! Do you know what about the input in this case gives CSV the wrong idea, so that I can work around this?

[willmcgugan]

Not sure. You could have a look at the source of the csv module.

[AndydeCleyre]

FYI:

• csv.Sniffer.has_header:

      def has_header(self, sample):
          # Creates a dictionary of types of data in each column. If any
          # column is of a single type (say, integers), *except* for the first
          # row, then the first row is presumed to be labels. If the type
          # can't be determined, it is assumed to be a string in which case
          # the length of the string is the determining factor: if all of the
          # rows except for the first are the same length, it's a header.
          # Finally, a 'vote' is taken at the end for each column, adding or
          # subtracting from the likelihood of the first row being a header.

• I spotted "lexter" @ https://github.com/Textualize/rich-cli/blob/main/src/rich_cli/__main__.py#L569