Yaniv Aknin added the comment:
I wouldn't mind producing the patch, if Mathew is OK with this.
--
nosy: +Yaniv.Aknin
___
Python tracker
<http://bugs.python.org/i
Yaniv Aknin added the comment:
I've zero experience with programming bluetooth (to be honest, I only tackled
this bug because I'm learning how to contribute to Python and it seemed
ultra-easy), so I'm not an authoritative source on whether such a 'loopback'
test i
Yaniv Aknin added the comment:
It seems to me that subprocess is protected against this flaw. Python 2.x has a
pure-Python implementation of the child logic (which is susceptible to an
unrelated issue). Python 3.x has a C implementation which falls back to
pure-Python if the former is not
Yaniv Aknin added the comment:
This affect 3.x as well.
Regardless of the exact version this will come out in, I think the only proper
solution is one with which we eventually, maybe in two versions' time, end up
with a behaviour that raises an exception upon double insertion. Als
Yaniv Aknin added the comment:
First, let me cast my vote in favour of leaving select() itself alone, it's
excessive to fix this issue with changing select().
Second, while exarkun's comments are accurate, I understand where pitrou is
coming from. EINTR is not a pathological case
Yaniv Aknin added the comment:
pitrou, re. test code: I actually started with the test code, so that part is
done.
I opted to use a forked SocketServer rather than threads. I'm not an expert on
the low-level details of a multi-threaded process receiving threads, but it
seems to me
Yaniv Aknin added the comment:
Attached is the addition of the 'low_level' parameter to ZipFile. Included are
the parameter, a global switch controlling whether the parameter will raise an
Exception or trigger a DeprecationWarning (the latter, for now), updated tests
and updated do
Yaniv Aknin added the comment:
I've updated the sample code to run with Python 3 and tested on Ubuntu 9.10
with and without setting subprocess._has_poll = False.
As expected, when using poll() the sample runs correctly.
When not using poll() the sample breaks (sometimes no data, some
Changes by Yaniv Aknin :
--
nosy: +Yaniv.Aknin
___
Python tracker
<http://bugs.python.org/issue8538>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Yaniv Aknin :
Removed file: http://bugs.python.org/file16841/socketserver_eintr_py3k.diff
___
Python tracker
<http://bugs.python.org/issue7978>
___
___
Pytho
Yaniv Aknin added the comment:
While bda's usecase is indeed fixed is recent versions, I want to point out the
issue still exists in a recent py3k checkout. I've updated my patch to apply
cleanly against recent py3k (and made less structural changes to
test_socketserver.py; I stil
Yaniv Aknin added the comment:
I'm looking into making a patch from this for py3k, and have the following
observations:
1. I agree with merwok, at the moment the monolithic ConfigureAction is a bit
excessive for most uses (other than maybe emulating ./Configure...). I vote we
split
Yaniv Aknin added the comment:
Ugh. Not 100% sure it's related, but I've been getting a similar traceback when
running pip's test suite (python setup.py test) on OSX 10.6.8 with Python 2.7.2.
Traceback (most recent call last):
File
"/usr/local/Cellar/pyt
Yaniv Aknin added the comment:
Shouldn't this be fixed in 2.7 as well?
It's a bug, it's in the wild, and it's causing people to do ugly (and maybe not
100% reliable) things like
https://code.djangoproject.com/browser/django/trunk/django/utils/decorators.py#L68
-
Change by Yaniv Aknin :
--
nosy: -Yaniv.Aknin
___
Python tracker
<https://bugs.python.org/issue8538>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yaniv Aknin added the comment:
I think if the test is conducted without closing stderr, it will only check
that stdin/stdout are handled correctly (you could assume that if one handled
stdin/stdout correctly, they did the same with stderr).
However, since I've used a context ma
New submission from Yaniv Aknin :
While reading the source I saw that recent py3k has this in Objects/object.c
(reasonably recent trunk has it as well):
#if 0 /* XXX this is not quite _PyType_Lookup anymore */
/* Inline _PyType_Lookup */
{ ... removed ...
}
#else
descr
Yaniv Aknin added the comment:
Oops, of course I meant r59944, off by one. :)
--
___
Python tracker
<http://bugs.python.org/issue8749>
___
___
Python-bugs-list m
New submission from Yaniv Aknin :
The documentation of the dis module mentions LOAD_LOCALS, which used to exist
in Python 2.x and I believe was removed from py3k (doesn't appear in recent
Include/opcode.h).
The exact offending section is:
http://docs.python.org/py3k/library/dis.html#o
19 matches
Mail list logo