to_latex has no keyword force_unicode

[jseabold]

Don't have time to look into now. Not sure it really matters, but the docs state you can use the force_unicode option here but it's not an included keyword argument.

[paulproteus]

This should be fairly easy for a newcomer to the code to examine, so I'll write up a quick note on how a newcomer might do that.

As background, you should have a vague idea of what LaTeX is. If you're not familiar with it, http://scottmcpeak.com/latex/whatislatex.html is a good introduction.

• First, find out where the docs say that the force_unicode option is accepted here
• Second, read the code, and see if force_unicode is accepted.

On my system, I search for the code with this command:

git grep 'def to_latex'

And I get these results:

pandas/core/format.py:    def to_latex(self, force_unicode=None, column_format=None):
pandas/core/frame.py:    def to_latex(self, buf=None, columns=None, col_space=None, colSpace=None,

I presume part of the problem is that core/format.py seems to accept the option, but core/frame.py does not.

The bug seems to be purely a documentation issue -- reading the code for to_latex() within core/format.py, we see a force_unicode option, but the code indicates that the option is deprecated.

Therefore, the correct fix seems (at the time of writing) to be to adjust the to_latex() function within core/format.py so that the docstring properly indicates that force_unicode exists, but is deprecated, and that the option does nothing.

Let this not serve as a replacement for you doing your own research; you (if you submit a pull request with a fix) should fact-check the claims here before submitting a pull request.

[wesm]

Note that the string formatting subsystem has changed substantially in v0.10, with unicode rendering being the default (force_unicode options have been deprecated)

[jseabold]

Looks like this can be closed then.