Python code will run on Microsoft’s Cloud.

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.

  • rhymepurple@lemmy.mlEnglish
    23·
    1 year ago

    I’m not a fan of it either, but I’m not sure how else this could work seamlessly. How would you ensure that everyone you share your Excel file that utilizes Python has the expected Python setup on their machine? What if they have an older version of a library you used that breaks your script? What if they don’t have Python installed at all?

    While this will only work on Windows desktop at first, Microsoft plans to roll this out to “other platforms” over time. Is there any other way for this integration to work for Excel for web, iPad, and/or Teams?

      • rhymepurple@lemmy.mlEnglish
        1·
        1 year ago

        Would something like this work for the web or Teams versions of Excel?

        Regardless, I agree. The license and remote only execution are horrible.

      • rhymepurple@lemmy.mlEnglish
        1·
        1 year ago

        That’s true. It wouldn’t solve the dependency issue though (eg - I’m using Pandas v1.5.3, you’re using Pandas v2.0.3) and I’m not sure how well it would work for some platforms like the web or Teams.

        • Golther@infosec.pubEnglish
          1·
          1 year ago

          I’m not sure exactly. Maybe it is one reason why they are pushing an online container. I guess then then it can have its own issues of dependency hell. At least with the container approach, everything either works or it is broken, and there is no having to verify which versions of Excel are installed to make the spreadsheet run.

          I doubt the end user would have control over package versions, but I had not gotten around to playing with it yet.