Mailman 3 October 2019 - code-quality

Instructing Pylint to find a module ?
by CrestChristopher Nov. 7, 2019

Nov. 7, 2019

Hi, I'm hoping someone can help. I want to know what setting within the|.pylintrc| file is the correct setting for pylint to find a module for linting ? Thank You Christopher

3 2

What would be the recommended way to execute pylint plugins tests ?
by Alexander Todorov Oct. 30, 2019

Oct. 30, 2019

Looking at https://github.com/PyCQA/pylint-django/issues/250 and https://github.com/PyCQA/pylint/commit/33b8185a455c1686d038258697bb93005f24… I am wondering what would be the recommended way to keep reusing test_functional.py from pylint ? The only thing I can come up with is git clone inside CI or locally pylint-django's test suite would be able to use this module. That would work but looks kind of ugly. Any other suggestions ? -- Alex

1 0

adapting code quality tools to non-traditional situation
by Mats Wichmann Oct. 18, 2019

Oct. 18, 2019

I'm fishing for pointers here, this isn't really a specific question I'm expecting a magic answer to - though one such would certainly be gratefully accepted :) I work on the scons project - scons is a software build system tool, which is controlled by configuration scripts which are written in Python; scons is itself written in Python as well. It would be nice to have the ability for users to be able to check their configuration scripts for errors, poor programming style, etc. We certainly get enough questions about people who have actually botched the Python in their scripts, rather than finding errors in scons itself. However - scons is not a Python module that you import to make its methods and attributes visible. Rather you run scons the program, and it finds the build scripts and interprets them using Python within the context of the already running program (i.e. exec(compile(scriptdata, ... ). That means if you run, for example, pylint on a perfectly valid script, it will certainly complain, because of the use of the scons "API" which will be well known during the run context but completely unknown to a static checker tool that does not operate in that context. So the scons model seems to be at odds with how all of the checkers I've looked at operate. I'm thinking that any possible way forward would be to have the checker operate in the scons context - that is, rather than expecting to run it from the command line, it would be activated by something like "scons --check". Anybody have any ideas how one could adapt something to this model? How would one teach a checker what it needs to know about the API? Or is it simpler than I'm making it out to be? thanks -- mats

3 4

On the topic of Codes of Conduct
by Ian Stapleton Cordasco Oct. 6, 2019

Oct. 6, 2019

Hi everyone, A few days ago, there was a thread where a member brought up the code of conduct to another member. In particular, as this list is provided by the Python Software Foundation, we are observing the PSF Code of Conduct. We are all expected to observe the code of conduct and I would expect that people would feel safe raising violations of the code of conduct. Furthermore, people shouldn't feel as if being asked to observe the Code of Conduct is a threat or a violation of the Code of Conduct. The Code of Conduct exists to ensure that everyone feels safe participating in this community. Granted, it's not a particularly active community but it should be capable of representing the global Python community. If having to observe the Code of Conduct offends you or makes you feel personally unsafe, perhaps you need to think long and hard about why that is. If you think that you can't abide by the Code of Conduct, you are not required to continue to subscribe to this list or participate in its discussions. To be clear, I have no intention to litigate the interaction from a few days ago. No complaint seems to have been made. Further, there's no intent to entertain discussion of moving this list off of PSF infrastructure to bypass a Code of Conduct as any list with me as a moderator or administrator will require a CoC. Cheers, Ian

2 1