Fix local path new directory

[milin]

Fixes the following current issues with importanize.

1. Running importanize on a newly created directory with a python file gives the following error

Error running importanize
Traceback (most recent call last):
  File "/Users/e002582/.virtualenvs/dtweb/lib/python2.7/site-packages/importanize/__main__.py", line 387, in main
    run(p, config, args)
  File "/Users/e002582/.virtualenvs/dtweb/lib/python2.7/site-packages/importanize/__main__.py", line 311, in run
    return run(text, config, args, source)
  File "/Users/e002582/.virtualenvs/dtweb/lib/python2.7/site-packages/importanize/__main__.py", line 261, in run
    organized = run_importanize_on_text(source, config, args)
  File "/Users/e002582/.virtualenvs/dtweb/lib/python2.7/site-packages/importanize/__main__.py", line 226, in run_im
portanize_on_text
    lines.pop(line_number)
IndexError: pop from empty list

2. Running importanize without giving the full path freezes importanize (gets stuck in the while loop). So, if theres a project configuration return it in such cases.

[coveralls]

Coverage remained the same at 100.0% when pulling c76a481 on milin:fix_local_path_new_directory into 2e17d19 on miki725:master.

[coveralls]

Coverage remained the same at 100.0% when pulling a7d09a2 on milin:fix_local_path_new_directory into 2e17d19 on miki725:master.

[miki725]

not sure when can this freeze here? this should go up the folder tree until root is encountered at which point loop should exit. what am I missing?

[milin]

Happens in cases when theres no root prefix for the specified file. for e.g
importanize utils/common.py.

path value lingers at PosixPath('.')

[miki725]

ah, this method is called without resolving the path. oops

[miki725]

thanks. this bombed on on all empty files. introduced this recently