New submission from Peter Saunders:
When compiling python 2.5.1 on Solaris 10 (sparc and x86), with openssl
0.9.8e - test_md5 fails with No module named _sha256. (As does doing an
"import md5")
When compiling, setup.dist was modified, the ssl parts were uncommented,
and modified
New submission from Peter Saunders <[EMAIL PROTECTED]>:
Feature Request:
Could configure etc be modified to detect if it can use
enable_extended_FILE_stdio() to allow solaris to use > 256 FD's while
still be compiled 32 bit. This is a new feature in Solaris 10 (came in
Update 4).
Changes by Peter Saunders <[EMAIL PROTECTED]>:
--
components: +Distutils -Interpreter Core
type: -> feature request
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Changes by Peter Saunders <[EMAIL PROTECTED]>:
--
components: +Interpreter Core -Distutils
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
New submission from Peter Saunders :
I have an example code that works fine on Python 2.6.3, but when run in
Python 3.1.1 - after a very short period of time, will go wrong.
Summary:
We have a queue, and when the queue has something in it (a list), we
start a thread to deal with that entry
Peter Saunders added the comment:
Further information: it doesn't fail everytime in Python 3.1 - usually 1
in 4, or 1 in 5 times. It never fails with Python 2.6.3
Example output from the script when its failing (python 3.1):
Starting data1
Starting data2
Started subproc: PID: 20209 :
Peter Saunders added the comment:
Well, if it helps, here is the output of the dtrace script from starting
of a loop with the failure, and stopping during the failure.
--
Added file: http://bugs.python.org/file15126/dtrace.txt
___
Python tracker
Peter Saunders added the comment:
If you mean, in main() instead of doing:
while True:
q.put(["data1", "data2"])
t = Process(target=popJobs, args=(q, ))
t.start()
t.join()
and doing:
while True:
q.put(["data1", "data2"])
popJob
Peter Saunders added the comment:
Same thing occurs, as you would expect, when I do:
while True:
fail=failureObject()
tlist = []
for x in ["data1", "data2"]:
t = threading.Thread(target=checkAlive, args = (fail, x), name=x)
t.start()
tlis
Peter Saunders added the comment:
Further oddness:
When running the script (i've reduced its size further now, see attached):
I get the following output:
Reaping PID: 23215
True
Started subproc: PID: 23216 : args: data1
Started subproc: PID: 23216 : args: data1
Started subproc: PID:
Peter Saunders added the comment:
Sorry for the spam on the updates :) - but, its the same thread printing
this out too. I changed the print line to:
curThread = threading.current_thread()
print("Started subproc: PID: %d : args: %s Thread ID: %s" %(newJob.pid,
str(args), str(curTh
Peter Saunders added the comment:
Tested on Linux, and repeated the issue - just to confirm this isn't a
Solaris specific issue.
Tested using dummy_threading - bug does not appear when that is used.
Added _verbose=True to threads, and log_to_stderr(SUBDEBUG) set for Process.
Attached i
New submission from Peter Saunders :
Only sucessfully replicated on solaris.
When running getpass() - it goes into non echo mode, however, once enter
is pressed, the password is echoed to the screen. E.g.
> /opt/python/2.6.3/bin/python -c 'import getpass; x=getpass.getpass()'
Changes by Peter Saunders :
--
keywords: +patch
Added file: http://bugs.python.org/file15201/getpass.diff
___
Python tracker
<http://bugs.python.org/issue7
14 matches
Mail list logo
