Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2492#issuecomment-56477603
> Understood, this side-effect is bit dangerous. The third-package could
appear in sys.path in any order
Are you worried about a user adding a Python module whose name conflicts
with a built-in module, thereby shadowing it? I think this is a general Python
problem that can occur even without `sys.path` manipulation, which is why it's
bad to have top-level modules that have the same name as built-in ones (and
also why relative imports can be bad):
http://www.evanjones.ca/python-name-clashes.html
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
