[ python-Bugs-1430076 ] typo in tutorial

2006-02-12 Thread SourceForge.net
Bugs item #1430076, was opened at 2006-02-12 13:53
Message generated for change (Comment added) made by effbot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430076&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Python 2.4
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: John Hicken (silverfish)
Assigned to: Nobody/Anonymous (nobody)
Summary: typo in tutorial

Initial Comment:
In the "Whetting Your Appetite" section of the 
tutorial:
http://www.python.org/doc/2.4.2/tut/node3.html

Near the end
"Python enables programs to written compactly..." 
should read "Python enables programs to be written 
compactly"

This is from Python version 2.4.2.




--

>Comment By: Fredrik Lundh (effbot)
Date: 2006-02-12 17:28

Message:
Logged In: YES 
user_id=38376

This has been fixed in SVN (revision 39344).

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430076&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1424171 ] patch for etree cdata and attr quoting

2006-02-12 Thread SourceForge.net
Bugs item #1424171, was opened at 2006-02-04 19:23
Message generated for change (Settings changed) made by effbot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1424171&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: XML
Group: Python 2.5
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Chris McDonough (chrism)
Assigned to: Fredrik Lundh (effbot)
Summary: patch for etree cdata and attr quoting

Initial Comment:
Attached is a patch for ElementTree (based on a checkout from the SVN 
trunk's xmlcore.etree) that seems to perform better escaping of cdata and 
attribute values.  Instead of replacing, for example ""e;" with 
""e;" or "&" with "&", it tries to avoid requoting 
ampersands in things that look like entities.

Sorry, I haven't tested this with anything except Python 2.4, I'm not quite 
sure what to do about _encode_entity, and I haven't patched any tests or 
written a new one for this change.  Consider this more of a RFC than a 
patch ready-for-submission as a result.

--

Comment By: Chris McDonough (chrism)
Date: 2006-02-08 18:00

Message:
Logged In: YES 
user_id=32974

Doh, of course.  Sorry, I suspect I'll need to go to remedial XML class.  
Ignore 
this.


--

Comment By: Fredrik Lundh (effbot)
Date: 2006-02-06 22:55

Message:
Logged In: YES 
user_id=38376

I'm not sure I follow.  ET works on the infoset side of
things, where everything is decoded into Unicode strings (or
compatible ASCII strings).  If you set an attribute to
"&" in the infoset, it *must* be encoded on the way out.  
If you want an ampersand, use "&".

--

Comment By: Chris McDonough (chrism)
Date: 2006-02-04 21:23

Message:
Logged In: YES 
user_id=32974

Egads, I did this time.

--

Comment By: Georg Brandl (birkenfeld)
Date: 2006-02-04 19:29

Message:
Logged In: YES 
user_id=1188172

OP: You did check the box?

--

Comment By: Chris McDonough (chrism)
Date: 2006-02-04 19:26

Message:
Logged In: YES 
user_id=32974

Sorry, the tracker doesn't seem to want to allow me to upload the file.  See 
http://www.plope.com/static/misc/betterescape.patch for the patch.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1424171&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1429585 ] segfault in FreeBSD

2006-02-12 Thread SourceForge.net
Bugs item #1429585, was opened at 2006-02-11 11:16
Message generated for change (Comment added) made by uyamba
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1429585&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Threads
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: aix-d (aix-d)
Assigned to: Nobody/Anonymous (nobody)
Summary: segfault in FreeBSD

Initial Comment:
Dear developers,

My program has many TCP connections (~30 per second),
MySQL connections (~100 per second) and threads (~280).
It works long time and receives this segmentation fault:

exited on signal 11 (core dumped)

=== GDB OUTPUT
=
Program received signal SIGSEGV, Segmentation fault.
0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
(gdb) backtrace
#0  0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
#1  0x2831b3d5 in internal_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#2  0x2831b440 in sock_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#3  0x0805a828 in PyObject_Call ()
#4  0x080a01dd in PyEval_EvalFrame ()
#5  0x080a294f in PyEval_EvalCodeEx ()
#6  0x080a138b in PyEval_EvalFrame ()
#7  0x080a212d in PyEval_EvalFrame ()
#8  0x080a212d in PyEval_EvalFrame ()
#9  0x080a212d in PyEval_EvalFrame ()
#10 0x080a212d in PyEval_EvalFrame ()
#11 0x080a212d in PyEval_EvalFrame ()
#12 0x080a294f in PyEval_EvalCodeEx ()
#13 0x080a138b in PyEval_EvalFrame ()
#14 0x080a212d in PyEval_EvalFrame ()
#15 0x080a294f in PyEval_EvalCodeEx ()
#16 0x080da027 in PyFunction_SetClosure ()
#17 0x0805a828 in PyObject_Call ()
#18 0x080a01dd in PyEval_EvalFrame ()
#19 0x080a294f in PyEval_EvalCodeEx ()
#20 0x080a138b in PyEval_EvalFrame ()
#21 0x080a294f in PyEval_EvalCodeEx ()
#22 0x080a138b in PyEval_EvalFrame ()
#23 0x080a294f in PyEval_EvalCodeEx ()
#24 0x080a138b in PyEval_EvalFrame ()
#25 0x080a294f in PyEval_EvalCodeEx ()
#26 0x080a138b in PyEval_EvalFrame ()
#27 0x080a294f in PyEval_EvalCodeEx ()
#28 0x080a138b in PyEval_EvalFrame ()
#29 0x080a294f in PyEval_EvalCodeEx ()
#30 0x080a138b in PyEval_EvalFrame ()
#31 0x080a212d in PyEval_EvalFrame ()
#32 0x080a294f in PyEval_EvalCodeEx ()
#33 0x080da027 in PyFunction_SetClosure ()
#34 0x0805a828 in PyObject_Call ()
#35 0x080601e9 in PyMethod_New ()
#36 0x0805a828 in PyObject_Call ()
#37 0x0809cd31 in PyEval_CallObjectWithKeywords ()
#38 0x080c21a5 in _PyObject_GC_Del ()
#39 0x2821e0cc in pthread_create () from
/usr/lib/libpthread.so.2
#40 0x282db757 in _ctx_start () from /lib/libc.so.6
(gdb)
 END OF GDB OUTPUT
=

Imported modules: socket, atexit, time, pickle, os,
random, traceback, MySQLdb, re, urllib, urllib2, threading

Python version: 2.4.2

Operating system: FreeBSD 6.0-STABLE

Can you help with debugging?

Best regards, Alexander.

--

Comment By: Uyamba (uyamba)
Date: 2006-02-12 19:47

Message:
Logged In: YES 
user_id=1450360

This is test program that generates fault:

#!/usr/local/bin/python

import socket, time
from threading import Thread

class cthread(Thread):
def __init__ (self):
Thread.__init__(self)

def run(self):
socket.setdefaulttimeout(5)
res = socket.getaddrinfo('19.54.123.2', 33, 
0, socket.SOCK_STREAM)[0]
sock = socket.socket(res[0], res[1], res[2])
try:
sock.connect(res[4])
except: pass

def main():
for i in range(1900):
print "starting " + str(i)
ct = cthread()
ct.start()

if __name__ == '__main__':
main()


IP 19.54.123.2 is random. Results are various for some IPs 
and hostnames.


--

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 09:54

Message:
Logged In: YES 
user_id=33168

Can you build python from source?  You can try checking out
the current 2.4 SVN.  This problem may have been fixed
recently.  I'm guessing that the socket descriptor value is
larger than FD_SETSIZE (probably 1k or 4k).  You also may
want to build python with debugging.

If that doesn't solve your problem, you will need to provide
more information about how to reproduce your problem.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1429585&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%

[ python-Bugs-1429585 ] segfault in FreeBSD

2006-02-12 Thread SourceForge.net
Bugs item #1429585, was opened at 2006-02-11 11:16
Message generated for change (Comment added) made by uyamba
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1429585&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Threads
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: aix-d (aix-d)
Assigned to: Nobody/Anonymous (nobody)
Summary: segfault in FreeBSD

Initial Comment:
Dear developers,

My program has many TCP connections (~30 per second),
MySQL connections (~100 per second) and threads (~280).
It works long time and receives this segmentation fault:

exited on signal 11 (core dumped)

=== GDB OUTPUT
=
Program received signal SIGSEGV, Segmentation fault.
0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
(gdb) backtrace
#0  0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
#1  0x2831b3d5 in internal_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#2  0x2831b440 in sock_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#3  0x0805a828 in PyObject_Call ()
#4  0x080a01dd in PyEval_EvalFrame ()
#5  0x080a294f in PyEval_EvalCodeEx ()
#6  0x080a138b in PyEval_EvalFrame ()
#7  0x080a212d in PyEval_EvalFrame ()
#8  0x080a212d in PyEval_EvalFrame ()
#9  0x080a212d in PyEval_EvalFrame ()
#10 0x080a212d in PyEval_EvalFrame ()
#11 0x080a212d in PyEval_EvalFrame ()
#12 0x080a294f in PyEval_EvalCodeEx ()
#13 0x080a138b in PyEval_EvalFrame ()
#14 0x080a212d in PyEval_EvalFrame ()
#15 0x080a294f in PyEval_EvalCodeEx ()
#16 0x080da027 in PyFunction_SetClosure ()
#17 0x0805a828 in PyObject_Call ()
#18 0x080a01dd in PyEval_EvalFrame ()
#19 0x080a294f in PyEval_EvalCodeEx ()
#20 0x080a138b in PyEval_EvalFrame ()
#21 0x080a294f in PyEval_EvalCodeEx ()
#22 0x080a138b in PyEval_EvalFrame ()
#23 0x080a294f in PyEval_EvalCodeEx ()
#24 0x080a138b in PyEval_EvalFrame ()
#25 0x080a294f in PyEval_EvalCodeEx ()
#26 0x080a138b in PyEval_EvalFrame ()
#27 0x080a294f in PyEval_EvalCodeEx ()
#28 0x080a138b in PyEval_EvalFrame ()
#29 0x080a294f in PyEval_EvalCodeEx ()
#30 0x080a138b in PyEval_EvalFrame ()
#31 0x080a212d in PyEval_EvalFrame ()
#32 0x080a294f in PyEval_EvalCodeEx ()
#33 0x080da027 in PyFunction_SetClosure ()
#34 0x0805a828 in PyObject_Call ()
#35 0x080601e9 in PyMethod_New ()
#36 0x0805a828 in PyObject_Call ()
#37 0x0809cd31 in PyEval_CallObjectWithKeywords ()
#38 0x080c21a5 in _PyObject_GC_Del ()
#39 0x2821e0cc in pthread_create () from
/usr/lib/libpthread.so.2
#40 0x282db757 in _ctx_start () from /lib/libc.so.6
(gdb)
 END OF GDB OUTPUT
=

Imported modules: socket, atexit, time, pickle, os,
random, traceback, MySQLdb, re, urllib, urllib2, threading

Python version: 2.4.2

Operating system: FreeBSD 6.0-STABLE

Can you help with debugging?

Best regards, Alexander.

--

Comment By: Uyamba (uyamba)
Date: 2006-02-12 20:48

Message:
Logged In: YES 
user_id=1450360

This is detailed backtrace (from python compiled with 
CFLAGS+="-g"):
==
#0  0xa8348959 in ?? ()
#1  0x08ebb800 in ?? ()
#2  0x0001 in ?? ()
#3  0x77881688 in ?? ()
#4  0x28348947 in internal_connect (s=0x8ebb800, 
addr=0x8ebb818, addrlen=16,
timeoutp=0x778816b4)
at /usr/ports/lang/python/work/Python-2.4.2/Modules/
socketmodule.c:1740
#5  0x28348a00 in sock_connect (s=0x8ebb800, 
addro=0x8ebd72c)
at /usr/ports/lang/python/work/Python-2.4.2/Modules/
socketmodule.c:1771
==

