Feature Type

  • [ ] Adding new functionality to pandas

  • [X] Changing existing functionality in pandas

  • [ ] Removing existing functionality in pandas

Problem Description

Have a DataFrame that contains both content in latex mathmode (eg. $x=3$), but also content which need to be escaped (eg. something_with_underscore).

With the current escape mode of the style.format() Function it is only possible to either escape both or none of them, instead of being agnostic of what is needed. 

import pandas as pd
df = pd.DataFrame([[1,"$x=3$"],[3,"something_with_underscore"]], columns=["A", "B"])
print(df.style.format(escape="latex").to_latex())

# Prints:
# \begin{tabular}{lrl}
#  & A & B \\
# 0 & 1 & \$x=3\$ \\
# 1 & 3 & something\_with\_underscore\\
# \end{tabular}

# or 
print(df.style.to_latex()) # no call to format function

# Prints:
# \begin{tabular}{lrl}
#  & A & B \\
# 0 & 1 & $x=3$ \\
# 1 & 3 & something_with_underscore\\
# \end{tabular}
# ... which is invalid LaTeX

Feature Description

  1. The easy way is to add an escape="latex-math" option and exclude the $ escaping if this string is supplied. https://github.com/pandas-dev/pandas/blob/8dab54d6573f7186ff0c3b6364d5e4dd635ff3e7/pandas/io/formats/style_render.py#L2299

  2. Because there might be other people needing different escapings one could also refactor the escape argument to take both predefined strings (e.g. "html" and "latex") but also a map with characters to escape.

    Could be called like this:

    ```python df.style.format(escape="latex;math").to_latex()

    or

    df.style.format(escape={ "%", "\%") }).to_latex() ```

  3. Both

Alternative Solutions

Replace the \\$ character with $ afterwards.

As mentioned by @attack68, if the content to be escaped is only in the header you can use format_index: 

import pandas as pd
df = pd.DataFrame([[1,"$x=3$"],[3,"Text"]], columns=["A", "under_score"])
print(df.style.format_index(axis=1, escape="latex").to_latex())

\begin{tabular}{lrl}
 & A & under\_score \\
0 & 1 & $x=3$ \\
1 & 3 & Text \\
\end{tabular}

Additional Context

Seems like other people have the same problem: https://stackoverflow.com/questions/48516653/how-to-prevent-pandas-dataframe-to-latex-from-adding-escape-characters-before https://stackoverflow.com/questions/44260547/pandas-to-latex-escapes-mathmode

Comment From: attack68

The stackoverflow examples specifically reference DataFrame.to_latex which operates differently to Styler.to_latex.

Your given example is also not ideal to describe your problem since your can actually code the separate scenarios using format_index and format separately..

import pandas as pd
df = pd.DataFrame([[1,"$x=3$"],[3,"Text"]], columns=["A", "under_score"])
print(df.style.format_index(axis=1, escape="latex").to_latex())

\begin{tabular}{lrl}
 & A & under\_score \\
0 & 1 & $x=3$ \\
1 & 3 & Text \\
\end{tabular}

However, I observe your point about math mode and allowing a customisable map and/or a specific escape callable to be passed is quite sensible. The escapers are generally quite simple functions. The suggestions regarding having a "latex-math" escape mode which is slightly different to "latex" is also valid.

Comment From: attack68

Of course you can always write your own formatting function anyway and supply that directly as the callable.

Comment From: DanielHabenicht

You have summarized it better than I can.

The stackoverflow examples specifically reference DataFrame.to_latex which operates differently to Styler.to_latex.

I just referenced the Stackoverflow answers to emphasize that its not just my problem, but reoccurring.

```python import pandas as pd df = pd.DataFrame([[1,"$x=3$"],[3,"Text"]], columns=["A", "under_score"]) print(df.style.format_index(axis=1, escape="latex").to_latex())

\begin{tabular}{lrl} & A & under_score \ 0 & 1 & $x=3$ \ 1 & 3 & Text \ \end{tabular} ```

Thanks for nice workaround!

However, I observe your point about math mode and allowing a customisable map and/or a specific escape callable to be passed is quite sensible. The escapers are generally quite simple functions. The suggestions regarding having a "latex-math" escape mode which is slightly different to "latex" is also valid.

I edited my request to reflect the problem better.

Of course you can always write your own formatting function anyway and supply that directly as the callable.

Nice, I didn't saw that it is implemented. The documentation should be updated to reflect that one can use a function too!

Should I add another mode and document it?

Comment From: attack68

My point was that one can use escape as an 'easy' way to get LaTeX valid string.

df = pd.DataFrame([["%", "&", "$x=3$"]])
print(df.style.format(escape="latex").to_latex())

\begin{tabular}{llll}
 & 0 & 1 & 2 \\
0 & \% & \& & \$x=3\$ \\
\end{tabular}

But the format method itself is well documented to accept a callable that formats the values. For example

def _custom_formatter(s):
    return s.replace("%", "\\%").replace("&", "\\&")
print(df.style.format(_custom_formatter).to_latex())

\begin{tabular}{llll}
 & 0 & 1 & 2 \\
0 & \% & \& & $x=3$ \\
\end{tabular}

Therefore, this is a second workaround, and I do not believe your requirements are currently beyond pandas. It is just that, perhaps, a common usage pattern (latex-math) is slightly beyond the basic input parameters,

Comment From: DanielHabenicht

Oh, okay. I thought you were trying to tell that one can: 

def _custom_escape(s):
    return s.replace("%", "\\%").replace("&", "\\&")
print(df.style.format(escape=_custom_escape).to_latex())

But that doesn't seem the case. Using the formatter multiple times is of course possible. :)

Then just update me if I should go ahead with providing a PR or if its not worth it maintaining it in the future.

Comment From: attack68

escape currently has the mode html and latex. I think it would be worth adding the escape mode latex-math where the only difference is that $ is not escaped (and potentially \[ and \] also but worth investigating).

This will be a user-friendly addition to the API arguments.

Comment From: natmokval

take

Comment From: attack68

@seyon99 you can't take an issue that has already been taken and which also already has a solution via the pull request that has already been submitted and approved.