Pandas 1.0
pandas.pydata.org
Pandas 1.0
1–10 of 80 posts
Re: Pandas 1.0
#2Re: Pandas 1.0
#3How are we supposed to interpret this in light of the promise that there will be no more API breakages until 2.0? It reads as if this promise does not apply to string data, which impacts rather a lot of use cases.
Re: Pandas 1.0
#4Re: Pandas 1.0
#5If anyone else is wondering what this is. (Source: project homepage
Re: Pandas 1.0
#6Re: Pandas 1.0
#7By comparison, the API of something like Pytorch is an absolute pleasure to use and even though I'm not using it all the time, I almost have no trouble every time I begin training models/trying out new things in Pytorch.
All that being said, this is definitely a step in the right direction and hopefully the API gets a bit more coherent over time.
Re: Pandas 1.0
#8I think it's worth it to acknowledge the great stewardship of the community by all the Pandas developers (and the rest of people in the PyData ecosystem). It has been an inspiration for me as I create and contribute to open source libraries for data science [0][1].
[0] https://github.com/FeatureLabs/featuretools/ [1] https://github.com/FeatureLabs/compose/
Re: Pandas 1.0
#9I am looking forward to a decade of fewer API breaking changes. However, 1.0 introduces a new column type for strings, recommends its use over the old "object" column type, yet says it is "Experimental and may change at any time." How are we supposed to interpret this in light of the promise that there will be no more API breakages until 2.0? It reads as if this promise does not apply to string data, which impacts ra…
Re: Pandas 1.0
#10I am looking forward to a decade of fewer API breaking changes. However, 1.0 introduces a new column type for strings, recommends its use over the old "object" column type, yet says it is "Experimental and may change at any time." How are we supposed to interpret this in light of the promise that there will be no more API breakages until 2.0? It reads as if this promise does not apply to string data, which impacts ra…
It states in the deprecation policy that "API-breaking changes will be made only in major releases (except for experimental features)".