This is the /usr/ports/lang/python/work/Python-2.4.2/
Modules/socketmodule.c:
==
if (s->sock_timeout > 0.0) {
1740:   if (res < 0 && errno == EINPROGRESS) {
timeout = internal_select(s, 1);
res = connect(s->sock_fd, addr, 
addrlen);
if (res < 0 && errno == EISCONN)
res = 0;
}
}
==

No ideas :-(

--

Comment By: Uyamba (uyamba)
Date: 2006-02-12 19:47

Message:
Logged In: YES 
user_id=1450360

This is test program that generates fault:

#!/usr/local/bin/python

import socket, time
from threading import Thread

class cthread(Thread):
def __init__ (self):
Thread.__init__(self)

def run(self):
socket.setdefaulttimeout(5)
res = socket.getaddrinfo('19.54.123.2', 33, 
0, socket.SOCK_STREAM)[0]
sock = socket.socket(res[0], res[1], res[2])
try:
s

[ python-Bugs-1429585 ] segfault in FreeBSD

2006-02-12 Thread SourceForge.net
Bugs item #1429585, was opened at 2006-02-11 00:16
Message generated for change (Comment added) made by nnorwitz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1429585&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Threads
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: aix-d (aix-d)
Assigned to: Nobody/Anonymous (nobody)
Summary: segfault in FreeBSD

Initial Comment:
Dear developers,

My program has many TCP connections (~30 per second),
MySQL connections (~100 per second) and threads (~280).
It works long time and receives this segmentation fault:

exited on signal 11 (core dumped)

=== GDB OUTPUT
=
Program received signal SIGSEGV, Segmentation fault.
0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
(gdb) backtrace
#0  0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
#1  0x2831b3d5 in internal_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#2  0x2831b440 in sock_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#3  0x0805a828 in PyObject_Call ()
#4  0x080a01dd in PyEval_EvalFrame ()
#5  0x080a294f in PyEval_EvalCodeEx ()
#6  0x080a138b in PyEval_EvalFrame ()
#7  0x080a212d in PyEval_EvalFrame ()
#8  0x080a212d in PyEval_EvalFrame ()
#9  0x080a212d in PyEval_EvalFrame ()
#10 0x080a212d in PyEval_EvalFrame ()
#11 0x080a212d in PyEval_EvalFrame ()
#12 0x080a294f in PyEval_EvalCodeEx ()
#13 0x080a138b in PyEval_EvalFrame ()
#14 0x080a212d in PyEval_EvalFrame ()
#15 0x080a294f in PyEval_EvalCodeEx ()
#16 0x080da027 in PyFunction_SetClosure ()
#17 0x0805a828 in PyObject_Call ()
#18 0x080a01dd in PyEval_EvalFrame ()
#19 0x080a294f in PyEval_EvalCodeEx ()
#20 0x080a138b in PyEval_EvalFrame ()
#21 0x080a294f in PyEval_EvalCodeEx ()
#22 0x080a138b in PyEval_EvalFrame ()
#23 0x080a294f in PyEval_EvalCodeEx ()
#24 0x080a138b in PyEval_EvalFrame ()
#25 0x080a294f in PyEval_EvalCodeEx ()
#26 0x080a138b in PyEval_EvalFrame ()
#27 0x080a294f in PyEval_EvalCodeEx ()
#28 0x080a138b in PyEval_EvalFrame ()
#29 0x080a294f in PyEval_EvalCodeEx ()
#30 0x080a138b in PyEval_EvalFrame ()
#31 0x080a212d in PyEval_EvalFrame ()
#32 0x080a294f in PyEval_EvalCodeEx ()
#33 0x080da027 in PyFunction_SetClosure ()
#34 0x0805a828 in PyObject_Call ()
#35 0x080601e9 in PyMethod_New ()
#36 0x0805a828 in PyObject_Call ()
#37 0x0809cd31 in PyEval_CallObjectWithKeywords ()
#38 0x080c21a5 in _PyObject_GC_Del ()
#39 0x2821e0cc in pthread_create () from
/usr/lib/libpthread.so.2
#40 0x282db757 in _ctx_start () from /lib/libc.so.6
(gdb)
 END OF GDB OUTPUT
=

Imported modules: socket, atexit, time, pickle, os,
random, traceback, MySQLdb, re, urllib, urllib2, threading

Python version: 2.4.2

Operating system: FreeBSD 6.0-STABLE

Can you help with debugging?

Best regards, Alexander.

--

>Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 12:54

Message:
Logged In: YES 
user_id=33168

Can you "print *s" ?  My guess is that s->sock_fd >
FD_SETSIZE on your box.  I will try your test code with the
current versions and see if they still fail.

--

Comment By: Uyamba (uyamba)
Date: 2006-02-12 09:48

Message:
Logged In: YES 
user_id=1450360

This is detailed backtrace (from python compiled with 
CFLAGS+="-g"):
==
#0  0xa8348959 in ?? ()
#1  0x08ebb800 in ?? ()
#2  0x0001 in ?? ()
#3  0x77881688 in ?? ()
#4  0x28348947 in internal_connect (s=0x8ebb800, 
addr=0x8ebb818, addrlen=16,
timeoutp=0x778816b4)
at /usr/ports/lang/python/work/Python-2.4.2/Modules/
socketmodule.c:1740
#5  0x28348a00 in sock_connect (s=0x8ebb800, 
addro=0x8ebd72c)
at /usr/ports/lang/python/work/Python-2.4.2/Modules/
socketmodule.c:1771
==

