I vote for none. A quick check of the python package index shows almost 25,000 Python modules available. Where would the line be drawn.
What I would like to see is for ESRI to install Python using the standard Python installation directories, then install ArcPy as just another package under the site-packages directory. That way all the off the shelf Python stuff works just fine.
I'm still on 10 so maybe 10.1 fixes this issue.
Pandas sounds like a really good idea.
Talking with the arcgis geoprocessing team at UC yesterday -- they said that ArcGIS Pro beta 4 (python 3.4 of course) is shipped with an "internal" python install used by the app and a separate installer with python 3.4 that includes what Bill M was calling the "sci stack" which includes the modules used by esri (numpy, matplotlib etc) plus a another 300MB of so of other scientific modules (I think he said scipy, pandas, netCDF4) that aren't used by Esri but are useful to us.
The idea is they don't have the footprint there in a standard Pro install, but the group of users that will be installing this separate python installer are developers and can deal with the footprint and any issues they run into with these modules and not blame Esri. 🙂
This is great news. Hope there is a blog post coming from the arcpy crew soon! Maybe on the cafe?
Another option that would be great is for Esri to simply include pip and Easy Install. This would make it easy for people to write scripts in Python or even BAT files that could add any 3rd party libraries needed. Most Python distributions (excluding windows) come with pip and Easy Install ready to go, it seems like something Esri could add that would make it more "pythonic" and much easier for anyone to require additional libraries or dependencies.
I would support adding pip and/or easy_install rather than including too many third party libraries.
Using pip or easy_install is super easy and quick to install whatever library you might need.
I'm not sure just using pip will solve our problems with third-party packages... many users have run into binary compatibility issues on the Windows platform where a .dll the Python library has a conflict with the .dll ArcGIS Desktop is using...
Cannot import pandas - ArcGIS 10.1 and also with netCDF4.
And of course we will be using Desktop / 2.7 for a while yet.
The ArcHydro team is currently distributing a simple .exe executable for netCDF4 that does work with ArcGIS Desktop using a .exe generated using distutils I'd guess...
More guidance would be very helpful!