Re: [PR] [SPARK-48056][PYTHON][CONNECT][FOLLOW-UP] Use `assertEqual` instead of `assertEquals` for Python 3.12 [spark]

2024-05-04 Thread via GitHub
dongjoon-hyun commented on PR #46377: URL: https://github.com/apache/spark/pull/46377#issuecomment-2094044455 Yes, it would be great like Scalastyle (Scala) and Checkstyle (Java). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] [SPARK-48056][PYTHON][CONNECT][FOLLOW-UP] Use `assertEqual` instead of `assertEquals` for Python 3.12 [spark]

2024-05-04 Thread via GitHub
nija-at commented on PR #46377: URL: https://github.com/apache/spark/pull/46377#issuecomment-2094043833 Wondering if we could get the linters or PR checks to catch this. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

Re: [PR] [SPARK-48056][PYTHON][CONNECT][FOLLOW-UP] Use `assertEqual` instead of `assertEquals` for Python 3.12 [spark]

2024-05-03 Thread via GitHub
dongjoon-hyun closed pull request #46377: [SPARK-48056][PYTHON][CONNECT][FOLLOW-UP] Use `assertEqual` instead of `assertEquals` for Python 3.12 URL: https://github.com/apache/spark/pull/46377 -- This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [PR] [SPARK-48056][PYTHON][CONNECT][FOLLOW-UP] Use `assertEqual` instead of `assertEquals` for Python 3.12 [spark]

2024-05-03 Thread via GitHub
dongjoon-hyun commented on PR #46377: URL: https://github.com/apache/spark/pull/46377#issuecomment-2093992824 Let me merge this to recover the Python CI. -- 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

[PR] [SPARK-48056][PYTHON][CONNECT][FOLLOW-UP] Use `assertEqual` instead of `assertEquals` for Python 3.12 [spark]

2024-05-03 Thread via GitHub
dongjoon-hyun opened a new pull request, #46377: URL: https://github.com/apache/spark/pull/46377 … ### What changes were proposed in this pull request? ### Why are the changes needed? ### Does this PR introduce _any_ user-facing change?