183

Microsoft is bringing Python to Excel (www.theverge.com)

submitted 10 months ago by pnutzh4x0r@lemmy.ndlug.org to c/python@programming.dev

59 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[-] rhymepurple@lemmy.ml 2 points 10 months 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 1 points 10 months 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 1 points 10 months 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).