Talking with some Argisscripters, I better understand their problem.
For them, Python is not an independent language, but a subset of
ArcGIS. They are limited by the default modules that come with Python-
ArcGIS. If they want to publish on Arcscript, they can not use a
module "unknown" by others (like shapely). The script must be
consistent with the original configuration, since the purpose is to be
able to access the scripts through, for example, ArcToolbox and not to
make the "best possible" script. They are not interested in Python ss
but by the result of the script in ArcGIS. I can understand but it is
unfortunate and limiting given the wealth and power of Python. I guess
it's the same thing for other languages (.net, vba ...).
In practice, it resembles the art to provide a feeling of opening
while closing all the opportunities that are not from ESRI.
