Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #2184
| From | CM <cmpython@gmail.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Directly Executable Files in Python |
| Date | 2011-03-29 10:19 -0700 |
| Organization | http://groups.google.com |
| Message-ID | <a9c433bd-4d45-4478-ab8c-e2a144530d02@b13g2000prf.googlegroups.com> (permalink) |
| References | <1364b9ed-56c8-40ca-98f9-576900fb2caf@glegroupsg2000goo.googlegroups.com> <mailman.1357.1301370909.1189.python-list@python.org> <A2dkp.11$2s6.9@newsfe13.iad> |
> it has to be reproducing the byte code > interpreter in the code segment and the byte code in the data segment... > so that each .exe file created by said process is actually loading an > entire copy of at least the byte code interpreter with each program > "compiled" ... Yes, if you think of it as a handy packager and not a compiler, it makes sense. > can't be very efficient?? How do you define efficient? All I know is that it works well. You click on the .exe and a moment later you are running the application despite not having Python installed on your computer. I'm grateful for its existence. Che
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Directly Executable Files in Python CM <cmpython@gmail.com> - 2011-03-29 10:19 -0700
csiph-web