Production RiskSoftware ResiliencyProgramming Best Practices
Production Risk
Wildcard(*) imports can increase production risks.
This code insight counts one violation each time a wildcard import is used.
Violations pattern is:
import *
from xxx import *
Why you should care
In general, import statements should be as specific as possible and you should only import what you need. When “
from module import *" is used, you are implicitly loading all locals of the imported module into and over the importing module. This has two disadvantages:
- first, you might unintentionally overload already imported objects.
- Second, it becomes difficult to detect undefined names in the program that imported the module.
Business Impacts
CAST recommendations
References
https://www.quantifiedcode.com/knowledge-base/maintainability/Avoid%20using%20wildcard%20%28%2A%29%20imports/3Q3eTYIU
About CAST and Highlight’s Code Insights
Over the last 25 years, CAST has leveraged unique knowledge on software quality measurement by analyzing thousands of applications and billions of lines of code. Based on this experience and community standards on programming best practices, Highlight implements hundreds of code insights across 15+ technologies to calculate health factors of a software.
See featuresHow it works