This is the /usr/ports/lang/python/work/Python-2.4.2/
Modules/socketmodule.c:
==
if (s->sock_timeout > 0.0) {
1740:   if (res < 0 && errno == EINPROGRESS) {
timeout = internal_select(s, 1);
res = connect(s->sock_fd, addr, 
addrlen);
if (res < 0 && errno == EISCONN)
res = 0;
}
}
==

No ideas :-(

--

Comment By: Uyamba (uyamba)
Date: 2006-02-12 08:47

Message:
Logged In: YES 
user_id=1450360

This is test program that generates fault:

#!/usr/local/bin/python

import socket, time
from threading import Thread

class cthread(Threa

[ python-Bugs-1429585 ] segfault in FreeBSD

2006-02-12 Thread SourceForge.net
Bugs item #1429585, was opened at 2006-02-11 00:16
Message generated for change (Comment added) made by nnorwitz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1429585&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: Extension Modules
Group: Python 2.4
Status: Open
>Resolution: Works For Me
Priority: 5
Submitted By: aix-d (aix-d)
>Assigned to: Neal Norwitz (nnorwitz)
Summary: segfault in FreeBSD

Initial Comment:
Dear developers,

My program has many TCP connections (~30 per second),
MySQL connections (~100 per second) and threads (~280).
It works long time and receives this segmentation fault:

exited on signal 11 (core dumped)

=== GDB OUTPUT
=
Program received signal SIGSEGV, Segmentation fault.
0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
(gdb) backtrace
#0  0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
#1  0x2831b3d5 in internal_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#2  0x2831b440 in sock_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#3  0x0805a828 in PyObject_Call ()
#4  0x080a01dd in PyEval_EvalFrame ()
#5  0x080a294f in PyEval_EvalCodeEx ()
#6  0x080a138b in PyEval_EvalFrame ()
#7  0x080a212d in PyEval_EvalFrame ()
#8  0x080a212d in PyEval_EvalFrame ()
#9  0x080a212d in PyEval_EvalFrame ()
#10 0x080a212d in PyEval_EvalFrame ()
#11 0x080a212d in PyEval_EvalFrame ()
#12 0x080a294f in PyEval_EvalCodeEx ()
#13 0x080a138b in PyEval_EvalFrame ()
#14 0x080a212d in PyEval_EvalFrame ()
#15 0x080a294f in PyEval_EvalCodeEx ()
#16 0x080da027 in PyFunction_SetClosure ()
#17 0x0805a828 in PyObject_Call ()
#18 0x080a01dd in PyEval_EvalFrame ()
#19 0x080a294f in PyEval_EvalCodeEx ()
#20 0x080a138b in PyEval_EvalFrame ()
#21 0x080a294f in PyEval_EvalCodeEx ()
#22 0x080a138b in PyEval_EvalFrame ()
#23 0x080a294f in PyEval_EvalCodeEx ()
#24 0x080a138b in PyEval_EvalFrame ()
#25 0x080a294f in PyEval_EvalCodeEx ()
#26 0x080a138b in PyEval_EvalFrame ()
#27 0x080a294f in PyEval_EvalCodeEx ()
#28 0x080a138b in PyEval_EvalFrame ()
#29 0x080a294f in PyEval_EvalCodeEx ()
#30 0x080a138b in PyEval_EvalFrame ()
#31 0x080a212d in PyEval_EvalFrame ()
#32 0x080a294f in PyEval_EvalCodeEx ()
#33 0x080da027 in PyFunction_SetClosure ()
#34 0x0805a828 in PyObject_Call ()
#35 0x080601e9 in PyMethod_New ()
#36 0x0805a828 in PyObject_Call ()
#37 0x0809cd31 in PyEval_CallObjectWithKeywords ()
#38 0x080c21a5 in _PyObject_GC_Del ()
#39 0x2821e0cc in pthread_create () from
/usr/lib/libpthread.so.2
#40 0x282db757 in _ctx_start () from /lib/libc.so.6
(gdb)
 END OF GDB OUTPUT
=

Imported modules: socket, atexit, time, pickle, os,
random, traceback, MySQLdb, re, urllib, urllib2, threading

Python version: 2.4.2

Operating system: FreeBSD 6.0-STABLE

Can you help with debugging?

Best regards, Alexander.

--

>Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 13:09

Message:
Logged In: YES 
user_id=33168

I get exceptions when running normally. I had to do ulimit
-n 2000 to be able to run without exception.

I can confirm that with an unpatched 2.4.2, python crashed.
 With the 2.4.2+ patch, no crash.  On SVN head (2.5), I
didn't get a crash, but got a thread exception.  I think
this bug may be fixed.  To get the new features, you need to
update at least these files:

http://svn.python.org/projects/python/branches/release24-maint/Modules/socketmodule.c
http://svn.python.org/projects/python/branches/release24-maint/Modules/_ssl.c
http://svn.python.org/projects/python/branches/release24-maint/PC/pyconfig.h

Please verify if this is fixed for you.

--

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 12:54

Message:
Logged In: YES 
user_id=33168

Can you "print *s" ?  My guess is that s->sock_fd >
FD_SETSIZE on your box.  I will try your test code with the
current versions and see if they still fail.

--

Comment By: Uyamba (uyamba)
Date: 2006-02-12 09:48

Message:
Logged In: YES 
user_id=1450360

This is detailed backtrace (from python compiled with 
CFLAGS+="-g"):
==
#0  0xa8348959 in ?? ()
#1  0x08ebb800 in ?? ()
#2  0x0001 in ?? ()
#3  0x77881688 in ?? ()
#4  0x28348947 in internal_connect (s=0x8ebb800, 
addr=0x8ebb818, addrlen=16,
timeoutp=0x778816b4)
at /usr/ports/lang/python/work/Python-2.4.2/Modules/
socketmodule.c:1740
#5  0x28348a00 in sock_connect (s=0x8ebb800, 
addro=0x8ebd72c)
at /usr/ports/lang/python/work/Python-2.4.2/Modules/
socketmodule.c:1771
==

