I suppose I'm in an interesting situation with regard to Win cmd prompt.
I did this work on XP. There the facility is a bit more constraining
than Win7 on my new PC. On XP, I do not have name completion w/o
setting something. I only recently started with cmd prompt again. In
Win7, it's automatic. There are other differences. An oddity, to me
at least, name completion in W7 does not halt at the first difference.
It goes all the way to completion at the first file that it can find, I
think. I have to back up and try again.
I think today will end my use of Python on XP. I have all files on Win7
now. I'll likely test py3exe there today to see how it behaves.
What you say about the path change makes sense, but it's unfortunate the
producers of py2exe haven't given some insight into this and the misc
files produced in the dist folder. Of course, I have not Googled much at
all on any of this. I'm glad I finally worked my way to this facility.
It should help a good deal on the distribution of my demos to non-python
friends, and fellow project workers at far flung places from here.
On 2/19/2010 11:44 AM, Alan Gauld wrote:
"Wayne Watson" <sierra_mtnv...@sbcglobal.net> wrote
pylab_scatter.exe. Interestingly, if I fire it up from the Win
folder, a dos-window appears and it dies. A few lines appear too
quickly to read. If I execute it from the command prompt, it works
fine. Still the mystery to me is why I don't need to add exe in the
cmd prompt to execute it.
DOS(*) automatically looks for executable file extensions (exe,com,
bat etc)
so you don't need to type them. You don't type cmd.exe to start a DOS
shell do you? You only type cmd... I hope!
(*)Actually the Windows command processor CMD.EXE
Further, how did it know to look in the dist folder?
Thats more interesting!
It presumably added dist to the PATH environment variable. Not
the Python path the DOS one - after all the EXE is not a python
program any more its an exe file running under DOS.
I have a comment about the tutorial.
The command line shown a few lines into section 3. does not need
python in the line in my case. setup.py py2exe works.
That only works because you have the file asociation set to
recognise .py files as associated with the interpreter. Using python
explicitly removes that potential trip wire and so for a tutorial writer
makes it a much safer option.
HTH,
--
"There is nothing so annoying as to have two people
talking when you're busy interrupting." -- Mark Twain
_______________________________________________
Tutor maillist - Tutor@python.org
To unsubscribe or change subscription options:
http://mail.python.org/mailman/listinfo/tutor
