Op di 16 jul. 2019 om 19:14 schreef Tensortable.com <contribute@tensortable.com>:
What will be the deprecation procedures post 1.0? If a deprecation doesn't make it for 1.0, will that be an effective moratorium on deprecation for e.g. a year?

I would actually like that stability, but that also means an extra effort to get all depecation done now could be worth an extra effort.

We can still do deprecations in the 1.x releases, that is no problem. But how to handling removing deprecations and breaking changes in the versioning scheme is something we still need to discuss (eg "rolling deprecations" (each deprecation is kept for ca 3 releases, like we currently have been doing) or removing them in a version bump (like eg django does. Note we can do major version bumps more regularly than we did up to now ;)).

But I would propose to have this discussion in a separate, dedicated thread.
 

--
  Terji Petersen
 



On Tue, Jul 16, 2019, at 10:56 PM, Joris Van den Bossche wrote:
Hi all,

We had some discussion about this on the in-person dev sprint end of June, and I thought it would be good to have some public record of this as well.

A pandas 0.25.0 release is close (the RC was released earlier this month), see https://github.com/pandas-dev/pandas/issues/24950

For pandas 1.0, the current plan is to finally "just do it". The idea is that it should not take too long after 0.25.0, without additional major API changes (additions are fine of course) but with removing the current deprecated functionalities.
Depending on how much feedback there is on 0.25.0 and on how smoothly it goes for removing deprecated stuff, we could (maybe optimistically) target September for that.

Comments certainly welcome!

Joris
_______________________________________________
Pandas-dev mailing list


_______________________________________________
Pandas-dev mailing list
Pandas-dev@python.org
https://mail.python.org/mailman/listinfo/pandas-dev