Th

[ python-Bugs-1429585 ] segfault in FreeBSD

2006-02-12 Thread SourceForge.net
Bugs item #1429585, was opened at 2006-02-11 00:16
Message generated for change (Comment added) made by nnorwitz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1429585&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Extension Modules
Group: Python 2.4
Status: Open
Resolution: Works For Me
Priority: 5
Submitted By: aix-d (aix-d)
Assigned to: Neal Norwitz (nnorwitz)
Summary: segfault in FreeBSD

Initial Comment:
Dear developers,

My program has many TCP connections (~30 per second),
MySQL connections (~100 per second) and threads (~280).
It works long time and receives this segmentation fault:

exited on signal 11 (core dumped)

=== GDB OUTPUT
=
Program received signal SIGSEGV, Segmentation fault.
0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
(gdb) backtrace
#0  0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
#1  0x2831b3d5 in internal_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#2  0x2831b440 in sock_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#3  0x0805a828 in PyObject_Call ()
#4  0x080a01dd in PyEval_EvalFrame ()
#5  0x080a294f in PyEval_EvalCodeEx ()
#6  0x080a138b in PyEval_EvalFrame ()
#7  0x080a212d in PyEval_EvalFrame ()
#8  0x080a212d in PyEval_EvalFrame ()
#9  0x080a212d in PyEval_EvalFrame ()
#10 0x080a212d in PyEval_EvalFrame ()
#11 0x080a212d in PyEval_EvalFrame ()
#12 0x080a294f in PyEval_EvalCodeEx ()
#13 0x080a138b in PyEval_EvalFrame ()
#14 0x080a212d in PyEval_EvalFrame ()
#15 0x080a294f in PyEval_EvalCodeEx ()
#16 0x080da027 in PyFunction_SetClosure ()
#17 0x0805a828 in PyObject_Call ()
#18 0x080a01dd in PyEval_EvalFrame ()
#19 0x080a294f in PyEval_EvalCodeEx ()
#20 0x080a138b in PyEval_EvalFrame ()
#21 0x080a294f in PyEval_EvalCodeEx ()
#22 0x080a138b in PyEval_EvalFrame ()
#23 0x080a294f in PyEval_EvalCodeEx ()
#24 0x080a138b in PyEval_EvalFrame ()
#25 0x080a294f in PyEval_EvalCodeEx ()
#26 0x080a138b in PyEval_EvalFrame ()
#27 0x080a294f in PyEval_EvalCodeEx ()
#28 0x080a138b in PyEval_EvalFrame ()
#29 0x080a294f in PyEval_EvalCodeEx ()
#30 0x080a138b in PyEval_EvalFrame ()
#31 0x080a212d in PyEval_EvalFrame ()
#32 0x080a294f in PyEval_EvalCodeEx ()
#33 0x080da027 in PyFunction_SetClosure ()
#34 0x0805a828 in PyObject_Call ()
#35 0x080601e9 in PyMethod_New ()
#36 0x0805a828 in PyObject_Call ()
#37 0x0809cd31 in PyEval_CallObjectWithKeywords ()
#38 0x080c21a5 in _PyObject_GC_Del ()
#39 0x2821e0cc in pthread_create () from
/usr/lib/libpthread.so.2
#40 0x282db757 in _ctx_start () from /lib/libc.so.6
(gdb)
 END OF GDB OUTPUT
