wrote:
>
>Being new to all this I feel that I might need to just start out with a
>command prompt working with Django and something else... another command
>prompt or VS to create my python files.
>
The main thing to take into account is the division between being IN
the interpreter and being in a command shell.
">>>" is the normal prompt from inside an interactive Python
interpreter session. At this level you can execute Python /statements/.
Any example that reads something like
[python] <filename>.py <arguments>
is meant for a command shell. Actually typing "python" first may be
optional if {Linux/UNIX: the .py file starts with a proper #! line
identifying the Python interpreter to be used | Windows: .py files have
been defined as an "executable" extension (in which case, even the .py
may be optional) AND .py files have been associated with the Python
interpreter}.
In many of the (I)DEs (PythonWin, IDLE, probably the various EMACS
and VI configurations, SciTE), one can edit a file, save it (some will
save for you if needed), then hit some key combo which will spawn a
Python interpreter passing it the file for execution. You may even be
prompted to supply command line arguments (PythonWin, I know does this).
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment