On Tue, 11 May 2021, 7:57 pm Petr Viktorin, wrote:
>
>
> On 11. 05. 21 11:08, Inada Naoki wrote:
> > On Tue, May 11, 2021 at 5:30 PM Petr Viktorin wrote:
> >>
> >> Test tools should treat DeprecationWarning as error by default [0][1].
> >> So even if end users don't really see it, I don't
On 11. 05. 21 11:08, Inada Naoki wrote:
On Tue, May 11, 2021 at 5:30 PM Petr Viktorin wrote:
Test tools should treat DeprecationWarning as error by default [0][1].
So even if end users don't really see it, I don't consider it "hidden".
*should* is not *do*. For example, nosetests don't
On Tue, 11 May 2021 10:25:38 +0200
Petr Viktorin wrote:
> On 10. 05. 21 10:53, Inada Naoki wrote:
> > Hi, folks.
> >
> > Now Python 3.11 development is open and I am removing some deprecated
> > stuffs carefully.
> >
> > I am considering `configparser.ParseError.filename` property that is
> >
On Tue, May 11, 2021 at 5:30 PM Petr Viktorin wrote:
>
> Test tools should treat DeprecationWarning as error by default [0][1].
> So even if end users don't really see it, I don't consider it "hidden".
>
*should* is not *do*. For example, nosetests don't show DeprecationWarning.
And there are
On 10. 05. 21 10:53, Inada Naoki wrote:
Hi, folks.
Now Python 3.11 development is open and I am removing some deprecated
stuffs carefully.
I am considering `configparser.ParseError.filename` property that is
deprecated since Python 3.2.
