See this comment from a previous pull request I submitted: pandas-dev/pandas#41524 (comment)

Just need to add , optional, so opening as good first issue

I just ran into an issue when trying to use to_csv with distributed workers that don't share a file system. I shouldn't have been surprised that writing to a local file system from a distributed worker doesn't work. It shouldn't work. But the error I got was just a File Not Found error. That brought me to:dask/dask#2656 (comment) - which was the answer.

It's normal to have many map() calls, and some of them can take a few minutes,
it would be nice to have a description on the progress bar.

Alternative solution:
Print the description before/after the map() call.

Describe the bug
Integer columns that are enclosed in quotes are not correctly inferred as integer columns.

Steps/Code to reproduce bug

import cudf
import pandas as pd
from io import StringIO
from cudf.tests.utils import assert_eq

buffer = '"intcol","stringcol"\n"1","some string"\n"2","some other string"'
pd_df = pd.read_csv(StringIO(buffer))
cu_df = cudf.read_csv(String

I've been experimenting with the crypto aspects of the library, and I do see that there are the endpoints for daily, weekly, and monthly, however the endpoint for intraday is not available using the "function=CRYPTO_INTRADAY" from the Cryptocurrencies section of the API.

I would assume the format would be:
`(data, meta) = cc.get_crypto_intraday(symbol = "", interval = "", market = "", outputs

• What's your use case?