On 7/03/2011 4:34 PM, Nick Coghlan wrote: > On Mon, Mar 7, 2011 at 3:19 PM, Mark Hammond<skippy.hammond at gmail.com> wrote: >> Without putting too much thought into it, I think a simple scheme could work >> where the path must either be "/usr/bin/python[23]?" or a fully-qualified >> path to a Python executable. IIUC, this should allow most scripts to have a >> shebang line that "does the right thing" on *nix and Windows systems while >> still offering maximum flexibility on Windows. > > Such a scheme should be able to handle "/usr/bin/env python2" and > variants as well. Agreed - that is just my ignorance showing through :) Cheers, Mark
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4