You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the main API reference indicates that the delim_whitespace option to pandas.read_csv is deprecated, the User Guide still lists it as an option with no caveat. This may lead new users to adopt an option that is already deprecated, and either immediately get warnings, or write code that will break relatively soon.
Suggested fix for documentation
Either remove the delim_whitespace option from the page (probably preferred; new users don't need to be introduced to features about to be deprecated) or add a deprecation notice similar to the one appearing on the read_csv reference
The text was updated successfully, but these errors were encountered:
this option's deprecation will be enforced so it will be removed from the docs in the next release anyway.
Agreed that it should be, but with the way it's hard coded in the User Guide, nothing will fail if it accidentally gets left behind. Also, in good generality I think the User Guide should represent how we want users to use pandas, so I think it makes sense to remove it now, ahead of its deprecation.
Pandas version checks
main
hereLocation of the documentation
https://pandas.pydata.org/docs/dev/user_guide/io.html#basic
Documentation problem
While the main API reference indicates that the
delim_whitespace
option topandas.read_csv
is deprecated, the User Guide still lists it as an option with no caveat. This may lead new users to adopt an option that is already deprecated, and either immediately get warnings, or write code that will break relatively soon.Suggested fix for documentation
Either remove the
delim_whitespace
option from the page (probably preferred; new users don't need to be introduced to features about to be deprecated) or add a deprecation notice similar to the one appearing on theread_csv
referenceThe text was updated successfully, but these errors were encountered: