Mailman 3 January 2002 - Python-Dev

What's up w/ CVS?
by Skip Montanaro 31 Jan '02

31 Jan '02

Anyone have any idea what's going on w/ SF CVS? I tried to "cvs up" earlier and it just hung. I just tried again now and got the dreaded "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!" from ssh. Skip

3 2

Re: [Python-Dev] test_curses
by Michael Hudson 31 Jan '02

31 Jan '02

Michael Hudson <mwh(a)python.net> writes: > Neal Norwitz <neal(a)metaslash.com> writes: > > > BTW, I test_curses fails: > > test test_curses crashed -- _curses.error: curs_set() returned ERR > > Hmm, yes I get that too (I'd commented it out, because I thought it > had something to do with the crashes, but it didn't AFAICT). > > It's very strange. I tried wrestling with gdb to find out how it was > failing, but didn't get very far. > > It's hard to see how curs_set can fail. Maybe I need to build ncurses > from source and link to that. Heh, well I worked that one out. The terminfo database didn't contain entries for cursor visibility for the $TERM I had (xterm-color, for some forgotten reason). Setting it to xterm made test_curses.py pass for me. much-python-dev-noise-not-much-content-from-me-ly y'rs M. -- That's why the smartest companies use Common Lisp, but lie about it so all their competitors think Lisp is slow and C++ is fast. (This rumor has, however, gotten a little out of hand. :) -- Erik Naggum, comp.lang.lisp

1 0

test_curses
by Michael Hudson 31 Jan '02

31 Jan '02

Neal Norwitz <neal(a)metaslash.com> writes: > BTW, I test_curses fails: > test test_curses crashed -- _curses.error: curs_set() returned ERR Hmm, yes I get that too (I'd commented it out, because I thought it had something to do with the crashes, but it didn't AFAICT). It's very strange. I tried wrestling with gdb to find out how it was failing, but didn't get very far. It's hard to see how curs_set can fail. Maybe I need to build ncurses from source and link to that. Cheers, M. -- ARTHUR: Yes. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying "Beware of the Leopard". -- The Hitch-Hikers Guide to the Galaxy, Episode 1

1 0

Odd errors when catching ImportError
by Paul Dubois 30 Jan '02

30 Jan '02

Please excuse me if this is in the bug list; I looked through it but the list is too long for old people. I have been running into a number of odd errors caused by code like the following. The behavior seems to be machine dependent. fooflag = 0 try: import foo except ImportError: fooflag = 1 I have had this result in a seg fault upon exit, and also when something like this was in file xxx.py inside a package, and the __init__.py did from xxx import fooflag I've had it tell me xxx had no attribute fooflag. I added "print fooflag" at the bottom of the file and it fixed it. That was on a DEC. On Linux it worked. I suppose I should be testing for the ability to import foo some other way but I don't know what it is.

2 1

Re: [Python-Dev] Mixing memory management APIs
by Michael Hudson 30 Jan '02

30 Jan '02

Neil Schemenauer <nas(a)python.ca> writes: > Michael Hudson wrote: > > Modified Files: > > _curses_panel.c > > Log Message: > > Oh look, another one. > > > > 2.2.1 candiate (he says, largely talking to himself :) > > > *** 192,196 **** > > Py_DECREF(po->wo); > > remove_lop(po); > > ! PyMem_DEL(po); > > } > > > > --- 192,196 ---- > > Py_DECREF(po->wo); > > remove_lop(po); > > ! PyObject_DEL(po); > > } > > I think we have to break down and do what Tim suggests. Ie make: > > free == PyMem_DEL == PyObject_DEL == PyObject_FREE == ... > > pymalloc needs to use a completely new set of APIs. The only problem I > see is coming up with names. NEW, MALLOC, REALLOC, RESIZE, and DEL are > all taken. Any suggestions? And then change all the current uses of PyObject_Del to the new API? What would that buy us? Unless I misunderstand we *have* to do something different to remove an object as opposed to freeing raw storage (GC, for example). I agree we have too many preprocessor macros, but I don't think we can have free == PyObject_DEL. I don't what we have is so bad; a helpful tip is that if you're using the _Free/_FREE/_Malloc/_REALLOC/etc interfaces, stop. That gets rid of half the problem. Cheers, M. -- We've had a lot of problems going from glibc 2.0 to glibc 2.1. People claim binary compatibility. Except for functions they don't like. -- Peter Van Eynde, comp.lang.lisp

5 4

Mixing memory management APIs
by Neil Schemenauer 30 Jan '02

30 Jan '02

Michael Hudson wrote: > Modified Files: > _curses_panel.c > Log Message: > Oh look, another one. > > 2.2.1 candiate (he says, largely talking to himself :) > *** 192,196 **** > Py_DECREF(po->wo); > remove_lop(po); > ! PyMem_DEL(po); > } > > --- 192,196 ---- > Py_DECREF(po->wo); > remove_lop(po); > ! PyObject_DEL(po); > } I think we have to break down and do what Tim suggests. Ie make: free == PyMem_DEL == PyObject_DEL == PyObject_FREE == ... pymalloc needs to use a completely new set of APIs. The only problem I see is coming up with names. NEW, MALLOC, REALLOC, RESIZE, and DEL are all taken. Any suggestions? Neil

3 2

Python/Web developer
by Rebecca Schaefer 30 Jan '02

30 Jan '02

TEKsystems in Appleton, WI has an opening for a web developer with Python, Zope, html, SQL, UNIX, and Perl experience. It is a long term contract opportunity. Any interested candidates should email Rebecca Schaefer at rschaefe(a)teksystems.com Thank you, Rebecca

2 1

Re: [Python-Dev] Mixing memory management APIs
by Michael Hudson 30 Jan '02

30 Jan '02

Michael Hudson <mwh(a)python.net> writes: > Neil Schemenauer <nas(a)python.ca> writes: > > > I think we have to break down and do what Tim suggests. Ie make: > > > > free == PyMem_DEL == PyObject_DEL == PyObject_FREE == ... > > > > pymalloc needs to use a completely new set of APIs. The only problem I > > see is coming up with names. NEW, MALLOC, REALLOC, RESIZE, and DEL are > > all taken. Any suggestions? > > And then change all the current uses of PyObject_Del to the new API? > What would that buy us? Unless I misunderstand we *have* to do > something different to remove an object as opposed to freeing raw > storage (GC, for example). > > I agree we have too many preprocessor macros, but I don't think we can > have free == PyObject_DEL. No, I take that back... -- Just point your web browser at http://www.python.org/search/ and look for "program", "doesn't", "work", or "my". Whenever you find someone else whose program didn't work, don't do what they did. Repeat as needed. -- Tim Peters, on python-help, 16 Jun 1998

1 0

Re: [Python-Dev] can someone with purify run test_curses
by Michael Hudson 30 Jan '02

30 Jan '02

Neal Norwitz <neal(a)metaslash.com> writes: > Michael Hudson wrote: > > > > Please? It segfaults for me, in a confusing way. > > > > It only segfaults if I run it under regrtest, not directly. > > What version? Current CVS? Any other special instructions? > When do you need it done? I don't think I do, now (see checkins). But it might be worth running test_curses --with-pymalloc, if it's not too much hassle. I'll have a look to see if there are any other Object/Mem mismatches. Cheers, M. -- Our lecture theatre has just crashed. It will currently only silently display an unexplained line-drawing of a large dog accompanied by spookily flickering lights. -- Dan Sheppard, ucam.chat (from Owen Dunn's summary of the year)

1 0

can someone with purify run test_curses
by Michael Hudson 30 Jan '02

30 Jan '02

Please? It segfaults for me, in a confusing way. It only segfaults if I run it under regrtest, not directly. Cheers, M. -- CLiki pages can be edited by anybody at any time. Imagine the most fearsomely comprehensive legal disclaimer you have ever seen, and double it -- http://ww.telent.net/cliki/index

2 1