elbowz/xbmc.service.pushbullet — pull request #17 by ruuk (2014-11-09 20:33:57+00:00)
Title: Remove wild import from common and user full paths instead

Would it be OK with you if we started doing this?

Reasons:
* Wild imports pollute the namespace (ex. I could accidentally define a method that replaces one imported from common)
```python
from lib.common import *

# Now logging is broken, and it's not obvious unless you know that log is in common
def log(msg):
pass
```
* It's easier to know where the method came from (especially helpful with more than one author)
```python
from lib import common

common.log("This method is from common")

from lib.common import *
from example import *

log("Where did I get this method")
```
* My editor can't warn me if I incorrectly spell a method name, because anything I type could be in the wild import

```python
from lib.common import *
flyingMonkeys("My editor has no problem with flyingMonkeys, it assumes it was imported from lib.common")

from lib import common
flyingMonkeys("My editor warns me that flyingMonkeys is not defined")
```