=

Imported modules: socket, atexit, time, pickle, os,
random, traceback, MySQLdb, re, urllib, urllib2, threading

Python version: 2.4.2

Operating system: FreeBSD 6.0-STABLE

Can you help with debugging?

Best regards, Alexander.

--

>Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 13:11

Message:
Logged In: YES 
user_id=33168

The 2.4 fix was committed in revision 42339.

--

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 13:09

Message:
Logged In: YES 
user_id=33168

I get exceptions when running normally. I had to do ulimit
-n 2000 to be able to run without exception.

I can confirm that with an unpatched 2.4.2, python crashed.
 With the 2.4.2+ patch, no crash.  On SVN head (2.5), I
didn't get a crash, but got a thread exception.  I think
this bug may be fixed.  To get the new features, you need to
update at least these files:

http://svn.python.org/projects/python/branches/release24-maint/Modules/socketmodule.c
http://svn.python.org/projects/python/branches/release24-maint/Modules/_ssl.c
http://svn.python.org/projects/python/branches/release24-maint/PC/pyconfig.h

Please verify if this is fixed for you.

--

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 12:54

Message:
Logged In: YES 
user_id=33168

Can you "print *s" ?  My guess is that s->sock_fd >
FD_SETSIZE on your box.  I will try your test code with the
current versions and see if they still fail.

--

Comment By: Uyamba (uyamba)
Date: 2006-02-12 09:48

Message:
Logged In: YES 
user_id=1450360

This is detailed backtrace (from python compiled with 
CFLAGS+="-g"):
==
#0  0xa8348959 in ?? ()
#1  0x08ebb800 in ?? ()
#2  0x0001 in ?? ()
#3  0x77881688 in ?? ()
#4  0x28348947 in internal_connect (s=0x8ebb800, 
addr=0x8ebb818, addrlen=16,
timeoutp=0x778816b4)
at /usr/ports/lang/python/work/Python-2.

[ python-Bugs-1430298 ] smtplib: empty mail addresses

2006-02-12 Thread SourceForge.net
Bugs item #1430298, was opened at 2006-02-12 22:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430298&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Freek Dijkstra (macfreek)
Assigned to: Nobody/Anonymous (nobody)
Summary: smtplib: empty mail addresses

Initial Comment:
It is not possible to send an email with smtplib with an empty return 
address.

if you leave the sender mail address empty, smtplib will use "" as 
sender, instead of "<>", as it should do. Note that an empty return 
address is typically used for mail delivery warnings (it has a valid usage!)

This bug is still in current SVN (I just checked http://svn.python.org/
projects/python/trunk/Lib/smtplib.py). Below is a fix for smtplib.py that 
came with Python 2.3 (since I still use that version). The bug is in the 
function "quoteaddr(addr):"

*** orig/smtplib.py   2005-05-14 23:48:03.0 +0200
--- smtplib.py  2006-02-08 09:52:25.0 +0100
***
*** 176,181 
--- 176,183 
  if m == (None, None): # Indicates parse failure or AttributeError
  #something weird here.. punt -ddm
  return "<%s>" % addr
+ elif m == None:
+ return "<>"
  else:
  return "<%s>" % m
  


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430298&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1333982 ] Bugs of the new AST compiler

