python warnings got way better in 3.12!

I totally missed this improvement when reviewing 3.12 back in the day and it's pretty significant. but I think they missed one key part :(
warnings in python: • python warnings (begin...
python warnings defaults suck: • python warnings defaul...
what's new in python 3.12: • python 3.12 release hi...
playlist: • anthony explains
==========
twitch: / anthonywritescode
dicsord: / discord
twitter: / codewithanthony
github: github.com/aso...
stream github: github.com/ant...
I won't ask for subscriptions / likes / comments in videos but it really helps the channel. If you have any suggestions or things you'd like to see please comment below!

[@eliottwillis784]

Nice! I wonder why `skip_file_prefixes` parameter has not been added to the new `warnings.deprecated` decorator in Python 3.13.

[@SQADIqw]

Does it have the same issue pointing on library code instead of library user calls?

[@anthonywritescode]

weird that they didn't add the api there too -- even more confusing they have `stacklevel=1` as the default... but it acts as `stacklevel=2` (so at least they got that part right?)

[@spencer3752]

Oh man. For internal calls to user-facing APIs that may invoke a warning, I've been doing things like `warnings.catch_warnings` and re-emitting warnings to correct the stack level. This seems a lot more convenient.

[@mrswats]

Never skip profecies

[@aditya_marathe]

Finally installed 3.12 looking forward to daily driving it for the foreseeable future.

[@ruroruro]

Btw, I wonder, how would one use this feature if your python package provides both the libary code and an executable entrypoint (via __main__.py or via console_scripts or similar).

[@anthonywritescode]

imo the warning system doesn't really make sense for cli tools -- it's more for programmatic warnings

[@CooperE16]

You mentioned you mainly write tools as opposed to libraries. What’s the distinction? I understand libraries v applications? Are tools just applications for developers? eg CLI

[@AcuteAangle]

I usually understand a ‘tool’ to be a program with a single primary purpose. I would describe the Coreutils as ‘tools’, as well as single-purpose GUI utilities like balenaEtcher. The CLI programs provided by ImageMagick, `ffmpeg`, or `btrfs-progs` as well. I wouldn’t call Firefox, Emacs, or KDE tools, however, as they have an expansive scope, being more like long-lived workspaces you perform a variety of tasks in, rather than narrowly-scoped utilities for a specific class of uses. Daemons and games are also not usually called ‘tools’.

[@anthonywritescode]

for me libraries are imported and used by other software. tools are kinda everything else (self contained, don't provide programmatic apis) and for me they are almost all in the form of command line applications

[@ln11389]

I have been working with 3.12 for a while and this was very informative. Thanks for the video.