Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

how to make a python or perl script portable to both linux and windows?

I was wondering how to make a python script portable to both linux and windows?

One problem I see is shebang. How to write the shebang so that the script can be run on both windows and linux?

Are there other problems besides shebang that I should know?

Is the solution same for perl script?

Thanks and regards!

like image 350
Tim Avatar asked Jun 11 '10 04:06

Tim


2 Answers

Windows will just ignore the shebang (which is, after all, a comment); in Windows you need to associate the .py extension to the Python executable in the registry, but you can perfectly well leave the shebang on, it will be perfectly innocuous there.

There are many bits and pieces which are platform-specific (many only exist on Unix, msvcrt only on Windows) so if you want to be portable you should abstain from those; some are subtly different (such as the detailed precise behavior of subprocess.Popen or mmap) -- it's all pretty advanced stuff and the docs will guide you there. If you're executing (via subprocess or otherwise) external commands you'd better make sure they exist on both platforms, of course, or check what platform you're in and use different external commands in each case.

Remember to always use /, not \, as path separator (forward slash works in both platforms, backwards slash is windows-only), and be meticulous as to whether each file you're opening is binary or text.

I think that's about it...

like image 168
Alex Martelli Avatar answered Oct 16 '22 17:10

Alex Martelli


Make sure you don't handle files and directories as strings and simply concatenate them with a slash in between. Perl:

$path = File::Spec->catfile("dir1", "dir2", "file")

Remember that Windows has volumes:

($volume, $path, $file) = File::Spec->splitpath($full_path);
@directories = File::Spec->splitdir($path);

When running other programs, try to avoid involving the shell. In Perl, when you run a command with the system function, you can easily get it wrong with:

$full_command = 'C:\Documents and Settings/program.exe "arg1" arg2'; # spaces alert!
system($full_command);

Instead, you can run system with a list as argument: the executable and the arguments being separate strings. In that case, the shell doesn't get involved and you don't get into trouble regarding shell escaping or spaces in file names.

system('C:\Documents and Settings/program.exe', 'arg1', 'arg2');

There's a bunch of portability nits documented in the perlport manual.

like image 35
tsee Avatar answered Oct 16 '22 18:10

tsee