Currently the build script copies all the source code in one place and runs the pylint scan on it since the number of python files is small. Since the number of files will increase in future, it is better to scan the code tree and list out all the python files and then run pylint scan on them.
I fear it's not as simple as you described it. Pylint also checks imports and therefore must be able to import packages and modules. But the pki namespace is split into two source trees base/common/python and base/server/python. The pki base package can not be turned into a namespace package because it contains code.
Patch 007 posted on pki-devel for review.
Metadata Update from @kaskahn: - Issue assigned to cheimes - Issue set to the milestone: UNTRIAGED
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1265
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.