st.dataframe is creating a pair of invisible quotes since 1.23.0 for data entries with commas in the text

[anirudhkaushik008]

Checklist

• I have searched the existing issues for similar issues.
• I added a very descriptive title to this issue.
• I have provided sufficient information below to help reproduce this issue.

Summary

I did not have this problem with streamlit 1.22.0
When you have a dataframe that has a column with strings and has a commas within the string, the dataframe is created and displayed normally. However when you select the dataframe and copy it over to say, excel, the entries that had a comma within the string appears with quotes around them. And it is only for those strings that have a comma in them.
This started with whatever amount of sweeping updates that happened with st.dataframe or st.data_editor in 1.23.0. I tried downgrading to 1.22.0 and the issue resolved itself

Reproducible Code Example

import streamlit as st
import pandas as pd


df = pd.DataFrame({
    'col1': [1,2],
    'col2': ['asdf,jklh','qwerrtyu']
})

st.dataframe(df)

Steps To Reproduce

1. Have streamlit version 1.23.0 or higher.
2. Run the .py script
3. Look at the dataframe and notice that there are no quotes
4. Select and copy the dataframe over to excel
5. Notice that only the one entry with a comma in it has quotes around it

Expected Behavior

With an older version, the dataframe is printed as it should be

Current Behavior

The entry asdf,jklh has a comma in the string and therefore appears as "asdf,jklh" when copying it to any text editor or spreadsheet

Is this a regression?

• Yes, this used to work in a previous version.

Debug info

• Streamlit version: 1.23.1
• Python version: 3.10.9
• Operating System: Windows 10
• Browser: Google Chrome

Additional Information

No response

[carolinedlu]

Thanks for sharing this, @anirudhkaushik008! I was able to reproduce this with Excel and Streamlit version 1.25.0 – asdf,jklh is wrapped in double quotes but qwerrtyu is not.

[anirudhkaushik008]

Yes, now to see if someone can figure out where the bug is coming from. There is no reason this should exist

[LukasMasuch]

The issue itself comes from the underlying datagrid library. But it might be fixed soon.

[benasse]

From what I've seen, a new stable version of glide-data-grid that resolves the bug has been released.
Do you plan to update it soon or will you wait until version 6.0.0 is released?

[LukasMasuch]

@benasse We are already working on the latest glide-data-grid update here. But we probably wait for 6.0.0 for release.

[LukasMasuch]

We merged the update of the underlying grid library. I believe this fixes the issue described here. This will be released in 1.32.

[sfc-gh-jesmith]

Just wanted to follow up that the updates are live as of the latest release 1.32.2. 🥳

Thanks everyone for your valuable input and feedback!