Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/8318
Ah that makes more sense. Sort of the default way of going about this would
make it so that pip installing PySpark puts pyspark on the path of the user,
but if they explicitly call a different ./bin/pyspark or ./bin/spark-submit we
prepend our own Python path before the existing ones so that one will have
precedence over the pip installed one. It seems like the is the behaviour most
people would expect (and its also probably the easiest to implement) :)
---
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]
