I know it's been a long while since this thread has been handled, but
maybe this is a final solution to your problem (if not yet resolved):
http://www.py2exe.org/index.cgi/SingleFileExecutable
Especially the last setup.py file results in only one exe which contains
*all* the necessary stuff
On Jan 1, 7:05 pm, Geert Vancompernolle geert.discussi...@gmail.com
wrote:
I know it's been a long while since this thread has been handled, but
maybe this is a final solution to your problem (if not yet resolved):
http://www.py2exe.org/index.cgi/SingleFileExecutable
Especially the last
I am objecting to embeddeding metadata in data.
I think we were just looking a different aspects of the elephant ;-)
I think you are right on both counts.
Given current filesystems, I like the #! method. I tend to like
approaches that have very low entrance access fees and can scale up.
Bengt Richter wrote:
I don't know what pythonw.exe does with std i/o that hasn't been intercepted,
but I would think it could be handy to have it force a console window, and maybe
have a pythonw.exe command line option to dump either or both stdout and stderr
silently. That way by default you'd
I think of it like the ''.join semantics. The object knows best how
to
handle join (even if it looks wierd to some people). In the #! case,
the program knows best how to start itself.
This I don't understand ;-)
With ','.join(['a','b','c'])You rely on what wants to join the
sequence to
On 22 Apr 2005 21:16:04 -0700, [EMAIL PROTECTED] wrote:
I think of it like the ''.join semantics. The object knows best how
to
handle join (even if it looks wierd to some people). In the #! case,
the program knows best how to start itself.
This I don't understand ;-)
With
click on my computer
Then select tools-folder options-File Types
scroll down the where the py extension is defined, highlight it, click
on advanced
then highlight open and hit the edit button.
There you should see python.exe with some other stuff, change it to
pythonw.exe
Then, in the future,
[EMAIL PROTECTED] (Bengt Richter) writes:
I would try right-clicking the shortcut icon and selecting
properties, then select the shortcut tab and edit the target string
with s/python/pythonw/ and then click ok.
Then try double clicking the shortcut icon again. If that does it,
you're home
[EMAIL PROTECTED] (Bengt Richter) writes:
I would try right-clicking the shortcut icon and selecting
properties, then select the shortcut tab and edit the target string
with s/python/pythonw/ and then click ok.
Thanks! I'll try that tomorrow. I never would have figured that out.
--
Python.exe starts up a windows console which gives you things stdin,
stderr, and stdout from the C runtime.
Be warned that you do not have those things with the consoleless(?)
pythonw.exe, stuff which MS intends for gui applications.
It reminds me of select() on windows only working halfway
Dumb question from a Windows ignoramus:
I find myself needing to write a Python app (call it myapp.py) that
uses tkinter, which as it happens has to be used under (ugh) Windows.
That's Windows XP if it makes any difference.
I put a shortcut to myapp.py on the desktop and it shows up as a
little
Paul Rubin skrev:
Question: is there any simple way to arrange to launch the app from
the desktop, without also launching a DOS box?
Just use the .pyw extension instead of .py, and the DOS box
automagically disappears -- or so I have been told ...
--
Leif Biberg Kristensen
[Paul Rubin]
Dumb question from a Windows ignoramus:
I find myself needing to write a Python app (call it myapp.py) that
uses tkinter, which as it happens has to be used under (ugh) Windows.
That's Windows XP if it makes any difference.
Nope, the Windows flavor doesn't matter.
I put a
On 19 Apr 2005 20:49:56 -0700, Paul Rubin http://[EMAIL PROTECTED] wrote:
Dumb question from a Windows ignoramus:
I find myself needing to write a Python app (call it myapp.py) that
uses tkinter, which as it happens has to be used under (ugh) Windows.
That's Windows XP if it makes any
14 matches
Mail list logo
