https://techcommunity.microsoft.com/t5/excel-blog/python-in-excel-available-now/ba-p/4240212
Python in Excel is now generally available for Windows users of Microsoft 365 Business and Enterprise. Last August, in partnership with Anaconda, we..
LibreOffice has had this for quite some time. It's nice to see Microsoft finally catching up. :)
Over a year later and I still do not understand what the use case for this is.
A lot of the examples/documentation that was made by Microsoft for this seems to focus on data analysis and data visualization. Anyone in those fields would probably prefer to get the data out of Excel and into their tool/pipeline of choice instead of running their Python code in Excel. That also makes the big assumption that the data being used is fully contained within the Excel file and that the libraries used within the code are avalaible in Excel (including the library version).
For anyone looking to learn/use Excel better, I doubt the best use of their time is learning a new programming language and how Excel implements that programming language. They would likely be better off learning Excel's formulas, pivot tables, charts, etc. They could even learn Power Query to take things to another level.
For anyone looking to learn Python, this is absolutely a terrible way to do so. For example, it abstracts away library maintenance, could provide modified error messages, and makes the developer feedback loop more complicated.
If you want to automate Excel then this realistically allows for very little new functionality that did not exist prior to this feature. Using other Python libraries like OpenPyxl and xlWings will still be required to automate Excel.
I am sure there are edge cases where this iteration of Python in Excel is perfect. However, this feels like a checkbox filler ("yeah, Excel supports Python now") than an implementation of an actual useful feature. A fully featured and supported Python library that manipulates Excel/Excel files would have been a much more exciting and useful feature - even if it had to be executed outside of Excel, like OpenPyxl.
Likely aimed at financial departments which often (in my experience) love to do everything in Excel.
Sometimes when IT only lets you hold a hammer, then by necessity everything looks like a nail.
Right. VBA or this may not be the best tools for the job but when IT restricts what can be used then VBA or excel python could be great examples of Shadow IT.
That's true, but how often have you heard a finance team member wanting a CSV file so they can more easily process the data using Pandas or visualize it with MatPlotLib? How many accountants or finance people (especially those that ask for everything in Excel) do you know that is comfortable writing even a single line of Python code? How many of the finance team's Excel-based tools will Python integrate well with? What feature(s) does Python within Excel provide that Excel (formulas, pivot tables, VBA, Power Query, Power Pivot, etc.) does not provide that someone on the finance team would need? What advanced charting/dashboarding functionality does Python in Excel provide that isn't better accomplished in PowerBI (if not handled by standard Excel charts/graphs)?
Don't get me wrong - Microsoft's implementation of Python in Excel has its merits and will solve some problems that otherwise would not be possible in Excel and will make some people happy. However, this is not the solution most people were expecting, asking for, or find useful.
My biggest issue with it is that it runs everything in the cloud. So you're shipping your data to Microsoft and have latency to run anything. Seems insecure and added complexity to get a bit more out of excel.
Oh seriously? When there were rumblings of it coming years ago, I just assumed it would be implemented as a VBA successor, have everything local but just baked into excel. I guess I shouldn't be that surprised though...
Yeah I was really disappointed when I heard it was a cloud solution. I think it's due to complexity of python runtime environments, but I doubt msoft minds the opportunity to take more control.
I agree with everything you said, but (in Microsoft's eyes) this is a feature - not a bug.
Without this cloud component, how could:
I do a lot of data analysis and visualization in my job, and you are correct. I use Excel when I need to share data with co-workers, but I prefer to use Python for just about everything else. I see no reason to embed Python in Excel.
Most of the time I just push the data into a database and then do whatever I want. I get why people use Excel, but once you reach its limits it's a huge headache to migrate.
Absolutely not a replacement to VBA. Not even close. As usual, Microsoft hypes something everyone wants, and then implements something nobody asked