I've had no luck replicating this issue. I'm wondering if
the xterm is continuing to send a Ctrl-D, for some reason.
Python handles an EOF error (ctrl-D) as an exception, and it
seems to do so cleanly on the systems I have available to test.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This has to be some very strange interaction between
FreeBSD, python, and Charm -- it's as if FreeBSD is not
correctly resetting a signal handler, or python's not
correctly resetting an exception handler, or something. It's
not reproducible with either xterm or the console on my
(non-FreeBSD) systems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I update charm when the FreeBSD port updates. The port is
currently at 1.7.0, which happened when I wasn't noticing --
I confess I use the software less when it is not working
correctly.
I get the same exact results with 1.7.0. When I start
"charm", I then hit ^D.
It does say "That is not a valid option.", and the menu
repeats, followed by "That is not a valid option.", and then
the menu again, infinitely repeating. It is almost as if
charm is not clearing the ^D or something.
I am using python 2.4.2, also from ports.
I even updated my OS -- version 5.5-PRERELEASE is what I'm
running now, still has the same results.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=159820
I've had no luck replicating this issue. I'm wondering if
the xterm is continuing to send a Ctrl-D, for some reason.
Python handles an EOF error (ctrl-D) as an exception, and it
seems to do so cleanly on the systems I have available to test.
Logged In: YES
user_id=118777
It still happens on 1.5.0. Can you try it on a FreeBSD
system? It happens on console too, so it's not just xterm.
Logged In: YES
user_id=159820
What version of Python are you using?
This has to be some very strange interaction between
FreeBSD, python, and Charm -- it's as if FreeBSD is not
correctly resetting a signal handler, or python's not
correctly resetting an exception handler, or something. It's
not reproducible with either xterm or the console on my
(non-FreeBSD) systems.
Logged In: NO
On my linux box using charm 1.7.0:
Python 2.4.2 (#1, Oct 16 2005, 00:06:10)
[GCC 3.3.6 (Gentoo Hardened 3.3.6, ssp-3.3.6-1.0,
pie-8.7.8)] on linux2
^D doesn't break anything. The main menu just says "That is
not a valid option." and repeats.
Is there a reason the OP isn't using a newer version?
Logged In: YES
user_id=118777
I update charm when the FreeBSD port updates. The port is
currently at 1.7.0, which happened when I wasn't noticing --
I confess I use the software less when it is not working
correctly.
I get the same exact results with 1.7.0. When I start
"charm", I then hit ^D.
It does say "That is not a valid option.", and the menu
repeats, followed by "That is not a valid option.", and then
the menu again, infinitely repeating. It is almost as if
charm is not clearing the ^D or something.
I am using python 2.4.2, also from ports.
I even updated my OS -- version 5.5-PRERELEASE is what I'm
running now, still has the same results.