Redefining name 'wearable_id' from outer scope (line 41)
8
9class Wearable:
10
11 def __init__(self, wearable_id, wearable_secret, home_id, home_secret):12 self.wearable_id = wearable_id
13 self.wearable_secret = wearable_secret
14 self.home_id = home_idRedefining name 'home_id' from outer scope (line 43)
8
9class Wearable:
10
11 def __init__(self, wearable_id, wearable_secret, home_id, home_secret):12 self.wearable_id = wearable_id
13 self.wearable_secret = wearable_secret
14 self.home_id = home_idRedefining name 'home_secret' from outer scope (line 44)
8
9class Wearable:
10
11 def __init__(self, wearable_id, wearable_secret, home_id, home_secret):12 self.wearable_id = wearable_id
13 self.wearable_secret = wearable_secret
14 self.home_id = home_idRedefining name 'wearable_secret' from outer scope (line 42)
8
9class Wearable:
10
11 def __init__(self, wearable_id, wearable_secret, home_id, home_secret):12 self.wearable_id = wearable_id
13 self.wearable_secret = wearable_secret
14 self.home_id = home_id
Description
The local variable name hides the variable defined in the outer scope, making it inaccessible and might confuse.
Bad practice
filename = 'myfile.txt'
def read_file(filename): # This shadows the global `filename`
with open(filename) as file:
return file.readlines()
Preferred:
FILENAME = 'myfile.txt' # renamed global to UPPER_CASE as convention
def read_file(filename):
with open(filename) as file:
return file.readlines()
Bad practice
Another usual suspect of this is when you use the same parameter name inside a function as the global variable you are using. For example:
def run_app(app):
# This `app` shadows the global app...
app.run()
if __name__ == '__main__':
app = MyApp() # This is a global variable!
run_app(app)
Preferred:
To avoid this re-defining of a global, consider not defining app as a global, but inside a main() function instead:
def run_app(app):
# There is no longer a global `app` variable.
app.run()
def main():
app = MyApp()
run_app(app)
if __name__ == '__main__':
main()