Github user Stibbons commented on the issue:
https://github.com/apache/spark/pull/14963
Thanks both of you for your reviews.
It also fix the version of sphinx for documentation build during the
`lint-python` My point of view is that for **application**, all versions of
tools used to build should be frozen (in `requirements.txt`), to ensure full
reproductibility. Upgrading any tool from version A to version B should be as
much controlled as any other change in the source code, since it may have
unwanted behavior. Pylint adds and remove checks from time to time and you
don't want you code to stop building when pylint release a new version on Pypi,
without a easy way to go back to a known state.
I am ready to submit new PR with currently-ignored pylint checks :)
---
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]
