Changes by Richard Oudkerk shibt...@gmail.com:
--
nosy: +sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13854
___
___
Python-bugs-list mailing
Changes by Richard Oudkerk shibt...@gmail.com:
--
nosy: +sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12157
___
___
Python-bugs-list mailing
Changes by Richard Oudkerk shibt...@gmail.com:
--
nosy: +sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10037
___
___
Python-bugs-list mailing
Richard Oudkerk shibt...@gmail.com added the comment:
It is not clear to me how to reproduce the bug.
When you say letting the workers terminate themselves do mean calling
sys.exit() or os._exit() in the submitted task? Are you trying to get the
result of a task which caused the worker
Richard Oudkerk shibt...@gmail.com added the comment:
The attached patch uses memoryview instead of ctypes.
If the patch for Issue #14953 (reimplementing RawArray/RawValue in terms of
memoryview) is applied, then it could be simplified a bit.
--
Added file: http://bugs.python.org
Richard Oudkerk shibt...@gmail.com added the comment:
The Windows buildbots were failing compilation.
I've added Object/namespaceobject.c and Include/namespaceobject.h to
PCbuild/pythoncore.vcxproj in changeset ee7cd7d51ed6.
--
nosy: +sbt
Richard Oudkerk shibt...@gmail.com added the comment:
Lesha, the problems about magical __del__ methods you are worried about
actually have nothing to do with threading and locks. Even in a single
threaded program using fork, exactly the same issues of potential corruption
would be present
Richard Oudkerk shibt...@gmail.com added the comment:
conn = MySQLConn()
start_thread1(conn)
start_thread2(conn):
while True:
if os.fork() == 0: # child
raise Exception('doom') # triggers destructor
There is no guarantee here that the lock will be held at the time
Richard Oudkerk shibt...@gmail.com added the comment:
I don't think there is anything special about PriorityQueue.
There is a similar concerning the use of the Python implementation of RLock in
signal handlers -- see http://bugs.python.org/issue13697.
Maybe the signal handler should
Richard Oudkerk shibt...@gmail.com added the comment:
Attached is an updated version of Charles-François's reinit_locks.diff.
Changes:
* Handles RLock by assuming that if self-count != 0 when we acquire
the lock, then the lock must have been reinitialized by
PyThread_ReInitLocks
Richard Oudkerk shibt...@gmail.com added the comment:
a) fork() is called with the DB lock held by thread1.
b) Some time passes before the child gets to exec().
c) In that time, the child's thread2 gets to doWork().
d) Simultaneously, the parent's doWork is still running and holding a lock
Richard Oudkerk shibt...@gmail.com added the comment:
Is there any particular reason not to merge Charles-François's
reinit_locks.diff?
Reinitialising all locks to unlocked after a fork seems the only sane
option.
I agree with this.
I haven't looked at the patch very closely. I
Changes by Richard Oudkerk shibt...@gmail.com:
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14930
Richard Oudkerk shibt...@gmail.com added the comment:
It seems the real issue here is that buffer objects are picklable (depending on
protocol) but the resulting string is not unpicklable.
There are probably lots of other examples where this happens: for instance
Exception subclasses which do
New submission from Richard Oudkerk shibt...@gmail.com:
The attached patch enables creation of shared objects allocated from shared
memory using memoryview objects instead of ctypes.
This enables the use of shared memory on systems where ctypes is unavailable.
The new functions/classes
Richard Oudkerk shibt...@gmail.com added the comment:
New patch.
--
Added file: http://bugs.python.org/file25742/memoryview-weakref.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14930
Richard Oudkerk shibt...@gmail.com added the comment:
In the test, you should call gc.collect() so that it works on non-
reference counted implementations.
I did think about using gc.collect(), but I was not sure whether it was
guaranteed to collect everything possible if you only call
Richard Oudkerk shibt...@gmail.com added the comment:
Updated patch.
--
Added file: http://bugs.python.org/file25744/memoryview-weakref.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14930
Changes by Richard Oudkerk shibt...@gmail.com:
--
nosy: +sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13797
___
___
Python-bugs-list mailing
New submission from Richard Oudkerk shibt...@gmail.com:
The attached patch makes memoryview objects weakrefable.
The reason I would like them to be weakrefable is so that I can manage the
finalization and pickling of memoryview objects which wrap shared mmap segments.
(It would be even better
Richard Oudkerk shibt...@gmail.com added the comment:
RawValue uses ctypes, right? That's problematic for platforms which don't
support ctypes.
Are there many posix systems (we care about) where ctypes doesn't work?
It would be fairly easy to use memoryview instead of ctypes. (In fact
Changes by Richard Oudkerk shibt...@gmail.com:
--
resolution: - fixed
stage: - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12098
Changes by Richard Oudkerk shibt...@gmail.com:
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9400
Richard Oudkerk shibt...@gmail.com added the comment:
Without more information I will close this.
--
resolution: - invalid
stage: - committed/rejected
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Richard Oudkerk shibt...@gmail.com added the comment:
I'll, remember that in future;-)
Closing.
--
resolution: - fixed
stage: - committed/rejected
status: open - closed
type: crash - behavior
___
Python tracker rep...@bugs.python.org
http
Changes by Richard Oudkerk shibt...@gmail.com:
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12091
Changes by Richard Oudkerk shibt...@gmail.com:
--
resolution: - fixed
stage: commit review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14548
Richard Oudkerk shibt...@gmail.com added the comment:
The patch was applied to 3.x branch in 0aa8af79359d and partially backported to
2.7 in 26bbff4562a7 - see #9400.
I will close.
--
nosy: +sbt
resolution: - fixed
stage: - committed/rejected
status: open - closed
Richard Oudkerk shibt...@gmail.com added the comment:
This is a duplicate of #9244 and #9400 which have been fixed by wrapping
unpicklable exceptions in picklable exceptions.
The larger issue of many exception classes being unpicklable, is dealt with in
#1692335.
--
resolution
Changes by Richard Oudkerk shibt...@gmail.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13751
___
___
Python-bugs
Richard Oudkerk shibt...@gmail.com added the comment:
_eintr_retry was removed by 99ef4501205b.
--
resolution: - out of date
stage: - committed/rejected
status: open - closed
type: - behavior
___
Python tracker rep...@bugs.python.org
http
Richard Oudkerk shibt...@gmail.com added the comment:
(1) Good catch. I suspect that this could be mitigated even if we cared
about LinuxThreads. I haven't looked, but there's got to be a way to
determine if we are a thread or a fork child.
Using a generation count would probably work just
Richard Oudkerk shibt...@gmail.com added the comment:
How would this differ from the normal communicate()?
It would block until one of the following occurs:
* some data has been written to stdin,
* some data has been read from stdout or stderr, or
* timeout passes (if timeout is not None
Changes by Richard Oudkerk shibt...@gmail.com:
--
nosy: +sbt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14881
___
___
Python-bugs-list mailing
Richard Oudkerk shibt...@gmail.com added the comment:
Comments on Josiah's patch:
* It uses pywin32 for PeekNamedPipe -- this is now available from _winapi.
* I don't think send(), recv() and recv_exact() will work correctly if
buffering is used -- an error should be raised in this case
Richard Oudkerk shibt...@gmail.com added the comment:
Personally, I would factor out the code for Popen.communicate() in to a
Communicator class which wraps a Popen object and has a method
communicate(input, timeout=None) - (bytes_written, output, error)
On Windows this would use threads
Richard West r.h.w...@gmail.com added the comment:
I also had an ImportError on _struct module during 'make install' when building
2.7.3 from source configured with --enable-shared. My solution, which *seems*
to have worked, is simple:
$ make -i install
$ make install
My guess
Richard Oudkerk shibt...@gmail.com added the comment:
I think the note for communicate() just means that you might get MemoryError
(or some other exception) if the output is too big. But I agree it is
ambiguous.
communicate() uses select() on Unix and threads on Windows, so deadlocks should
Richard Oudkerk shibt...@gmail.com added the comment:
PCbuild/build.bat and Modules/_decimal/tests/runall.bat still use vcbuild
instead of msbuild.
It also seems that if an external dependency is unavailable then msbuild can
fail to build targets which do not depend on it. For instance if I
Richard Oudkerk shibt...@gmail.com added the comment:
Failure to build _multiprocessing will mean that multiprocessing cannot
be imported. So if the function goes somewhere in multiprocessing then
it makes running the test suite with multiple processes dependent on the
building
Richard Oudkerk shibt...@gmail.com added the comment:
- the function generating the flags should be exported (with a private
name), so that it can be reused by Lib/test/[test_]support.py. Duplicate
code is error-prone, especially when enumerating command-line flags,
attribute names
Changes by Richard Oudkerk shibt...@gmail.com:
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14753
New submission from Richard Oudkerk shibt...@gmail.com:
In version 3.2 and earlier, Process.join() and Connection.poll() treat negative
timeouts as zero timeouts. (Thread.join() does the same.)
In the current 3.3 version, they treat negative timeouts as infinite timeouts.
Also
Richard Oudkerk shibt...@gmail.com added the comment:
I've recently started seeing this failure repeatably on Linux (Ubuntu
Jaunty):
The test is newly enabled. Does repeatably mean you always get the failure?
I have not seen any failures on the Linux buildbots
Changes by Richard Oudkerk shibt...@gmail.com:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14725
Richard Oudkerk shibt...@gmail.com added the comment:
I found a race where a connection attempt could happen before the listening
socket's listen() method was called.
Vinay, could you update and try again please.
--
___
Python tracker rep
Richard Oudkerk shibt...@gmail.com added the comment:
The documentation page for ConnectNamedPipe
(http://msdn.microsoft.com/en-us/library/windows/desktop/aa365146(v=vs.85).aspx)
has a community addition which says that ConnectNamedPipe will appear to
fail with ERROR_NO_DATA (232) if a client
Richard Oudkerk shibt...@gmail.com added the comment:
TBH I don't understand why it should crash, and therefore how your patch
helps. Trying again using narrow strings should always work; indeed, the
code did that before I touched it. Can you describe how it crashes?
The important part
Richard Oudkerk shibt...@gmail.com added the comment:
Without the check for RuntimeError
os.utime(foo, times=(5,5), ns=(5,5))
raises
TypeError(TypeError: 'str' does not support the buffer interface)
because we have fallen through to the narrow path. The correct error
Richard Oudkerk shibt...@gmail.com added the comment:
Let me recap, just to make sure I have it straight. There are two errors
on Windows:
That's right. The patch looks good and passes for me on Windows.
--
___
Python tracker rep
Richard Oudkerk shibt...@gmail.com added the comment:
There is another problem causing a fatal error in test_posix on Unix.
The attached patch fixes it: *ua-path should be decrefed not ua-path.
--
Added file: http://bugs.python.org/file25452/utime_read_time_arguments.patch
Richard Oudkerk shibt...@gmail.com added the comment:
Looks good to me. You're a core contributor, yes? If not let me know and
I'll commit it.
I will commit.
Though I must admit I'm baffled how I haven't seen that crash. I've run
the unit tests a zillion times on this patch.
Were you
Richard Oudkerk shibt...@gmail.com added the comment:
I'm developing on Linux (64-bit) in case that helps.
I tested it on 32 bit Linux.
I have committed it, but I forgot to put the issue number in the commit message.
--
___
Python tracker rep
Richard Oudkerk shibt...@gmail.com added the comment:
bba131e48852 causes crashes on Windows.
The attached patch fixes the crash and makes test_os pass for me.
However, using PyErr_ExceptionMatches(PyExc_RuntimeError) to check whether to
try again using narrow strings is ugly. Maybe
Richard Oudkerk shibt...@gmail.com added the comment:
I have backported the fix for issue #9244 to 2.7. This should fix the hang and
produce a traceback containing a representation of the original error.
--
___
Python tracker rep...@bugs.python.org
Richard Oudkerk shibt...@gmail.com added the comment:
There are plenty of other bad exception classes apart from
CalledProcessError, including TimeoutExpired in the same file. In fact I
suspect this is true of the majority of the exception classes in the stdlib
which override __init__. So I
Richard Oudkerk shibt...@gmail.com added the comment:
The problems with error numbers seem to be caused by the addition of a new
section in errno.h:
/* POSIX SUPPLEMENT */
#define EADDRINUSE 100
#define EADDRNOTAVAIL 101
...
#define ETXTBSY 139
#define EWOULDBLOCK 140
Richard Oudkerk shibt...@gmail.com added the comment:
According to http://msdn.microsoft.com/en-us/library/5814770t.aspx the
supported errno values in VS2010 are
E2BIG EACCES EAGAIN EBADF ECHILD EDEADLOCK EDOM EEXIST EILSEQ
EINVAL EMFILE ENOENT ENOEXEC ENOMEM ENOSPC ERANGE EXDEV
Richard Oudkerk shibt...@gmail.com added the comment:
the errno codes (EAGAIN etc) are provided only as a compatibility for
posix apps that test errno. On windows, we use the WSA return values
from the api functions and WsaGetLastError().
...
So, the proposed patch is not a change
Richard Oudkerk shibt...@gmail.com added the comment:
New patch which adds timeout to ResourceSharer.stop() which defaults to 0.
When stop() fails it now uses the logger.
pthread_sigmask() only stops this background thread from receiving signals.
Signals will still be delivered to other
Richard Oudkerk shibt...@gmail.com added the comment:
This doesn't change that, and as far as I know, this has worked and
continues to work. errno is supported.
Using your patch, does the following throw an AssertionError?
import os, errno
try:
... os.read(-1, 10)
... except OSError
Richard Oudkerk shibt...@gmail.com added the comment:
I can't work out what is wrong here.
The code does not to account for a partial read of the message from the socket.
The attached patch fixes that, but it does not address the cause of this
failure.
--
keywords: +patch
Added file
Richard Oudkerk shibt...@gmail.com added the comment:
New version of patch which does
signal.pthread_sigmask(signal.SIG_BLOCK, range(1, signal.NSIG))
in the thread (is that right?).
It also uses a timeout when trying to join the thread.
--
Added file: http://bugs.python.org
Richard Oudkerk shibt...@gmail.com added the comment:
Warning added to patch.
--
Added file: http://bugs.python.org/file25362/mp_resource_sharer_stop.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14666
Richard Oudkerk shibt...@gmail.com added the comment:
Version of patch which checks invariants in the setter and adds tests.
--
Added file:
http://bugs.python.org/file25363/writable_closure_with_checking.patch
___
Python tracker rep
Richard Oudkerk shibt...@gmail.com added the comment:
Shouldn't test___closure__() also test what happens when the closure is
replaced with None, or a tuple which is too long or too short or contains
non-cell objects?
All of these things seem to be checked when you create a new function using
Richard Oudkerk shibt...@gmail.com added the comment:
The patch causes crashes. If I define
def cell(o):
def f(): o
return f.__closure__[0]
def f():
a = 1
b = 2
def g():
return a + b
return g
g = f()
then I find
g.__closure__ = None; g
Richard Oudkerk shibt...@gmail.com added the comment:
This patch adds a ResourceSharer.stop() method. This is called from
tearDownClass() in the unittest.
--
keywords: +patch
Added file: http://bugs.python.org/file25357/mp_resource_sharer_stop.patch
Richard Oudkerk shibt...@gmail.com added the comment:
I don't think _DummyThread can override __stop(), because of the name
mangling of __private methods. However, the hasattr() approach would
probably work.
Wouldn't a _DummyThread._Thread__stop() method override Thread.__stop()? Like
K Richard Pixley r...@noir.com added the comment:
I think a better solution that declaring it to be apple's bug would be to
release one binary for pre-10.7, (or maybe 10.6 with the current xcode), and a
different binary for post-10.7.
This isn't an apple bug in the sense that there's anything
New submission from K Richard Pixley r...@noir.com:
Once I've instantiated my server class, along with a handler class, called
server.serve_forever(), handler.handle() has been called, I've done my work,
and I'm ready to shut the whole thing down...
How do I do that?
The doc says
K Richard Pixley r...@noir.com added the comment:
It appears as though the problem is that shutdown() blocks waiting for the
serve_forever loop to terminate, which won't happen as long as the process is
blocked on shutdown.
I'd like to propose that the library be changed to eliminate
K Richard Pixley r...@noir.com added the comment:
On second thought, my proposal is likely to break existing code, so I withdraw
it.
I don't know how to exit the server in a way that both works in all conditions
and also continues to support existing semantics.
I expect we'll need to create
New submission from K Richard Pixley r...@noir.com:
Install the Python-2.7.2 mac installer for Lion on Lion.
Then attempt easy_install -U psutil. I get:
za-dc-dev/bin/easy_install -U psutil
install_dir
/Users/rich/projects/za-packages/za-dependency-checker/za-dc-dev/lib/python2.7/site
Richard Saunders richismyn...@mac.com added the comment:
Here's a test demonstrating the memcmp optimization effect:
---
more ~/PickTest5/Python/string_test3.py
a = []
b = []
c = []
d = []
for x in range(0,1000) :
a.append(the quick
Richard Saunders richismyn...@mac.com added the comment:
Added branches for specializing for UCS2 and UCS4 types
--
Added file:
http://bugs.python.org/file23574/unicode_with_memcmp_and_ucs_specialization.patch
___
Python tracker rep
Richard Saunders richismyn...@mac.com added the comment:
Some more information:
Bob Arendt and I have been playing with the Fedora Core .spec file
for python on Fedora Core 15:
the compile options we found seem to automatically (as we did non invoke
this option) invoke '-fno-builtin-memcmp
New submission from Richard Saunders richismyn...@mac.com:
In discussions of memcmp performance, (http://www.picklingtools.com/study.pdf)
it was noted how well Python 2.7 can take advantage of faster memcmps (indeed,
the rich comparisons are all memcmp calls).
There have been some discussion
Richard Saunders richismyn...@mac.com added the comment:
This is a potential patch:
I believe it follows the C-style of PEP 7
There is a test as well, testing 1 and 2 byte kinds.
I have run it through the python tests and have added no new breakages
(there were some tests that failed
K Richard Pixley r...@noir.com added the comment:
My point was for python-2.7. I haven't stumbled into the buffer protocol yet.
So no, it doesn't really.
I still think the documentation, especially the 2.7 doc, could be more explicit.
My concern here is with the use of close() becoming
K Richard Pixley r...@noir.com added the comment:
An interesting point, although I think that's only relevant if the
documentation lists the ABC and a reference to it. (python-3 doc essentially
does this.)
I see no such reference in the 2.7 gzipfile doc, which leads me to believe,
(from
K Richard Pixley r...@noir.com added the comment:
I didn't miss it.
I think the close call needs equal treatment to the open call. The mention is
certainly present, but seems implicit to me. I would prefer to see it listed
explicitly.
But I also don't think it's important enough in the 2.7
K Richard Pixley r...@noir.com added the comment:
I'm now convinced this isn't worth fixing in 2.x.
--
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11203
New submission from K Richard Pixley r...@noir.com:
mmap.read requires a argument. Since most file-like objects do not, this
breaks the file-like object illusion.
mmap.read argument should be optional, presumably defaulting to the entire
mmap'd area.
--
messages: 135362
nosy: rich
New submission from Richard Rabbat rab...@google.com:
image/webp is missing from the mimetypes.py list of valid mimetypes.
webp is an open-source image format and uses vp8 as a codec.
--
components: Library (Lib)
messages: 129786
nosy: Richard.Rabbat
priority: normal
severity: normal
Richard Lowe richl...@richlowe.net added the comment:
I don't find anything lacking about the error messages, I meant that there were
no more specific exceptions, or fields in GetoptError to allow the caller to
tell what was specifically wrong and provide its own localized messages. So
while
Richard Lowe richl...@richlowe.net added the comment:
Sure, just localizing them in the getopt implementation would be fine.
I suggested subclassing to solve the more general problem of the caller being
able to tell one getopt error from another, for which it is a pretty common
solution
K Richard Pixley r...@noir.com added the comment:
Documentation needs to be updated to state that these are now context managers.
This is important since they aren't in python-2.x.
I'm not sure whether this should be added to the new in python blurbs.
--
nosy: +teamnoir
New submission from K Richard Pixley r...@noir.com:
The documentation for gzip should include the close method.
It's use in the 2.7 documentation implies it's existence but it should also be
stated explicitly that it exists.
In the 3.x documentation, the use of close not in the examples since
New submission from Richard Nienaber rjniena...@gmail.com:
According to Microsoft documentation
(http://msdn.microsoft.com/en-us/library/ms724884(v=vs.85).aspx) when using the
REG_EXPAND_SZ value type, environment variables (e.g. %programfiles%) should be
expanded to their values (e.g. 'C
Richard Nienaber rjniena...@gmail.com added the comment:
Further documentation on the RegEnumValue function (used by the _winreg
module): http://msdn.microsoft.com/en-us/library/ms724865(v=vs.85).aspx. The
documentation doesn't say whether the string is expanded or not on retrieval.
Given
K Richard Pixley r...@noir.com added the comment:
How does rm -rf address this issue? Or does it?
shutils.rmtree should probably do the same thing.
--
nosy: +teamnoir
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4489
New submission from Richard vanchagr...@gmail.com:
Whenever I paste anything into the IDLE shell, the program freezes, and then
crashes.
I'm using Python 2.7.1rcl with a Version 10.6.4 Mac OSX
--
components: IDLE
messages: 122441
nosy: 5ragar5
priority: normal
severity: normal
status
New submission from Richard Fuhr richard.f...@gmail.com:
When running Python 2.7 if you invoke
help(divmod)
the first line of the resulting help displays
Help on built-in function divmod in module __builtin__:
but I believe that the name of the module is __builtins__
so the line should say
Richard Fuhr richard.f...@gmail.com added the comment:
I had a typo in my own bug report that was reporting a typo; what I intended to
say was the following ( the q should not have been there at the end )
When running Python 2.7 if you invoke
help(divmod)
the first line of the resulting
Richard Fuhr richard.f...@gmail.com added the comment:
OK, thanks for the clarification. I am new to Python.
Sent from my iPod
On Nov 9, 2010, at 3:54 PM, Andreas Stührk rep...@bugs.python.org wrote:
Andreas Stührk andy-pyt...@hammerhartes.de added the comment:
__builtin__
Richard pub...@careaga.net added the comment:
Sorry to be obscure, Ronald. I mistook my configuration problem, described
below for the original problem. But I can reproduce the problem with opening an
existing file under IDLE, which is a segmentation fault. When opening a new
window, I get
Richard Jones richardjo...@optushome.com.au added the comment:
Thanks for the investigation Antoine.
In r84088 I've added a call to asyncore.close_all in the smtpd test tearDown
methods.
--
resolution: - fixed
status: open - closed
___
Python
Richard pub...@careaga.net added the comment:
I'm thinking that the Snow Leopard abort trap when invoking IDLE from the
command line is a permissions problem somewhere because it works ok when
invoked with sudo. The console displays an odd message 2010-08-07 20:38:23.375
Python[25858:170b
Richard Jones richardjo...@optushome.com.au added the comment:
Merged mock socket from test_smtpd.py and committed.
--
resolution: - accepted
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2423
901 - 1000 of 1061 matches
Mail list logo
