Microsoft is bringing popular programming language Python to Excel. A public preview of the feature is available today, allowing Excel users to manipulate and analyze data from Python.

You won’t need to install any additional software or set up an add-on to access the functionality, as Python integration in Excel will be part of Excel’s built-in connectors and Power Query. Microsoft is also adding a new PY function that allows Python data to be exposed within the grid of an Excel spreadsheet. Through a partnership with Anaconda, an enterprise Python repository, popular Python libraries like pandas, statsmodels, and Matplotlib will be available in Excel.

  • whataboutshutup@discuss.online
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    But why? Excel is a shit way to work with big amounts of data due to it’s own format’s complexity and bloated software. It’s welcome to implement python, but that’s not what holds it down. Opening a big csv would crash it on the same machine that loads it with a python IDE in seconds. It’s not made for this. It’s like, nice, but the volume of information you need to make it matter would break Excel in halves.

    • gecko@programming.dev
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      edit-2
      1 year ago

      This feels like a really dated take to me. Leaving aside whether this was true in the past, in 2023, Excel is happy to open absolutely gargantuan files, and it’s quite speedy once it’s done so. You can even directly tie it to a database via ODBC if you want, and that works (albeit it obviously flattens the data out in the process, so goodbye foreign keys in any real sense). It also has tons of very easy-to-use data manipulation tools (pivot tables, tables in general, data extrapolation, graphs, etc.) that end up being wonderful complements to something like Python.

      Could you write a Python program that would run faster than pure Excel and do the same thing? I mean, probably (although Excel’s core execution engine is honestly pretty freaking fast). But could you write it as quickly? Maybe, maybe not. And certainly someone who knows Excel well would have an easier time adding a little Python to patch up any issues than rewriting the whole thing from scratch.

      tl;dr I think you’re not being accurate about contemporary Excel, and I separately suspect you’re not really the target audience here

      • Dr Cog@mander.xyz
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Could I write a Python program that does the same thing as Excel but faster?

        I don’t need to. It’s called pandas

      • rhymepurple@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        I agree with all your points about Excel being capable. However, I’m struggling to think of examples where this newly announced Python integration within Excel would be helpful (with the exception of new/different visualizations) - especially for the reasons you stated about modern Excel.

        Are there any use cases that you can think of where someone who knows Excel well would resort to “adding a little Python to patch up any issues”?

        • GBU_28@lemm.ee
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          Maybe some sort of “team toolbox” of logical functions or something? I’ve seen some nightmare shops where big reports have a page of manipulations that get copied to new reports/projects every time, and each represents some sort of canned, core business logic.

          I dunno. I cant imagine how the code storage will go

          • rhymepurple@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            The code storage for Python is no different than regular Excel functions (eg - VLOOKUP(), SUM(), etc.), meaning that it is stored within an Excel cell. The only differences are that Python code is run remotely vs Excel functions running locally and the location of Python’s code matters vs Excel’s functions are location agnostic (ie - Python code runs in cells located left-to-right, top-to-bottom but Excel’s functions can dynamically determine the calculation order/location).

            I’m not sure that this new Python integration changes much about this use case (except for another way to accomplish the same/similar tasks).