• @[email protected]
    link
    fedilink
    151 day ago

    Wow, they (apparently) finally made the REPL not suck! I always thought it was weird how shit it was given that it’s one of the big reasons Python has become as popular as it is.

    Maybe in another 20 years they can make the package tooling not suck too.

    • @[email protected]
      link
      fedilink
      81 day ago

      poetry has made the package tooling generally not suck for me, and uv seems to be getting better. Just a few more PEPs to go until uv does what I want. Here’s hoping.

    • @solrize
      link
      31 day ago

      The Python REPL was always sort of minimal when used from the command line, but is quite usable in an Emacs window. IDLE is also useful some of the time. I never felt the need for anything like Eclipse because of it.

    • @[email protected]
      link
      fedilink
      English
      21 day ago

      Maybe because people who needed it knew there were better ways to do it, like ipython and Jupyter. I’ve never heard of anyone gushing about the stock REPL.

  • @[email protected]
    link
    fedilink
    81 day ago

    Woo!

    We’re still on 3.11, but it’s been some time since I last checked compatibility with the later releases. Good job everyone, I’m going to be playing with this over the next couple weeks to see if we can upgrade to it.

  • @[email protected]
    link
    fedilink
    131 day ago

    Now only have to wait for:

    • pyenv release
    • pycharm update (including terminal)
    • 3rd party libraries

    to catch up…

    • @[email protected]
      link
      fedilink
      319 hours ago

      Once that happens it’ll be just couple of years until trickles down to corpo I work at :(

      We got Python 3.10 in our Hadoop/Spark setup recently. I’m really enjoying those improved debug messages, man.

    • @[email protected]
      link
      fedilink
      21 day ago

      Wait how does one make enough money to afford the JetBrains suite? I just do everything in VSCode.

      • @faltryka
        link
        416 hours ago

        I know some people who have their work pay for it. I pay for the all products pack and it decreases in cost each year until a certain point. Not sure if I’m on some extra discount or whatnot but I only pay $18/mo and it’s easily worth it.

          • @faltryka
            link
            214 hours ago

            I have the jetbrains toolbox on like 4 of my machines at this point and three are personal and one is work. It’s a great experience but I pay for it personally because I value it.

            • @[email protected]
              link
              fedilink
              112 hours ago

              If I end up getting a promotion I’ll have to consider that. It’s just a lot of money for me right now, because my current employer doesn’t pay shit at my title/rank.

        • @[email protected]
          link
          fedilink
          114 hours ago

          Oh if only I could get my work to pay for it. Unfortunately, I’m in a megacorp that would shove said request so far down into bureaucracy hell…

      • @ArtVandelay
        link
        English
        31 day ago

        I use and enjoy VS codium as well, but PyCharm has a community edition that is free.

  • @[email protected]
    link
    fedilink
    121 day ago

    Nice I guess it’s time to check if my daily used libraries have stable 3.12 releases already.

    I guess the free-threaded mode and the JIT compiler will be the most important features from what I read, but their significance is out of my expertise.

    My absolute favorite with this update is the new REPL! It features Multiline-editing and a paste mode for easier pasting code. It also added the spaces automatically in my example.

    Sometimes I want to make some quick tests on some data in the terminal without installing IPython to my environment first, this is great news!

    This new error message will also be very useful for beginners and relieve StackOverflow:

    AttributeError: module 'numpy' has no attribute 'array' (consider renaming '/home/me/numpy.py' if it has the same name as a third-party module you intended to import)
    
    
    • @[email protected]
      link
      fedilink
      English
      213 hours ago

      That last one is going to be so good. Months ago I ran into that while porting the “Crafting Interpreters” java-based interpreter into python. It took me a few hours to figure out that one of my modules was colliding with “token” in the stdlib, a module I didn’t even know existed. Glad it’s being made clearer.