2006-02-12 Thread SourceForge.net
Bugs item #1333982, was opened at 2005-10-21 10:08
Message generated for change (Comment added) made by arigo
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1333982&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Parser/Compiler
Group: AST
Status: Open
Resolution: None
Priority: 5
Submitted By: Armin Rigo (arigo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bugs of the new AST compiler

Initial Comment:
The newly merged AST branch is likely to expose
a number of small problems before it stabilizes,
so here is a tentative bug tracker entry to
collect such small problems.


--

>Comment By: Armin Rigo (arigo)
Date: 2006-02-12 21:54

Message:
Logged In: YES 
user_id=4771

Subscripting is generally a bit sloppy: e.g. the AST model has
no way to distinguish between a single value and a one-element
tuple value!  See:

>>> d = {}
>>> d[1,] = 6
>>> d
{1: 6}# !

I suggest we fix the model to turn the 'subs' of the 'Subscript' node
from a list of nodes to a single, mandatory 'sub' node.  If tupling is
necessary, it can be explicitly represented with a 'sub' containing a
'Tuple' node.

--

Comment By: Michael Hudson (mwh)
Date: 2006-02-09 15:02

Message:
Logged In: YES 
user_id=6656

We found another one.  Something is wrong in the compilation of augmented 
assignment to subscriptions containing tuples; running this code:

class C:
def __setitem__(self, i, v):
print i, v
def __getitem__(self, i):
print i
return 0

c = C()
c[4,5] += 1

gives a spurious exception:

Traceback (most recent call last):
  File "", line 1, in 
TypeError: object does not support item assignment

By contrast, "c[(4,5)] += 1" works fine.



--

Comment By: Neal Norwitz (nnorwitz)
Date: 2005-12-18 07:10

Message:
Logged In: YES 
user_id=33168

EXTENDED_ARG problem was fixed a while ago.
The assert/pass problem was fixed with: 41756.

That leaves the LOAD_CONST/POP_TOP optimization that was
lost and one compiler warning: marshal_write_mod() not being
used.

--

Comment By: Michael Hudson (mwh)
Date: 2005-12-11 00:41

Message:
Logged In: YES 
user_id=6656

You have to include those lines in a source file.  It still crashes for me.

--

Comment By: Brett Cannon (bcannon)
Date: 2005-12-10 23:44

Message:
Logged In: YES 
user_id=357491

I just checked Armin's problem code on rev. 41638 and it
worked for me in the interpreter.  You still having
problems, Armin?

--

Comment By: Armin Rigo (arigo)
Date: 2005-12-04 10:30

Message:
Logged In: YES 
user_id=4771

At rev 41584, the following code snippet triggers an assert
if --with-pydebug is enabled:
Python/compile.c:3843: assemble_lnotab: Assertion 'd_lineno >= 0' failed

---
assert 1, ([s for s in x] +
   [s for s in x])
pass
---

--

Comment By: Neal Norwitz (nnorwitz)
Date: 2005-10-23 19:14

Message:
Logged In: YES 
user_id=33168

Checkpoint of outstanding issues.  I think all the others
mentioned so far have been fixed:

 * Raymond's warnings in compile.c (unused locals are fixed)
 * EXTENDED_ARG problem
 * LOAD_CONST/POP_TOP (note we can fix this in the optimizer
generally which would get rid of other useless code too)


--

Comment By: Raymond Hettinger (rhettinger)
Date: 2005-10-23 04:53

Message:
Logged In: YES 
user_id=80475

FWIW, here are the warnings issued by my compiler:

Python-ast.c
C:\py25\Python\Python-ast.c(1995) : warning C4101: 'i' : 
unreferenced local variable
C:\py25\Python\Python-ast.c(2070) : warning C4101: 'i' : 
unreferenced local variable
C:\py25\Python\Python-ast.c(2085) : warning C4101: 'i' : 
unreferenced local variable
C:\py25\Python\Python-ast.c(2130) : warning C4101: 'i' : 
unreferenced local variable
C:\py25\Python\Python-ast.c(2151) : warning C4101: 'i' : 
unreferenced local variable
C:\py25\Python\Python-ast.c(2261) : warning C4101: 'i' : 
unreferenced local variable
C:\py25\Python\Python-ast.c(2270) : warning C4101: 'i' : 
unreferenced local variable


compile.c
C:\py25\Python\compile.c(3782) : warning C4305: '=' : truncation 
from 'const int ' to 'char '
C:\py25\Python\compile.c(3802) : warning C4305: '=' : truncation 
from 'const int ' to 'char '
C:\py25\Python\compile.c(3806) : warning C4305: '=' : truncation 
from 'const int ' to 'char '


-

[ python-Bugs-1429585 ] segfault in FreeBSD

2006-02-12 Thread SourceForge.net
Bugs item #1429585, was opened at 2006-02-11 11:16
Message generated for change (Comment added) made by uyamba
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1429585&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Extension Modules
Group: Python 2.4
Status: Open
Resolution: Works For Me
Priority: 5
Submitted By: aix-d (aix-d)
Assigned to: Neal Norwitz (nnorwitz)
Summary: segfault in FreeBSD

Initial Comment:
Dear developers,

My program has many TCP connections (~30 per second),
MySQL connections (~100 per second) and threads (~280).
It works long time and receives this segmentation fault:

exited on signal 11 (core dumped)

=== GDB OUTPUT
=
Program received signal SIGSEGV, Segmentation fault.
0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
(gdb) backtrace
#0  0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
#1  0x2831b3d5 in internal_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#2  0x2831b440 in sock_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#3  0x0805a828 in PyObject_Call ()
#4  0x080a01dd in PyEval_EvalFrame ()
#5  0x080a294f in PyEval_EvalCodeEx ()
#6  0x080a138b in PyEval_EvalFrame ()
#7  0x080a212d in PyEval_EvalFrame ()
#8  0x080a212d in PyEval_EvalFrame ()
#9  0x080a212d in PyEval_EvalFrame ()
#10 0x080a212d in PyEval_EvalFrame ()
#11 0x080a212d in PyEval_EvalFrame ()
#12 0x080a294f in PyEval_EvalCodeEx ()
#13 0x080a138b in PyEval_EvalFrame ()
#14 0x080a212d in PyEval_EvalFrame ()
#15 0x080a294f in PyEval_EvalCodeEx ()
#16 0x080da027 in PyFunction_SetClosure ()
#17 0x0805a828 in PyObject_Call ()
#18 0x080a01dd in PyEval_EvalFrame ()
#19 0x080a294f in PyEval_EvalCodeEx ()
#20 0x080a138b in PyEval_EvalFrame ()
#21 0x080a294f in PyEval_EvalCodeEx ()
#22 0x080a138b in PyEval_EvalFrame ()
#23 0x080a294f in PyEval_EvalCodeEx ()
#24 0x080a138b in PyEval_EvalFrame ()
#25 0x080a294f in PyEval_EvalCodeEx ()
#26 0x080a138b in PyEval_EvalFrame ()
#27 0x080a294f in PyEval_EvalCodeEx ()
#28 0x080a138b in PyEval_EvalFrame ()
#29 0x080a294f in PyEval_EvalCodeEx ()
#30 0x080a138b in PyEval_EvalFrame ()
#31 0x080a212d in PyEval_EvalFrame ()
#32 0x080a294f in PyEval_EvalCodeEx ()
#33 0x080da027 in PyFunction_SetClosure ()
#34 0x0805a828 in PyObject_Call ()
#35 0x080601e9 in PyMethod_New ()
#36 0x0805a828 in PyObject_Call ()
#37 0x0809cd31 in PyEval_CallObjectWithKeywords ()
#38 0x080c21a5 in _PyObject_GC_Del ()
#39 0x2821e0cc in pthread_create () from
/usr/lib/libpthread.so.2
#40 0x282db757 in _ctx_start () from /lib/libc.so.6
(gdb)
 END OF GDB OUTPUT
=

Imported modules: socket, atexit, time, pickle, os,
random, traceback, MySQLdb, re, urllib, urllib2, threading

Python version: 2.4.2

Operating system: FreeBSD 6.0-STABLE

Can you help with debugging?

Best regards, Alexander.

--

Comment By: Uyamba (uyamba)
Date: 2006-02-13 02:14

Message:
Logged In: YES 
user_id=1450360

Thank you very much!!! :-)
It works fine: python-devel from FreeBSD ports with three 
files updated by SVN to latest version. But i can't compile 
full last SVN release on FreeBSD :-( Could you help with 
updating FreeBSD port please.

--

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-13 00:11

Message:
Logged In: YES 
user_id=33168

The 2.4 fix was committed in revision 42339.

--

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-13 00:09

Message:
Logged In: YES 
user_id=33168

I get exceptions when running normally. I had to do ulimit
-n 2000 to be able to run without exception.

I can confirm that with an unpatched 2.4.2, python crashed.
 With the 2.4.2+ patch, no crash.  On SVN head (2.5), I
didn't get a crash, but got a thread exception.  I think
this bug may be fixed.  To get the new features, you need to
update at least these files:

http://svn.python.org/projects/python/branches/release24-maint/Modules/socketmodule.c
http://svn.python.org/projects/python/branches/release24-maint/Modules/_ssl.c
http://svn.python.org/projects/python/branches/release24-maint/PC/pyconfig.h

Please verify if this is fixed for you.

--

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 23:54

Message:
Logged In: YES 
user_id=33168

Can you "print *s" ?  My guess is that s->sock_fd >
FD_SETSIZE on your box.  I will try your test code with the
current versions and see if they still fail.

--

Comment By: Uyamba (uyamba)
Date: 2006-02-12 20

[ python-Bugs-1429585 ] segfault in FreeBSD

2006-02-12 Thread SourceForge.net
Bugs item #1429585, was opened at 2006-02-11 00:16
Message generated for change (Settings changed) made by nnorwitz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1429585&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Extension Modules
Group: Python 2.4
>Status: Closed
Resolution: Works For Me
Priority: 5
Submitted By: aix-d (aix-d)
Assigned to: Neal Norwitz (nnorwitz)
Summary: segfault in FreeBSD

Initial Comment:
Dear developers,

My program has many TCP connections (~30 per second),
MySQL connections (~100 per second) and threads (~280).
It works long time and receives this segmentation fault:

exited on signal 11 (core dumped)

=== GDB OUTPUT
=
Program received signal SIGSEGV, Segmentation fault.
0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
(gdb) backtrace
#0  0x283199e8 in ?? () from
/usr/local/lib/python2.4/lib-dynload/_socket.so
#1  0x2831b3d5 in internal_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#2  0x2831b440 in sock_connect ()
   from /usr/local/lib/python2.4/lib-dynload/_socket.so
#3  0x0805a828 in PyObject_Call ()
#4  0x080a01dd in PyEval_EvalFrame ()
#5  0x080a294f in PyEval_EvalCodeEx ()
#6  0x080a138b in PyEval_EvalFrame ()
#7  0x080a212d in PyEval_EvalFrame ()
#8  0x080a212d in PyEval_EvalFrame ()
#9  0x080a212d in PyEval_EvalFrame ()
#10 0x080a212d in PyEval_EvalFrame ()
#11 0x080a212d in PyEval_EvalFrame ()
#12 0x080a294f in PyEval_EvalCodeEx ()
#13 0x080a138b in PyEval_EvalFrame ()
#14 0x080a212d in PyEval_EvalFrame ()
#15 0x080a294f in PyEval_EvalCodeEx ()
#16 0x080da027 in PyFunction_SetClosure ()
#17 0x0805a828 in PyObject_Call ()
#18 0x080a01dd in PyEval_EvalFrame ()
#19 0x080a294f in PyEval_EvalCodeEx ()
#20 0x080a138b in PyEval_EvalFrame ()
#21 0x080a294f in PyEval_EvalCodeEx ()
#22 0x080a138b in PyEval_EvalFrame ()
#23 0x080a294f in PyEval_EvalCodeEx ()
#24 0x080a138b in PyEval_EvalFrame ()
#25 0x080a294f in PyEval_EvalCodeEx ()
#26 0x080a138b in PyEval_EvalFrame ()
#27 0x080a294f in PyEval_EvalCodeEx ()
#28 0x080a138b in PyEval_EvalFrame ()
#29 0x080a294f in PyEval_EvalCodeEx ()
#30 0x080a138b in PyEval_EvalFrame ()
#31 0x080a212d in PyEval_EvalFrame ()
#32 0x080a294f in PyEval_EvalCodeEx ()
#33 0x080da027 in PyFunction_SetClosure ()
#34 0x0805a828 in PyObject_Call ()
#35 0x080601e9 in PyMethod_New ()
#36 0x0805a828 in PyObject_Call ()
#37 0x0809cd31 in PyEval_CallObjectWithKeywords ()
#38 0x080c21a5 in _PyObject_GC_Del ()
#39 0x2821e0cc in pthread_create () from
/usr/lib/libpthread.so.2
#40 0x282db757 in _ctx_start () from /lib/libc.so.6
(gdb)
 END OF GDB OUTPUT
=

Imported modules: socket, atexit, time, pickle, os,
random, traceback, MySQLdb, re, urllib, urllib2, threading

Python version: 2.4.2

Operating system: FreeBSD 6.0-STABLE

Can you help with debugging?

Best regards, Alexander.

--

>Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 15:20

Message:
Logged In: YES 
user_id=33168

Closing this bug report since it's fixed.

As to python not compiling on FreeBSD, open a new bug report
with all the info about what is causing the failure.  It
would be great if you can help diagnose the problem as not
many python developers have access to FreeBSD.  Is the
FreeBSD port up-to-date?

--

Comment By: Uyamba (uyamba)
Date: 2006-02-12 15:14

Message:
Logged In: YES 
user_id=1450360

Thank you very much!!! :-)
It works fine: python-devel from FreeBSD ports with three 
files updated by SVN to latest version. But i can't compile 
full last SVN release on FreeBSD :-( Could you help with 
updating FreeBSD port please.

--

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 13:11

Message:
Logged In: YES 
user_id=33168

The 2.4 fix was committed in revision 42339.

--

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-02-12 13:09

Message:
Logged In: YES 
user_id=33168

I get exceptions when running normally. I had to do ulimit
-n 2000 to be able to run without exception.

I can confirm that with an unpatched 2.4.2, python crashed.
 With the 2.4.2+ patch, no crash.  On SVN head (2.5), I
didn't get a crash, but got a thread exception.  I think
this bug may be fixed.  To get the new features, you need to
update at least these files:

http://svn.python.org/projects/python/branches/release24-maint/Modules/socketmodule.c
http://svn.python.org/projects/python/branches/release24-maint/Modules/_ssl.c
http://svn.python.org/projects/python/branches/release24-maint/PC/pyconfig.h

Please v

[ python-Bugs-1430435 ] urlib2

2006-02-12 Thread SourceForge.net
Bugs item #1430435, was opened at 2006-02-13 04:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430435&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: halfik (halfik)
Assigned to: Nobody/Anonymous (nobody)
Summary: urlib2

Initial Comment:
reg = urllib2.Request(url, data, headers)
rl_handle = urllib2.urlopen(reg)

urllib2 has hot memory leaks.

gc: uncollectable <_fileobject memory_adres>
gc: uncollectable 


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430435&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1430436 ] recursive __getattr__ in thread crashes OS X

