TO_CSV Compression with dict arguement released in .25.0, but my Pandas .25.3 doesn't reflect source?

[ahackit]

Docstring for TO_CSV from my repo

    compression : str, default 'infer'

        Compression mode among the following possible values: {'infer',
        'gzip', 'bz2', 'zip', 'xz', None}. If 'infer' and `path_or_buf`
        is path-like, then detect compression from the following
        extensions: '.gz', '.bz2', '.zip' or '.xz'. (otherwise no
        compression).

        .. versionchanged:: 0.24.0

           'infer' option added and set to default.

Docstring for TO_CSV from pandas

    compression : str or dict, default 'infer'

        If str, represents compression mode. If dict, value at 'method' is
        the compression mode. Compression mode may be any of the following
        possible values: {'infer', 'gzip', 'bz2', 'zip', 'xz', None}. If
        compression mode is 'infer' and `path_or_buf` is path-like, then
        detect compression mode from the following extensions: '.gz',
        '.bz2', '.zip' or '.xz'. (otherwise no compression). If dict given
        and mode is 'zip' or inferred as 'zip', other entries passed as
        additional compression options.
        .. versionchanged:: 0.25.0
           May now be a dict with key 'method' as compression mode
           and other entries as additional compression options if
           compression mode is 'zip'.

Problem description

Possibly a misunderstaning of documenentation, but based on how it reads I assumed it was released.

TO_CSV has a new compression functionality to accept dictionary with METHOD type and Archive Name, in source repo doc string for TO_CSV says functionality was added to .25.0, but my docstring for TO_CSV doesn't reflect that as shown above.

I'm using a fresh install of Python + Pandas

Expected Output

Output of pd.show_versions()

INSTALLED VERSIONS

commit : None
python : 3.8.0.final.0
python-bits : 64
OS : Windows
OS-release : 10
machine : AMD64
processor : Intel64 Family 6 Model 142 Stepping 9, GenuineIntel
byteorder : little
LC_ALL : None
LANG : en_US.UTF-8
LOCALE : English_United States.1252

pandas : 0.25.3
numpy : 1.17.3
pytz : 2019.3
dateutil : 2.8.0
pip : 19.2.3
setuptools : 41.2.0
Cython : None
pytest : None
hypothesis : None
sphinx : None
blosc : None
feather : None
xlsxwriter : None
lxml.etree : None
html5lib : None
pymysql : None
psycopg2 : None
jinja2 : None
IPython : None
pandas_datareader: None
bs4 : None
bottleneck : None
fastparquet : None
gcsfs : None
lxml.etree : None
matplotlib : None
numexpr : None
odfpy : None
openpyxl : None
pandas_gbq : None
pyarrow : None
pytables : None
s3fs : None
scipy : None
sqlalchemy : None
tables : None
xarray : None
xlrd : None
xlwt : None
xlsxwriter : None

[cdw9]

It looks like that 0.25.0 version mentioned in 0d0daa8 might be wrong. Shouldn't this be 0.26.0 @drew-heenan @WillAyd ?

[WillAyd]

Weird. Working on posting updated docs for 0.25.3 at the moment so will check after that. But yes feature is part of 0.25

[jreback]

that hash above is for 1.0

[WillAyd]

Whoops yea sorry. This is a 1.0.0 (confused myself before) from #26023

[WillAyd]

Should read as 1.0.0 on master. @ahackit interested in submitting a PR to fix that doc?

[ahackit]

Can do. Will complete this weekend.

…

On Nov 1, 2019, at 5:42 PM, William Ayd ***@***.***> wrote:  Should read as 1.0.0 on master. @ahackit interested in submitting a PR to fix that doc? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[ahackit]

@WillAyd Assuming I did everything correctly, PR to fix doc #29390