Re: Executable standalone *.pyc after inserting "#!/usr/bin/python" or other options

On Jan 15, 8:32 am, schmeii wrote: > On Jan 14, 10:55 pm, epsilon wrote: > > > All: > > > I've been playing with "Lua" and found something really cool that I'm > > unable to do in "Python". With "Lua", a script can be compiled to byte > > code using "luac" and by adding "#!/usr/bin/lua" at the to

Re: Executable standalone *.pyc after inserting "#!/usr/bin/python" or other options

On Jan 14, 10:55 pm, epsilon wrote: > All: > > I've been playing with "Lua" and found something really cool that I'm > unable to do in "Python". With "Lua", a script can be compiled to byte > code using "luac" and by adding "#!/usr/bin/lua" at the top of the > binary, the byte code becomes a singl

Re: Executable standalone *.pyc after inserting "#!/usr/bin/python" or other options

> This works great! Do you or anyone else have information on how to do > the same thing for Windows and/or Solaris. On Windows, just associate the .pyc extension with Python - the standard installation will already do that. On Solaris, I don't think something like this is supported. Regards, Ma

Re: Executable standalone *.pyc after inserting "#!/usr/bin/python"or other options

On 01/15/10 09:33, Martin v. Loewis wrote: > > P.S. The approach you present for Lua indeed does not work for > Python. Actually the approach should work, though with a little workaround; you can write your wrapper (e.g. #!/usr/bin/mypython) that simply strips the first line and pass the file to

Re: Executable standalone *.pyc after inserting "#!/usr/bin/python" or other options

On Jan 14, 5:33 pm, "Martin v. Loewis" wrote: > > I've been playing with "Lua" and found something really cool that I'm > > unable to do in "Python". With "Lua", a script can be compiled to byte > > code using "luac" and by adding "#!/usr/bin/lua" at the top of the > > binary, the byte code become

Re: Executable standalone *.pyc after inserting "#!/usr/bin/python" or other options

> I've been playing with "Lua" and found something really cool that I'm > unable to do in "Python". With "Lua", a script can be compiled to byte > code using "luac" and by adding "#!/usr/bin/lua" at the top of the > binary, the byte code becomes a single file executable. After I found > this trick,

Executable standalone *.pyc after inserting "#!/usr/bin/python" or other options

All: I've been playing with "Lua" and found something really cool that I'm unable to do in "Python". With "Lua", a script can be compiled to byte code using "luac" and by adding "#!/usr/bin/lua" at the top of the binary, the byte code becomes a single file executable. After I found this trick, I r