On 11/27/2019 10:38 AM, Brett Cannon wrote:
What do people think of the idea of requiring all deprecations specifying a
version that the feature will be removed in (which under our annual release
cadence would be at least the third release from the start of the deprecation,
hence the
> What do people think of the idea of requiring all deprecations specifying
a version that the feature will be removed in (which under our annual
release cadence would be at least the third release from the start of the
deprecation, hence the deprecation being public for 2 years)? And that we
also
Gregory P. Smith wrote:
> On Wed, Nov 27, 2019 at 10:15 AM Brett Cannon br...@python.org wrote:
> > Gregory P. Smith wrote:
> > On Tue, Nov 26, 2019 at 12:00 PM Brett Cannon
> > br...@python.org wrote:
> > Python 3.9 is going to be the first release
> > which
> > will exist without any
> > Python
What do people think of the idea of requiring all deprecations specifying a
version that the feature will be removed in (which under our annual release
cadence would be at least the third release from the start of the deprecation,
hence the deprecation being public for 2 years)? And that we
On Wed, Nov 27, 2019 at 10:15 AM Brett Cannon wrote:
> Gregory P. Smith wrote:
> > On Tue, Nov 26, 2019 at 12:00 PM Brett Cannon br...@python.org wrote:
> > > Python 3.9 is going to be the first release which
> > > will exist without any
> > > Python 2.7 overlap. Does this mean we are ready to
Gregory P. Smith wrote:
> On Tue, Nov 26, 2019 at 12:00 PM Brett Cannon br...@python.org wrote:
> > Python 3.9 is going to be the first release which
> > will exist without any
> > Python 2.7 overlap. Does this mean we are ready to start removing things
> > that have been deprecated since at least