What You Need To Know About Python 3.13

แชร์
ฝัง
  • เผยแพร่เมื่อ 8 ม.ค. 2025

ความคิดเห็น • 26

  • @maxkupchik2112
    @maxkupchik2112 3 หลายเดือนก่อน +13

    OK so version 3.13 is out. Then next Python version will be 3.14... will it be called PIthon? There it is, folks, the worst programming pun of 2024!

  • @dowroa
    @dowroa 3 หลายเดือนก่อน +7

    Thank you for the video. As some constructive feedback, having time annotations really helps someone get to the content about 3.13 they want quickly.
    To help take your videos to the next level, here are the timestamps you could include so a viewer can get to the content they want to hear about quicker:
    0:24 - New Features
    0:54 - Interactive Interpreter
    5:19 - Free Threading
    6:56 - JIT Compiler
    8:17 - Random new CLI
    10:05 - ARGPARSE Deprecations
    10:40 - Changes to How locals() works
    11:45 - __static_attributes__
    12:36 - Removed in 3.13
    13:10 - Newly Deprecated in 3.13
    14:00 - C API Changes
    14:59 - Removed from C API
    15:40 - Thanks for Watching

    • @JakeCallahan
      @JakeCallahan  3 หลายเดือนก่อน +1

      Hey there, thanks for taking the time to collect these! I'm actually running a few experiments with this video, including seeing how well TH-cam does with its Automatic Chapters feature. I figure given a more traditional presentation, it has its best shot with this video.

  • @Neceros
    @Neceros 3 หลายเดือนก่อน +2

    🎯 Key points for quick navigation:
    00:00 *🆕 Python 3.13 introduces trends and changes that will shape programming for years.*
    00:14 *🔍 Focus on key features: interactive interpreter improvements, free threading, JIT compiler, new CLI for random, argparse deprecations, locals changes.*
    00:29 *🖥️ Enhanced interactive interpreter with multi-line editing and better indentation handling.*
    00:43 *🧵 Introduction of free threading, a major language change.*
    00:56 *🆚 Demonstration of interactive interpreter changes between Python 3.12 and 3.13.*
    01:09 *🔄 REPL now retrieves entire class definitions for easier editing.*
    01:24 *📐 Automatic indentation handling within functions in Python 3.13.*
    01:52 *🖌️ Enhanced prompt and traceback colors for better readability and error reporting.*
    03:17 *🛠️ Continuous improvements in tracebacks with clearer error locations.*
    03:31 *📚 Invoke help in REPL with just 'help' instead of 'help()'.*
    03:44 *❌ Exit and quit commands now work without parentheses in REPL.*
    03:59 *🔧 New hotkeys: F1 for help, F2 for input history, F3 for paste mode in interactive interpreter.*
    05:20 *⚠️ Free threading is experimental in Python 3.13 and not recommended for production.*
    06:57 *⚡ Introduction of an experimental JIT compiler as a tier 2 interpreter.*
    08:06 *🎲 New CLI for the random module enhances random operations capabilities.*
    09:58 *⛔ Deprecations in argparse allow marking options as deprecated with warnings.*
    10:54 *🔄 locals() now returns independent snapshots, improving consistency across implementations.*
    11:36 *🧩 Addition of dunder static attributes tracks accessed class attributes during compilation.*
    12:33 *🚫 Removal of several modules via PEP 594; check compatibility before upgrading.*
    14:10 *🛠️ Changes to C API in Python 3.13; library maintainers need to review release notes.*
    Made with HARPA AI

  • @eziola
    @eziola 2 หลายเดือนก่อน

    Great video! Stoked to see some more of your Standard Library videos!

  • @JakeCallahan
    @JakeCallahan  3 หลายเดือนก่อน +4

    What are you most looking forward to in Python 3.13?
    Update: it looks like there was a performance regression that has delayed the release to October 7th.

    • @cheesecake_mafia
      @cheesecake_mafia 3 หลายเดือนก่อน

      Read somewhere about changes to the GIL in the new version and how it's going to be better. Also, i remember reading that in multiprocessing, sharing data between processes is going to be easier. Tbh, i didn't understand any of it.
      But again as usual, great video Jake. Your channel is criminally underrated. This was helpful.

    • @JakeCallahan
      @JakeCallahan  3 หลายเดือนก่อน

      So some of the GIL-related changes are applicable to all of Python, and not just free-threaded builds. That's because they've been simplifying and optimizing where and when the lock is acquired and released.
      I'm notnsure about the multiprocessing changes you're referring to, but sounds promising!

    • @NostraDavid2
      @NostraDavid2 3 หลายเดือนก่อน

      The JIT compiler. Not because it's faster, but because of its future potential. Pypy is great, but always having it lag behind isn't great, so something similar being integrated is a great move, IMO.

  • @jmreagle
    @jmreagle 2 หลายเดือนก่อน +1

    Pedantry: you speak of changes to the language that are not that; they are changes to CPython and its REPL.

    • @JakeCallahan
      @JakeCallahan  2 หลายเดือนก่อน

      I agree that this comment is pedantic ;)
      Of course, you're correct. I do largely use Python to refer to CPython since it is the most widely used implementation of the Python language. If I do need to speak about other variants, I will call them out by name.

  • @blanky_nap
    @blanky_nap 3 หลายเดือนก่อน +1

    Smooth review!

  • @dragonkat13
    @dragonkat13 3 หลายเดือนก่อน +1

    Another great video! I love how you cover topics that others do not, or if they do, they are very poor at teaching it or explaining it in such a calm, easy manner as you do. Thank YOU for taking the time and putting in the hard work to make these video for us !

  • @OmidAtaollahi
    @OmidAtaollahi 2 หลายเดือนก่อน

    plaese explain more about JIT

  • @juancarlospizarromendez3954
    @juancarlospizarromendez3954 3 หลายเดือนก่อน +2

    I do know thread-safe and thread-unsafe but, is free-threading thread-free?

    • @JakeCallahan
      @JakeCallahan  3 หลายเดือนก่อน

      It isn't thread-free, but more "independent threads" if that makes more sense.

  • @mikescholz6429
    @mikescholz6429 3 หลายเดือนก่อน

    Is it going to make Inkscape start faster?

    • @JakeCallahan
      @JakeCallahan  3 หลายเดือนก่อน

      Unfortunately, this won't improve the performance of C++ applications

    • @mikescholz6429
      @mikescholz6429 3 หลายเดือนก่อน

      @@JakeCallahan if its compiled to c++ then why didn’t 3.10 speed it up? 😉

    • @JakeCallahan
      @JakeCallahan  3 หลายเดือนก่อน

      You're blowing my mind!!

  • @OmidAtaollahi
    @OmidAtaollahi 2 หลายเดือนก่อน

    tnx🥰

  • @Dunning_Kruger_Is__On_Youtube
    @Dunning_Kruger_Is__On_Youtube 3 หลายเดือนก่อน +1

    Yeah adding those parentheses at the end of help or quit in the REPL were so cumbersome that I almost gave up programming.
    Thanks for the info!

    • @JakeCallahan
      @JakeCallahan  3 หลายเดือนก่อน +1

      I can't count how many times I failed to quit the repl on my first attempt!
      Probably why I switched to IPython

    • @NostraDavid2
      @NostraDavid2 3 หลายเดือนก่อน

      Ctrl-d to send a SIGQUIT signal to quit the REPL, but only on Linux because Windows is poopoo.

  • @salamanetwork
    @salamanetwork 3 หลายเดือนก่อน

    Perl has Plain Old Document since 90's (POD).
    Python will borrow POD in 2024 😄

  • @pauleedavidson9251
    @pauleedavidson9251 3 หลายเดือนก่อน

    Jackson Anna Lewis Nancy Lewis Susan