[issue3831] Multiprocessing: Expose underlying pipe in queues

Changes by Forest Wilkinson pyth...@tibit.com: -- nosy: +forest ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3831 ___ ___ Python-bugs-list

[issue1641] asyncore delayed calls feature

Changes by Forest Wilkinson [EMAIL PROTECTED]: -- nosy: +forest __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1641 __ ___ Python-bugs-list mailing list Unsubscribe

[issue2550] SO_REUSEADDR doesn't have the same semantics on Windows as on Unix

Changes by Forest Wilkinson [EMAIL PROTECTED]: -- nosy: +forest ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2550 ___ ___ Python-bugs-list mailing

[issue3904] asynchat async_chat __init__() arguments changed in python 2.6

New submission from Forest Wilkinson [EMAIL PROTECTED]: In python 2.6rc2, the async_chat.__init__() parameters have changed. The first arg was called 'conn' in python 2.5, and it is now called 'sock'. This change breaks code that worked with previous python 2.x versions, if that code followed

[issue1533164] Installed but not listed *.pyo break bdist_rpm

Changes by Forest Wilkinson [EMAIL PROTECTED]: -- nosy: +forest ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1533164 ___ ___ Python-bugs-list mailing

[issue1856] shutdown (exit) can hang or segfault with daemon threads running

Changes by Forest Wilkinson for...@users.sourceforge.net: -- nosy: +forest ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1856 ___ ___ Python-bugs

[issue1720705] thread + import = crashes?

Changes by Forest Wilkinson for...@users.sourceforge.net: -- nosy: +forest ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1720705 ___ ___ Python

[issue4690] asyncore calls handle_write() on closed sockets when use_poll=True

New submission from Forest Wilkinson for...@users.sourceforge.net: With use_poll=True on linux, asyncore calls handle_write() after the socket has been closed. More specifically, it looks like asyncore dispatches handle_read() and handle_close() events between the writable() test

[issue2944] asyncore doesn't handle connection refused correctly

Changes by Forest Wilkinson for...@users.sourceforge.net: -- nosy: +forest ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue2944 ___ ___ Python-bugs

[issue1194378] sendmsg() and recvmsg() for C socket module

Changes by Forest Wilkinson for...@users.sourceforge.net: -- nosy: +forest ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1194378 ___ ___ Python

[issue3143] Make the left sidebar in the doc collapsible

Forest Wilkinson for...@users.sourceforge.net added the comment: I just noticed Ezio's change to the title of this bug. Does the proposed fix address the original bug title (docs waste a lot of horizontal space on left nav bar) for third-party packages that use docutils to generate their docs

[issue2632] performance problem in socket._fileobject.read

Changes by Forest Wilkinson [EMAIL PROTECTED]: -- nosy: +forest __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2632 __ ___ Python-bugs-list mailing list Unsubscribe

[issue3143] development docs waste a lot of horizontal space on left nav bar

New submission from Forest Wilkinson [EMAIL PROTECTED]: I was just browsing the development docs, and noticed that the new left-side navigation bar wastes a lot of horizontal space on the web page. It fills nearly a third of my browser window (at its usual size) with useless blank space

[issue3823] ssl.wrap_socket() is incompatible with unprivileged servers, due to keyfile requirement

New submission from Forest Wilkinson [EMAIL PROTECTED]: SSLSocket() and ssl.wrap_socket() accept private keys only as paths to their location on the file system. This means that a server can only support SSL if it has read access to its private key file at the time when client connections

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

Changes by Forest Wilkinson [EMAIL PROTECTED]: -- title: ssl.wrap_socket() is incompatible with unprivileged servers, due to keyfile requirement - ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

Changes by Forest Wilkinson [EMAIL PROTECTED]: -- nosy: +janssen ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3823 ___ ___ Python-bugs-list mailing

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

Forest Wilkinson [EMAIL PROTECTED] added the comment: This problem also exists in the add-on ssl module for python 2.6: http://pypi.python.org/pypi/ssl/ ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3823

[issue3823] ssl.wrap_socket() is incompatible with servers that drop privileges, due to keyfile requirement

Forest Wilkinson [EMAIL PROTECTED] added the comment: Simon: I wish I could offer guidance here, but I'm afraid that I too am reading some of these openssl man pages for the first time. I agree that writing to a temporary file would be bad. Accepting file-like objects from python code would

[issue17431] email.parser module has no attribute BytesFeedParser

New submission from Forest Wilkinson: The docs claim that email.parser.BytesFeedParser exists, but it doesn't. Looks like email.feedparser.FeedParser is imported into the email.parser module, but someone forgot to do the same for BytesFeedParser. -- components: email messages: 184247

[issue1641] asyncore delayed calls feature

Forest Wilkinson for...@users.sourceforge.net added the comment: I'm looking forward to having this functionality in asyncore. It would help me remove some unwanted hackery from my own code. Giampaolo, I'm concerned that your patch uses a global 'tasks' list which cannot be overriden

[issue5397] PEP 372: OrderedDict

Forest Wilkinson for...@users.sourceforge.net added the comment: I was just reading the PEP, and caught this bit: Does OrderedDict.popitem() return a particular key/value pair? Yes. It pops-off the most recently inserted new key and its corresponding value. Okay, but I'd also like a convenient

[issue5397] PEP 372: OrderedDict

Forest Wilkinson for...@users.sourceforge.net added the comment: Shouldn't popitem() allow the caller to choose which end from which to pop? Thinking it through a bit more, and LRU cache would actually need to access the oldest item without necessarily removing it. Besides, popitem() should

[issue5397] PEP 372: OrderedDict

Forest Wilkinson for...@users.sourceforge.net added the comment: Agreed here. Thanks, gents. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5397

[issue3143] development docs waste a lot of horizontal space on left nav bar

Forest Wilkinson for...@users.sourceforge.net added the comment: It is relative to the resolution of the user's browser window. Don't make the mistake of assuming that everyone keeps their browser maximized. :) -- ___ Python tracker rep