HyukjinKwon commented on a change in pull request #24898: [SPARK-22340][PYTHON] Add a mode to pin Python thread into JVM's URL: https://github.com/apache/spark/pull/24898#discussion_r339889301
########## File path: python/pyspark/tests/test_pin_thread.py ########## @@ -0,0 +1,156 @@ +# +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +# +import os +import time +import random +import threading +import unittest + +from pyspark import SparkContext, SparkConf + + +class PinThreadTests(unittest.TestCase): + # These tests are in a separate class because it uses + # 'PYSPARK_PIN_THREAD' environment variable to test thread pin feature. Review comment: Yeah, agree. I don't think there's kind of a consistent rule for that. I usually just write comments when the contents are not directly related to the description of the class or method. e.g.) "this class contains tests blah blah" -> docstring, "this test class don't use something because blah blah" -> comments . But I guess it's just me :-). Actually I don't bother docstrings often in test classes because it's unlikely the docstrings in class are read via pydoc (e.g., `help(PinThreadTests)` in Python shall) or generated as a doc. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