2006-02-12 Thread SourceForge.net
Bugs item #1430436, was opened at 2006-02-12 22:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430436&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Threads
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Aaron Swartz (aaronsw)
Assigned to: Nobody/Anonymous (nobody)
Summary: recursive __getattr__ in thread crashes OS X

Initial Comment:
The following code consistently crashes Python 2.4 on Mac OS X:

import threading

class foo:
def __getattr__(self, x): self.foo

def j(): foo().bar

t = threading.Thread(target=j, args=())
t.start()

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430436&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1430436 ] recursive __getattr__ in thread crashes BSDs

2006-02-12 Thread SourceForge.net
Bugs item #1430436, was opened at 2006-02-12 22:35
Message generated for change (Comment added) made by aaronsw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430436&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Threads
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Aaron Swartz (aaronsw)
Assigned to: Nobody/Anonymous (nobody)
>Summary: recursive __getattr__ in thread crashes BSDs

Initial Comment:
The following code consistently crashes Python 2.4 on Mac OS X:

import threading

class foo:
def __getattr__(self, x): self.foo

def j(): foo().bar

t = threading.Thread(target=j, args=())
t.start()

--

>Comment By: Aaron Swartz (aaronsw)
Date: 2006-02-12 22:41

Message:
Logged In: YES 
user_id=122141

