Have a look at Adding keymaps to src blocks by John Kitchin. It does more than you want. You can edit src blocks as you would normally edit code of that type. There is a link to a file in org-mode that you can download and evaluate to make this available for you. You will need to adapt the recipes he gives for your needs.
The major problem is defining the ...
If you want to configure it in .org format instead of Lisp, so that you can keep your property declarations the between files as in a specific file, then you can use the #+SETUPFILE setting:
The setup file or a URL pointing to such file is for additional in-buffer settings. Org loads this file and parses it for any settings in it only when Org opens the ...
It depends on what you want to do with the tables of course, but assuming that you want to produce generic Org mode tables that can be exported in the standard way, you will have to make the python block produce the structure that Org Babel expects in order to produce the generic Org mode table. That structure is a list of lists: first a list for the headers,...
Use the header argument :results silent to suppress the #+RETULTS: output of a single source block. With the header argument, the results are shown in the message buffer instead.
Minimal working example:
#+BEGIN_SRC emacs-lisp :results silent
"This string goes to the message buffer instead of popping up below the source block."
How you ...
You could add the non-breaking space as a new font-lock keyword to python-mode:
;; I'm defining a new face, though any face with underline should work
'((t :inherit default :underline t))
"My non-breaking space face.")
(font-lock-add-keywords 'python-mode '(("\u00a0" . 'my-nobreak-space)))
You can define header vars in various ways, e.g. globally:
#+PROPERTY: header-args :var COMPILE_FLAGS="-std=c99 -Wall -Werror -pedantic"
or in a property drawer in a specific section:
:header-args: :var COMPILE_FLAGS="-std=c99 -Wall -Werror -pedantic"