Hi,
1. How do I recall my keyboard input or cycle thru its history ?
2. Is there a way to save all my input in the shell to a file?
3. Why does the cursor remains an hour glass(or really a clock) after I
type in 'help'?
Tks.
AL
Hi,
1. How do I recall my keyboard input or cycle thru its history ?
2. Is there a way to save all my input in the shell to a file?
3. Why does the cursor remains an hour glass(or really a clock) after I
type in 'help'?
Tks.
AL
Alfredo P. Ricafort wrote:
Hi,
1. How do I recall my keyboard input or cycle thru its history ?
Use Ctrl-Up and Ctrl-Down.
2. Is there a way to save all my input in the shell to a file?
Sorry, I don't know, offhand?
3. Why does the cursor remains an hour glass(or really a clock) after I
type in 'help'?
I have never seen this. Do you get a dialog box hen you type 'help()'? What version of wxPython, and Python?
Mark.
No dialog box.
I'm using python2.2 and wxPyhon 2.3.3.1
On Fri, 2002-12-20 at 22:24, Mark Melvin wrote:
>3. Why does the cursor remains an hour glass(or really a clock) after I
>type in 'help'?
>
>
I have never seen this. Do you get a dialog box hen you type 'help()'?
What version of wxPython, and Python?
He's running an older version of PyCrust. It used to pop up a dialog box for
stdin. Now it uses the shell with an input prompt of `<-- `.
On Friday 20 December 2002 06:03 pm, Alfredo P. Ricafort wrote:
> I have never seen this. Do you get a dialog box hen you type 'help()'?
> What version of wxPython, and Python?No dialog box.
I'm using python2.2 and wxPyhon 2.3.3.1
--
Patrick K. O'Brien
Orbtech http://www.orbtech.com/web/pobrien
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------
1.) what is the actual version?
2.) Has anybody except me ever used pycrust with a non-us-keyboard? When I
press a-umlaut the PyCrust shell gets severly damaged & ceases functioning.
(ä is a-umlaut).
(is there a unicode version of PyCrust)
tnx
Harald
1.) what is the actual version?
The current version of PyCrust is 0.8.1.
2.) Has anybody except me ever used pycrust with a non-us-keyboard? When I
press a-umlaut the PyCrust shell gets severly damaged & ceases functioning.
(ä is a-umlaut).
(is there a unicode version of PyCrust)
I don't have a non-us-keyboard, but others that do have been very helpful in
submitting bug reports and patches. For example, I'm able to do the following:
Welcome To PyCrust 0.8.1 - The Flakiest Python Shell
Sponsored by Orbtech - Your source for Python programming expertise.
Python 2.2.2 (#4, Dec 13 2002, 21:58:45)
[GCC 3.2 (Mandrake Linux 9.0 3.2-1mdk)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
s = 'ä'
s
'\xe4'
print s
ä
raw_input()
<-- ä
'\xe4'
ä = 'umlaut'
ä
'umlaut'
As far as I know, PyCrust 0.8 and later works fine with non-us-keyboards and
unicode. If not, please let me know.
On Saturday 21 December 2002 06:24 am, Harald Armin Massa wrote:
--
Patrick K. O'Brien
Orbtech http://www.orbtech.com/web/pobrien
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------
1.) what is the actual version?
There is now an about() method that displays current version info:
Welcome To PyCrust 0.8.1 - The Flakiest Python Shell
Sponsored by Orbtech - Your source for Python programming expertise.
Python 2.2.2 (#4, Dec 13 2002, 21:58:45)
[GCC 3.2 (Mandrake Linux 9.0 3.2-1mdk)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
shell.about()
PyCrust Version: 0.8.1
Shell Revision: 1.93
Interpreter Revision: 1.17
Python Version: 2.2.2
wxPython Version: 2.3.4.1
Platform: linux2
Note that the Shell and Interpreter revision numbers you see will be different
if you run the PyCrust that ships with wxPython, versus the PyCrust from
SourceForge, because there is no easy way to maintain the CVS revision info
between the two repositories.
On Saturday 21 December 2002 06:24 am, Harald Armin Massa wrote:
--
Patrick K. O'Brien
Orbtech http://www.orbtech.com/web/pobrien
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------
Hello,
I started using PyCrust in the actual version ... now I can type a-umlaut
without crashing the shell.
But: Patrick K. O'Brien can do:
>>> s = 'ä'
>>> s
'\xe4'
>>> print s
ä
>>> raw_input()
<-- ä
'\xe4'
>>> ä = 'umlaut'
>>> ä
'umlaut'
When I entered the first line
s='ä'
shell complained about encoding error. So I changed default-encoding to
UTF-8.
NOW I can do:
a='Nasenbär'
a
'Nasenb\xc3\xa4r'
print a
Nasenbär
so 2 out of 3 ain't bad ... I suspect the printing-problem is somewhere
raw_input()
'\xc3\xa4'
ä='aumlaut'
File "<input>", line 1
ä='aumlaut'
^
SyntaxError: invalid syntax
My versions are:
Version: 0.8.1
Shell Revision: 1.93
Interpreter Revision: 1.17
Python Version: 2.2.1
wxPython Version: 2.3.4.1u
Platform: win32
So I suspect there are some things I did not take care of ... connected with
unicode?
Can someboe help me where to search?
Tnx
Harald
I thought that this is pretty common to most interpreters?
Most of the time, I use the interpreter to experiment. I would try out a number of
codes. I should be able to save them for future reference.
Similarly, when the interpreter finds any syntax error on my code, I don't want
to type them all over again. I should be able to save the code in a file, edit it, and then
load it.
Al
On Fri, 2002-12-20 at 23:07, Patrick K. O'Brien wrote:
> 2. Is there a way to save all my input in the shell to a file?
Not yet. Patches are welcome. What's the use case for this?
> > 2. Is there a way to save all my input in the shell to a file?
>
> Not yet. Patches are welcome. What's the use case for this?I thought that this is pretty common to most interpreters?
I've not had much demand for this, nor have I felt much of a need myself. I do
plan to add it some day. It just isn't high on my list.
Most of the time, I use the interpreter to experiment. I would try out a
number of codes. I should be able to save them for future reference.
You can copy and paste from the shell, with or without the prompts.
Similarly, when the interpreter finds any syntax error on my code, I don't
want to type them all over again. I should be able to save the code in a
file, edit it, and then load it.
You don't have to retype anything. Just recall the command from the history
and edit it - even multiline commands can be recalled and edited directly in
the shell. If the code is in a module, just edit and reload() the module.
On Saturday 21 December 2002 06:44 pm, Alfredo P. Ricafort wrote:
On Fri, 2002-12-20 at 23:07, Patrick K. O'Brien wrote:
--
Patrick K. O'Brien
Orbtech http://www.orbtech.com/web/pobrien
-----------------------------------------------
"Your source for Python programming expertise."
-----------------------------------------------