s/compile/execute when talking about Python

The word 'compile' is just misleading here.

README.md

@@ -181,7 +181,7 @@ using the matched rule and runs it. Rules enabled by default are as follows:
 * `open` – prepends `http` to address passed to `open`;
 * `pip_unknown_command` – fixes wrong pip commands, for example `pip instatl/pip install`;
 * `python_command` – prepends `python` when you trying to run not executable/without `./` python script;
-* `python_compile` – appends missing `.py` when compiling and running Python files;
+* `python_execute` – appends missing `.py` when executing Python files;
 * `quotation_marks` – fixes uneven usage of `'` and `"` when containing args'
 * `rm_dir` – adds `-rf` when you trying to remove directory;
 * `sl_ls` – changes `sl` to `ls`;

tests/rules/test_python_execute.py

@@ -1,5 +1,5 @@
 import pytest
-from thefuck.rules.python_compile import match, get_new_command
+from thefuck.rules.python_execute import match, get_new_command
 from tests.utils import Command
 
 

thefuck/rules/python_execute.py

@@ -1,4 +1,4 @@
-# Appends .py when compiling python files
+# Appends .py when executing python files
 #
 # Example:
 # > python foo