News for hackers. Stuff that matters.
Re:Excel team considering Python as scripting language: aski... by smortaz on Thursday December 14, 2017 @04:21PM (#15927185)
Clickable Link:

https://excel.uservoice.com/forums/304921-excel-for-windows-...

[disclaimer+bias: on Python team @ msft & would love to see this happen!]

Re:Excel team considering Python as scripting language: aski... by askvictor on Thursday December 14, 2017 @05:03PM (#15927580)
Interestingly, the survey doesn't seem to consider education as a use-case of this - has your team considered that aspect? Spreadsheets are the most common way that school students are introduced to programming, and the only 'programming' that a lot of teachers (and others) do. There are heaps of reasons for this, but any even moderate programming (beyond very simple operations) in a spreadsheet sucks. Something like this (if it's easy out of the box) could revolutionise programming education (and data education for that matter).

Are there plans to get this working with the Excel web-app, or just the desktop version? I'm just having a daydream about Excel, Juypter notebooks, and OneNote Class notebooks...

Re:Excel team considering Python as scripting language: aski... by smortaz on Thursday December 14, 2017 @05:14PM (#15927680)
That's a very good point! I hope you provided that input :).

Our team provides a free service for anyone to run Jupyter Notebooks on Azure. It's currently a big hit with the Edu crowd. We're seeing lots & lots of universities upload & teach courses on it. eg:

http://notebooks.azure.com/richie

There's also an Intro to Python notebook on the front page.

Hopefully the Excel team will consider Jupyter integration, esp for the web-app version! You're right that it's a killer combo. Check out xlwing's video on using Excel+Jupyter - it's brilliant.

Re:Excel team considering Python as scripting language: aski... by rmbeard on Friday December 15, 2017 @12:48AM (#15929900)
I think we will see and are already seeing a move away from using spreadsheets in Education, there are simply much better solutions out there now. Jupyter notebooks being one which allow reading and writing to Excel files. The interface of these is far superior for educational purposes than a spreadsheet. I've already dropped Excel for this reason.
Re:Excel team considering Python as scripting language: aski... by bdowling on Thursday December 14, 2017 @04:46PM (#15927403)
So, would this imply numpy and scipy support in Python for Excel? How about support for Excel worksheets within Jupyter notebooks?
Re:Excel team considering Python as scripting language: aski... by smortaz on Thursday December 14, 2017 @04:59PM (#15927537)
That's for the Excel team to decide. My personal hope is that they'll offer as a base:

* Python 3

* Numpy, SciPy, Pandas, Matplotlib, Altair, ...

* Pythonic bindings for Excel APIs (sheets, etc etc)

* VSCode's Python Editor + Debugger built in

* Some sort of conda based env/pkg mgmt

* Right-click, "Open in Jupyter" (data/code)

* <your wish here>

Re:Excel team considering Python as scripting language: aski... by auxym on Thursday December 14, 2017 @05:23PM (#15927758)
Transparent access to Excel tables as Pandas Dataframes would be so, so very awesome.

I mean, MS implemented these really nice Tables in excel, but then left us no way to easily query them with something like SQL.

Re:Excel team considering Python as scripting language: aski... by garyclarke27 on Friday December 15, 2017 @01:57AM (#15930125)
I agree, SQL in Excel would be awesome, Index Match everywhere is a right pain to maintain - to replicate foreign keys. Its amazing what you can do with Sumifs and Countifs, but SQl is better. VBA is OK but NO search across modules makes it such a pain just to find your code, I wish VBA had better support for UDFs so that they can appear the same to users, as built in functions with tooltips. MS have done a really bad job of incorporating Power Pivot, it’s confusing and doesn’t feel like a natural part of Excel. I don’t like Pivot Tables they are too Dynamic and a pain too format.
Re:Excel team considering Python as scripting language: aski... by govert on Friday December 15, 2017 @05:00AM (#15930757)
You can add-in IntelliSense for VBA functions using the (free) Excel-DNA IntelliSense extension. See this detailed write-up by Charles Williams: https://fastexcel.wordpress.com/2016/10/07/writing-efficient...
Re:Excel team considering Python as scripting language: aski... by mistermann on Thursday December 14, 2017 @11:56PM (#15929741)
Someone posted a link to a really nice 3rd part addin on the reddit thread, on mobile so can't find the link unfortunately but was very well done. Shame on Microsoft for half-assing Excel for the last decade.
Re:Excel team considering Python as scripting language: aski... by auxym on Friday December 15, 2017 @07:25AM (#15931285)
Possibly querystorm, in case anyone is looking for it. It did look interesting last time I looked at it, but I've never tried it.
Re:Excel team considering Python as scripting language: aski... by mistermann on Friday December 15, 2017 @07:36PM (#15936549)
Re:Excel team considering Python as scripting language: aski... by breatheoften on Thursday December 14, 2017 @11:33PM (#15929688)
Doesn’t pandas.read_excel provide this?
Re:Excel team considering Python as scripting language: aski... by dragonwriter on Thursday December 14, 2017 @06:49PM (#15928499)
Well, there is PowerPivot...
Re:Excel team considering Python as scripting language: aski... by vvanders on Thursday December 14, 2017 @05:14PM (#15927676)
Yeah, matplotlib, scipy and numpy are kinda no-brainers there.
Re:Excel team considering Python as scripting language: aski... by breatheoften on Thursday December 14, 2017 @11:34PM (#15929691)
Please not matplotlib ... are we really stuck with matplotlib forever ..?
Re:Excel team considering Python as scripting language: aski... by vvanders on Friday December 15, 2017 @01:36AM (#15930046)
If you've got better suggestions I'm all ears. I've found it pretty great for debugging and being able to understand data in a rapid manner.
Re:Excel team considering Python as scripting language: aski... by disgruntledphd2 on Saturday December 16, 2017 @06:19AM (#15939004)
ggplot2. Simply better in every way. Hell, even base R is better than matplotlib. Full disclosure: I hate matplotlib so very, very much.
Re:Excel team considering Python as scripting language: aski... by ateesdalejr on Thursday December 14, 2017 @06:03PM (#15928113)
No, watch them pump out some horribly supported python library .
Re:Excel team considering Python as scripting language: aski... by odonnellryan on Thursday December 14, 2017 @04:30PM (#15927255)
So what's the strategy here re: security? I assume it'd be a fairly stripped-down version of Python ... or will you just design the UI to say "you probably shouldn't execute files from people you don't know" etc?
Re:Excel team considering Python as scripting language: aski... by esmi on Thursday December 14, 2017 @04:40PM (#15927355)
From a security point of view how is embedding python different from embedding Visual Basic? This is not my area of expertise so I’m genuinely curious.
Re:Excel team considering Python as scripting language: aski... by Groxx on Thursday December 14, 2017 @04:57PM (#15927519)
Potentially different. .NET allows signed binaries / libs / a fully signed execution context, Python has nothing equivalent AFAIK.
Re:Excel team considering Python as scripting language: aski... by auxym on Thursday December 14, 2017 @05:25PM (#15927773)
Excel VBA is not .Net though. It's plain old VB code in text files inside the .xlsx, and you just have to trust it (or not).
Re:Excel team considering Python as scripting language: aski... by Groxx on Thursday December 14, 2017 @05:56PM (#15928068)
Aaah. Then probably about the same, yea :) Maybe less of a nightmare around dependencies than the pip world...?
Re:Excel team considering Python as scripting language: aski... by davb on Thursday December 14, 2017 @04:39PM (#15927346)
I’d rather full fat Python but heavily sandboxed with some form of firewall. “Do you want to allow 2018_Stock_Report_Q1.xlsp to connect to api.erp.corp.mycompany.com?”. Codesigning with my something under my corp CA, manage permissions via Group Policy and let users, on a per-endpoint or per-permission basis, authorise things like filesystem access, network connections, etc.
Re:Excel team considering Python as scripting language: aski... by smortaz on Thursday December 14, 2017 @04:38PM (#15927341)
Challenges exist & will have to be looked at for sure. Incidentally, one of the guys on our team just a gave talk on his PEP for "Secure" Python:

https://www.python.org/dev/peps/pep-0551/

There's a YT talk as well.

Re:Excel team considering Python as scripting language: aski... by Nullabillity on Thursday December 14, 2017 @04:32PM (#15927285)
> @ msft

Well, I guess that explains why you care about Office in 2017.

Re:Excel team considering Python as scripting language: aski... by canadianwriter on Thursday December 14, 2017 @04:46PM (#15927402)
That and the fact that the vast majority of companies use Office...
Re:Excel team considering Python as scripting language: aski... by cm2187 on Thursday December 14, 2017 @06:33PM (#15928370)
Which is also why it is surprising that Microsoft has spent so little time on office in 20 years. Outside of changing the colors regularly, there has been very few new significant functionalities between Office 2003 and Office 2016. And opening the VBA IDE is a nasty reminder.

I'd argue large companies are still running Windows because of Office. The cost of retraining people, redesigning all of these user processes and converting all those documents would be massive. Whereas most new corporate applications in the last 5 years have been mostly web based.

So I am surprised Microsoft under-invest in what is they main strategic lock-in in the juicy enterprise market.

Re:Excel team considering Python as scripting language: aski... by taspeotis on Thursday December 14, 2017 @06:56PM (#15928550)
Between 2003 and 2016 they took some massive desktop applications and put versions of them on the web and mobile...
Re:Excel team considering Python as scripting language: aski... by toyg on Thursday December 14, 2017 @08:40PM (#15929072)
> very few new significant functionalities between Office 2003 and Office 2016

The first release to feature the Ribbon, arguably one of the all-time major changes in Office, was 2007. That took quite a bit for most users to get used to.

An Office suite is not where you add experimental features for the hell of it. People use it to get the job done in so many different scenarios, any change will significantly impact entire industries.

Office programs are the "lawyers" and "accountants" of the software world: their work has been more or less the same since they existed, and any major change to them is a basically societal upheaval, so their approach will always be naturally conservative.

Re:Excel team considering Python as scripting language: aski... by cm2187 on Friday December 15, 2017 @03:16AM (#15930374)
Reshuffling buttons when they added ribbon is what I would classify as "changing the color", not really a new functionality.

There are many things lawyers, bankers, consultants and accountants would need that Office doesn't do. Linking a spreadsheet to a powerpoint document is a nightmare right now. Linking spreadsheets between them too. There should be a way to express a UDF as a spreadsheet so that people who can't code could create their own UDF. I love Apple's Number canvas approach, where a sheet is not a grid but a canvas on which you can add grids or charts, and they overflow with a scrollbar. Etc.

There are lots of new functionalities they could add that would make people's life better. Instead these products barely evolved in 20 years. Click the "fx" button in excel 2016 and you will get the same non resizable dialog box with a tiny listbox and a search box that doesn't search anything than in Office XP.

Re:Excel team considering Python as scripting language: aski... by bluedino on Thursday December 14, 2017 @08:10PM (#15928948)
If you think about it, only 20% if employees can use office at a medium to high level anyways - a lot less people to retrain. The rest are "I click this button then do this thing"