Importing naming collisions can cause risks
This code insight Counts one violation each time a name collision is encountered: pattern 1: from xxx import yyy from zzz import yyy pattern 2: from xxx import yyy as zzz from aaa import bbb as zzz pattern 3: import yyy as zzz import bbb as zzz badfrom numpy import floor
from numpy import array
from math import floor # Overwrites already imported floor function
good
from numpy import floor as np_floor
from numpy import array as np_array
from math import floor # Does no longer overload numpy's floor function
Why you should care
As the last import will overload previous one's, importing two objects with the same name can lead to unpredictable or even catastrophic results.Business Impacts
[nz_btn text="Production Risk" target="_self" animate="false" animation_type="ghost" color="pink" size="small" shape="rounded" type="normal" hover_normal="opacity" hover_ghost="fill" link="http://casthighlight.wpengine.com/category/product/indicators-methodology/innovation/" icon="icon-office"]CAST recommendations
References
https://www.quantifiedcode.com/knowledge-base/correctness/Resolve%20import%20naming%20collision/kJ13jArnAbout 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.
For reference only. For the complete details please refer the original article
https://doc.casthighlight.com/alt_importconflict-avoid-naming-collision-with-imports/
https://doc.casthighlight.com/alt_importconflict-avoid-naming-collision-with-imports/
Comments