I've also tested it on FreeBSD and it has the same problem (Segmentation fault 
(core dumped)).

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430436&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1430436 ] recursive __getattr__ in thread crashes BSDs

2006-02-12 Thread SourceForge.net
Bugs item #1430436, was opened at 2006-02-12 22:35
Message generated for change (Comment added) made by aaronsw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430436&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Threads
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Aaron Swartz (aaronsw)
Assigned to: Nobody/Anonymous (nobody)
Summary: recursive __getattr__ in thread crashes BSDs

Initial Comment:
The following code consistently crashes Python 2.4 on Mac OS X:

import threading

class foo:
def __getattr__(self, x): self.foo

def j(): foo().bar

t = threading.Thread(target=j, args=())
t.start()

--

>Comment By: Aaron Swartz (aaronsw)
Date: 2006-02-12 22:44

Message:
Logged In: YES 
user_id=122141

Since the indenting was off above, I've attached the code.

--

Comment By: Aaron Swartz (aaronsw)
Date: 2006-02-12 22:41

Message:
Logged In: YES 
user_id=122141

I've also tested it on FreeBSD and it has the same problem (Segmentation fault 
(core dumped)).

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1430436&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[ python-Bugs-1428789 ] add /usr/local support

2006-02-12 Thread SourceForge.net
Bugs item #1428789, was opened at 2006-02-10 02:55
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1428789&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Installation
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Karol Pietrzak (noodlez84)
Assigned to: Nobody/Anonymous (nobody)
Summary: add /usr/local support

Initial Comment:
Generally, /usr/local support needs to be added for   
python.  Many distributions already do this, either   
partially or completely, causing inconsistencies   
between Python installations among Linux   
distributions.   
   
1. There should be a site-packages directory   
in /usr/local,   
probably /usr/local/lib/python/site-packages.  Just   
like in /usr, it'll need the appropriate symlinks.
x86_64 bit issues also need to be taken into account,   
so /usr/local/lib64/python2.4/site-packages should be   
the local site-packages directory for Python 2.4.x on   
a x86_64 machine.   
   
The reasons for these are numerous.  $PATH   
contains /usr/local/bin, $GTK_PATH   
contains /usr/local, $MANPATH   
contains /usr/local/share/man, and $PKG_CONFIG_PATH   
contains /usr/local/lib/pkgconfig.  Adding a   
site-packages directory in /usr/local will simply   
fill in the hole in the Python configuration.   
   
As the FHS points out, /usr may very well be mounted   
read-only for security purposes.  /usr/local should   
be used instead, especially for non-system / testing   
software.   
   
2. Distutils should install, by default, in   
the site-packages directory in /usr/local described  
in part (1).  This will simply mimic the auto(conf| 
make|etc.) default installation path (isn't the  
default installation path for Python  
itself /usr/local?).  
  
For simplicity and consistency's sake, the default  
installation path for distutils should be the 
site-packages directory in /usr/local. 
 
If someone would point me in the right direction, I 
will gladly write the patch myself. 

--

>Comment By: Martin v. Löwis (loewis)
Date: 2006-02-13 06:05

Message:
Logged In: YES 
user_id=21627

I fail to see the bug in Python here. In the default
configuration, Python does use site-packages in /usr/local,
and distutils does install into /usr/local. So it appears
that Python already does what you say you want.

Apparently, you are talking about Linux here. However, even
on Linux, Python installs to /usr/local by default. If Linux
distributors chose to install it into /usr, then why can't
they also arrange these other changes?

To get /usr/local into sys.path, either edit
site.py, or add a file sitecustomize.py. At compile time,
you can also edit Modules/Setup[.local] to set SITEPATH.

To change the default installation directories, add a
distutils.cfg into the distutils directory, or edit the
unix_prefix scheme in command/install.py

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1428789&group_id=5470
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com