These sort of things always seem to assume a fairly relaxed software environment.
In practice I’ve found the big corporates try hard to keep their excel files with financial data and their Python environments with pip & all those associated risks far apart. That’s if pip works at all & isn’t caught by a firewall
Most corporates, last I knew, didn't use Python outside of IT. Devs outside of IT would be using VBA.
However in Financial companies, Python and Excel have always been used together by devs and also quants.
And they tend to use Anaconda, and also like all their other package managers, they would host an in-house package repository and block the public one. That way only approved packages are used, and they only update packages as needed.
Many though have a policy of minimising Excel and rolling out formal platforms whether in-house or off the shelf, as Excel is regarded as a ongoing risk of in-accuracy as full editable at all times, lack of git/version control and so on.
>Many though have a policy of minimising Excel and rolling out formal platforms whether in-house or off the shelf, as Excel is regarded as a ongoing risk of in-accuracy as full editable at all times, lack of git/version control and so on.
Can confirm this practice in place at fortune 50 financial institutions. One in particular calls it "End-User Computing System Risk", meaning the end user created a business-critical "system" (i.e., a complex Excel file or Access database) on their own computer.
This. The amount of begging and pleading I had to do to get basic python access was insane ( long story, but boss did not believe in it ). In some organizations, things change slowly and even if I could work around some of those restrictions, doing so does not really do me any favors.