Alexander Ponomarev

We need to think how automatic testing of shellpy functions will be done and create a couple of examples of tests. Also some small article on it is needed in...

Now it is hardcoded in `header_root.tpl` with pretty generic `#!/usr/bin/env python` . But maybe it should be possible to configure it.

Here is an example ^CTraceback (most recent call last): File "/tmp/shellpy_root/root/cr/scripts/monitor.py", line 272, in Traceback (most recent call last): File "/usr/bin/shellpy", line 9, in load_entry_point('shellpy==0.4.5', 'console_scripts', 'shellpy')() File "/usr/lib/python2.7/site-packages/shellpython/shellpy.py", line...

Recompile files for new version of shellpy

2

Now .spy files are not reprocessed if the version of shellpy itself changes. We don't even have this version in shellpy. We have to make it.

What if user wants /bin/bash for shell and not /bin/sh? Maybe give him/her such ability?

Now there are no linesep in the end of each line. Maybe user would like to have them. Can and should we add this ability?

For some cases it is more convenient just to get string of stdout from the command executed, not result. We need to think about it. Is it worth it to...

Now grave accents (`) are forbidden for shell commands. We need to think how to allow them. Maybe with some escaping.

What if two shellpy processes will write one preprocessed file to cache in one time?

Now stdout in non interactive mode is not printed immediately, it waits when the process finishes. It would be great to see stdout, stderr as soon as it comes.