GitHub user mnazario opened a pull request:

    https://github.com/apache/spark/pull/6439

    [SPARK-7899][PYSPARK] Fix Python 3 pyspark/sql/types module conflict

    This PR makes the types module in `pyspark/sql/types` work with pylint 
static analysis by removing the dynamic naming of the `pyspark/sql/_types` 
module to `pyspark/sql/types`.
    
    Tests are now loaded using `$PYSPARK_DRIVER_PYTHON -m module` rather than 
`$PYSPARK_DRIVER_PYTHON module.py`. The old method adds the location of 
`module.py` to `sys.path`, so this change prevents accidental use of relative 
paths in Python.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mnazario/spark feature/SPARK-7899

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/6439.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #6439
    
----
commit 673528fc49223198e52759906340040c24a481ac
Author: Michael Nazario <[email protected]>
Date:   2015-05-27T15:12:15Z

    Move _types back to types

commit 6ee4f756564e43563896dfaac35da1c8c09fd2c6
Author: Michael Nazario <[email protected]>
Date:   2015-05-27T15:13:56Z

    Change test scripts to use "-m"
    
    By changing to use "-m", the directory which contains the test file
    (e.g. python/pyspark/sql/types.py) will not be added to sys.path.

commit bb8b04db418922ac43d814dc5967e61fa03c99c4
Author: Michael Nazario <[email protected]>
Date:   2015-05-27T18:05:14Z

    Make doctests consistent with other tests

----


---
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]

Reply via email to