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
I`m thinking about making a PR to remove StringMixin from the code base in order to make pandas use more standard string output methodology (putting the base string representations in the ``repr`` , as is standard in python3, instead of in ``str``).
Any objections to this? This is backwards compatible for users of Pandas, but may be slightly backwards incompatible for subclasses of Pandas classes located in external packages, e.g. If a downstream package did this:
I`m thinking about making a PR to remove
StringMixin
from the code base in order to make pandas use more standard string output methodology (putting the base string representations in the ``repr`` , as is standard in python3, instead of in ``str``).Any objections to this? This is backwards compatible for users of Pandas, but may be slightly backwards incompatible for subclasses of Pandas classes located in external packages, e.g. If a downstream package did this:
the repr would output an unexpected string.
Would this e.g. affect Geopandas, @jorisvandenbossche?
The text was updated successfully, but these errors were encountered: