[spambayes-dev] Nuke experimental_ham_spam_imbalance_adjustment?

[Tim Peters]

[Skip Montanaro]
> My intent was to mimic rfc-822-style experimental headers, but it
> appears I don't really understand what ConfigParser does vis a vis
> case-sensitivity. (I thought it was case-insensitive, and the code
> suggests it is, but that seems to not quite be the case.)  In
> OptionsClass.merge_file() I originally wanted to use X- (note its
> presence in a comment I forgot to change), but wound up switching to
> x-.  A little more investigation suggests that ConfigParser does
> indeed ignore case in the values it reads from the options file, but
> that the code in OptionsClass.py doesn't treat the options it stores
> in self._options that way.

I'd call that a bug in OptionsClass.py, then.  ConfigParser is modeled on
RFC 822 header fields, and supplies case-insensitive option names *because*
822 mandates case-insensitive semantics.

> I don't really care what hoops we as programmers have to jump
> through, but I'd like users to be able to use either x- or X-.  I
> agree, the docstrings should match required usage.  In any case, it
> appears Tim (or someone else) has fixed things).

Tony checked in a bunch of changes, but I suspect it's still case-sensitive.