people liked they could set up scripts in VBA for automating routine tasks, but hated the VBA language syntax, from what I've understood, and wished they could program those functions in some more popular language like Python etc. But that isn't what this is.
If we are going to open up Jupyter notebooks, we have already failed.
(That's why VBA works, it's the only thing that runs on locked down corp laptops, because it's inside Excel.)
> The Python in Excel add-on license includes everything in Python in Excel for Microsoft 365, plus premium compute and more calculation mode options. Premium compute means faster Python formula calculation times. With the additional calculation mode options, you can switch between manual, partial, or automatic calculation modes to control when and how often your workbooks recalculate Python formulas.
https://support.microsoft.com/en-us/office/python-in-excel-a...
This is disappointing. A much easier way to 'keep your data private' would be to run it locally. Surely a bundled Python interpreter run inside a sandbox that prevents network access would be just as secure, and cheaper for Microsoft since they don't have to run any Azure resources to support it.
no way, itd be more secure...they wouldnt be able to peek into your spreadsheet
If you've ever written a spreadsheet of meaningful complexity, you've probably been forced into a disastrous mess of nested IF statements (or helper columns).
Python is soooo much easier to read than the built-in formulas.
I'm excited to try this out!
I wonder if Microsoft may eventually EEE CPython by creating their own competing implementation running on top of Excel.
For local python in a spreadsheet, LibrePythonista allows running IPython code in a LibreOffice spreadsheet
When you get very complicated flows, of one cell pointed to another cell, it becomes a massive mess. It's hard to debug and there's no way to "linearize" the flow into something more legible, and even harder to log everything. I hope Python in Excel figures out how to get over those hurdles
So with a little bit of effort this has already been a thing for 2 decades.
Not entirely sure how you move from plain win32 to DCOM, and it's probably a bit more difficult than WSH, but it should be doable.
Nope, not only there is the security issue, regardless of what is promised, good luck editing those Excel files in flights, or train travels.
