Spotfire Ideas Portal
Problem:
Currently, Python Tools just does ignore system-wide proxy settings.
(while other Spotfire client components take proxy settings from IE)
In our environment, internet is not reachable directly, only via proxy. Therefore, by default, python packages cannot be managed via python tools, because pypi repos are not available.
Workaround:
If you have admin privileges on you machine, it is possible to modify
TIBCO Spotfire (show login dialog).bat as below, by adding environment variables with a proxy settings:
set HTTP_PROXY=http://yourproxy.net:8080
set HTTPS_PROXY=http://yourproxy.net:8080
And this will make Python Tools functional.
However, most of the users do not have such permissions, and modifying bat files somewhere inside Spotfire client is not user friendly at all. Therefore, almost nobody is able to use this workaround. I've included it to illustrate nature of the problem.
Why this problem should be fixed:
Using only SPK-managed python packages is not feasible for some cases.
a) Users should have possibility to test their solutions fast, without being forced to take a long journey of requesting every new module they want to try out, to be added to the SPK packages.
b) We want to evade adding everything into the SPK package, as it will affect update time for the client. SPK package should contain only packages that are actually used by a wide list of users, not a one user who needs a lot of modules for his personal experiments.
How this may be fixed:
1) Python tools may have a checkbox for taking proxy settings from IE, just like other Spotfire client parts do.
2) Python tools may have a manual settings for proxy (like the custom statistics server URL is currently configured)
3) Python tools may have proxy settings taken from Administration manager->Preferences, (like statistics server URL currently is configured, and assigned per groups)
| Implemented in | 11.4 |
Many thanks for highlighting this issue Mikhail, and for the detailed problem description and suggested solutions. Self service access to Python packages is a core piece of our Python support and I hope we can find a solution sooner rather than later.
The workaround, as proposed by TIBCO, is not acceptable for users in our real-world. Our users do not have admin rights on their machines, and should never be expected to modify scripts or config files. This is 2020, and the bar is so much higher that what we are given. For a self-service tool, there needs to be a better way to set this up.
JP Lee