| No, originally sys.exit() would just call the C routine exit(). There
Ok. issue closed.
| Then fix os.py! (This particular bug will be fixed in the next
| release.)
Yes, I did and gave you my solution.
| Note that os.py also assigns sep = '/' which you probably don't want
| under DOS, although I think it does work; should I fix it? (I think
| it should also set name = 'dos' or perhaps 'msdos'.)
Good idea! I'll send you what I come up with.
| Under DOS the _exit() function shouldn't be in os since it isn't in
| the C library either. (Or is it? Then maybe I should add it to the
| DOS version of the posix interface... Please enlighten me, I always
| thought that _exit() is specific to real UNIX and not specified by
| Standard C.)
I'm not saying it should be there (what does posix mean under msdos?).
I'm saying that os.py callously tried to include it.
| > are quite a few of them). Couldn't we add something that would allow
| > you to pass a list of exception types as the first argument to
| > except:?
|
| You can already do this! (I believe it has always been possible and
| is even documented in the reference manual.)
You're right, I glanced over the syntax, which doesn't make it clear.
The next page explains it. Maybe the syntax could be updated?
(i.e. from ("except" [condition] ["," target]]... to e.g.
("except" [conditions] ["," target]]...)
| If your script is bugfree, it should never print a stack trace. If it
| does generate an exception, the user can show (or mail) the stack
| trace to the author of the script who can then find the bug. Printing
| only the exception would make this much harder. I don't understand
I wouldn't care about the stack trace so much if the format wasn't so
confusing to the ordinary user (yes, other people than myself are using
python programs). Maybe, if the error message could be called out more
and the stack trace could be preceded with some disclaimer, it wouldn't
be so confusing to the ordinary user. They complain to me: WHAT IS
HAPPENING??? as where the fault is e.g. disk full or something else
that I don't check for (is that a bug??? Can't check for everything...)
and they can't seem to find the actual problem in all the output.
I'm done whining now. :-)
-Jaap-
-- Jaap Vermeulen +--------------------------+ | Sequent Computer Systems | Internet : jaap@sequent.com | Beaverton, Oregon | Uucp : ...uunet!sequent!jaap +--------------------------+