Steven D'Aprano writes:
> Or maybe, as a developer (not an end-user of an app), you could be more
> proactive in reporting those warnings to the third party, and
> encouraging them to fix them. Maybe even submitting a patch?
As Chris B points out, it's quite possible that (generic) you have
On Thu, Jan 27, 2022 at 10:47 AM Steven D'Aprano
wrote:
> > >Getting the right people to pay attention to them is always the hard
> part.
>
> Or maybe, as a developer (not an end-user of an app), you could be more
> proactive in reporting those warnings to the third party, and
> encouraging them
On Wed, Jan 26, 2022 at 02:40:32PM -0800, Neil Schemenauer wrote:
> On 2022-01-18 23:14, Gregory P. Smith wrote:
> >
> >Our stdlib unittest already enables warnings by default per
> >https://bugs.python.org/issue10535.
> >
> >Getting the right people to pay attention to them is always the hard
On Wed, Jan 26, 2022 at 12:50 PM Neil Schemenauer
wrote:
> maybe we should be more aggressive about showing PendingDeprecationWarning
> if it comes from code that seems to be written by the user, e.g. outside
> site-packages
>
> That would be pretty straightforward.
> or not from a package
On 2022-01-18 23:14, Gregory P. Smith wrote:
Our stdlib unittest already enables warnings by default per
https://bugs.python.org/issue10535.
Getting the right people to pay attention to them is always the hard part.
I wonder if we can do a bit better in that regard. When I install 3rd
On Wed, Jan 19, 2022 at 11:58 AM Sebastian Rittau wrote:
>
> Am 18.01.22 um 22:57 schrieb Victor Stinner:
> > At the end of my first email, I also suggest thinking about
> > incompatible changes differently, try to make affected projects
> > compatible in advance. The problem are not the changes
Am 18.01.22 um 22:57 schrieb Victor Stinner:
At the end of my first email, I also suggest thinking about
incompatible changes differently, try to make affected projects
compatible in advance. The problem are not the changes themselves, but
how they are introduced in Python, and more globally how
On Tue, Jan 18, 2022 at 6:24 AM Victor Stinner wrote:
> Hi,
>
> My colleagues Tomáš Hrnčiar and Miro Hrončok made good progress on
> updating Python 3.10 to Python 3.11 in Fedora, but some specific
> Python 3.11 incompatible changes are causing more troubles than
> others:
>
On Tue, Jan 18, 2022 at 10:58 PM Christopher Barker
wrote:
> On Tue, Jan 18, 2022 at 10:30 AM Brett Cannon wrote:
>
>> I remember that "noisy by default" deprecation warnings were widely
>>> despised.
>>>
>>> One thought, what if they were off by default UNLESS you were doing unit
>>> tests?
On Tue, Jan 18, 2022 at 10:30 AM Brett Cannon wrote:
> I remember that "noisy by default" deprecation warnings were widely
>> despised.
>>
>> One thought, what if they were off by default UNLESS you were doing unit
>> tests?
>>
>
> I believe pytest already does this.
>
Indeed it does, at least
On Tue, Jan 18, 2022 at 5:48 PM Steve Dower wrote:
> Discovering during alpha that some packages haven't updated for the
> release that hasn't happened yet isn't the end of the world. Reverting
> the changes now is probably a bit premature - realistically we can undo
> these anytime during beta
On Tue, Jan 18, 2022 at 9:43 AM Richard Damon
wrote:
>
>
> On Jan 18, 2022, at 11:34 AM, Guido van Rossum wrote:
>
>
> At best it shows that deprecations are complicated no matter how well you
> plan them. I remember that "noisy by default" deprecation warnings were
> widely despised.
>
> On
> On Jan 18, 2022, at 11:34 AM, Guido van Rossum wrote:
>
>
> At best it shows that deprecations are complicated no matter how well you
> plan them. I remember that "noisy by default" deprecation warnings were
> widely despised.
>
>> On Tue, Jan 18, 2022 at 6:49 AM Antoine Pitrou wrote:
On 1/18/2022 2:44 PM, Antoine Pitrou wrote:
We propose to revert the following 2 changes in Python 3.11 and
postpone them in a later Python version, once most projects will be
compatible with these changes:
* Removal of unittest aliases (bpo-45162): it broke 61 Fedora packages
* Removals from
At best it shows that deprecations are complicated no matter how well you
plan them. I remember that "noisy by default" deprecation warnings were
widely despised.
On Tue, Jan 18, 2022 at 6:49 AM Antoine Pitrou wrote:
> On Tue, 18 Jan 2022 15:17:41 +0100
> Victor Stinner wrote:
> > Hi,
> >
> >
On Tue, 18 Jan 2022 15:17:41 +0100
Victor Stinner wrote:
> Hi,
>
> My colleagues Tomáš Hrnčiar and Miro Hrončok made good progress on
> updating Python 3.10 to Python 3.11 in Fedora, but some specific
> Python 3.11 incompatible changes are causing more troubles than
> others:
>
16 matches
Mail list logo
