Daniel Farina added the comment:
altered title now that it's been seen in init_posix.
--
title: dictobject infinite loop while importing socket -> dictobject infinite
loop in module set-up
___
Python tracker
<http://bugs.python.org
Daniel Farina added the comment:
Attached. The program's function is to take a base64 encoded string and
arguments as input and then to materialize this program on disk and run it with
its arguments.
Notably, this one contains no socket interaction at all, unlike the other
examples,
Daniel Farina added the comment:
I've confirmed this in a non-gevent program (actually a very trivial one, I can
include the source if anyone asks), in 'initposix'. This is on a quiet system,
so OOM is not a very likely explanation. Perhaps signal handling?
#0 0x
Changes by Daniel Farina :
--
title: dictobject infinite loop -> dictobject infinite loop while importing
socket
___
Python tracker
<http://bugs.python.org/issu
Daniel Farina added the comment:
In addition to being re-verified on 2.7, this occurred on a 64 bit system, so
I've changed the title accordingly.
--
title: dictobject infinite loop on 2.6.5 on 32-bit x86 -> dictobject infinite
loop
__
Daniel Farina added the comment:
Okay, fair enough, in that case, here's a patch to fix the documentation as to
not make incorrect statements.
--
status: closed -> open
Added file:
http://bugs.python.org/file30549/fix-subprocess-compat-documentation-
Daniel Farina added the comment:
Also, this fix would be for 2.7. My mistake, even though the goal was to
import on older Pythons.
--
status: closed -> open
versions: +Python 2.7 -Python 2.6
___
Python tracker
<http://bugs.python.org/issu
Daniel Farina added the comment:
Then most assuredly the message at the top is out of date. It seems a pity
that for this small change that older python versions cannot use the same code
verbatim.
It reads:
# This module should remain compatible with Python 2.2, see PEP 291
New submission from Daniel Farina:
I was vendoring subprocess to pick up the change for #16327 when I noticed I
could not import it on 2.6. The backwards compatibility claim at the top is
2.2.
Included is a tiny patch that uses a semantically equivalent form.
--
components: Library
Changes by Daniel Farina :
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue14903>
___
___
Python-bugs-list mailing list
Unsubscribe:
Daniel Farina added the comment:
Hello folks,
After long delay, I can confirm this issue reproduces in a similar way inside
of init_socket in 2.7.
--
___
Python tracker
<http://bugs.python.org/issue14
Daniel Farina added the comment:
Unfortunately it's not so easy to upgrade the system's Python, however, it is
something we might try. The reproducing test case would appear to be akin to:
"import _socket"
And, within the gevent stack trace program,
https://github.co
New submission from Daniel Farina :
I seem to be encountering somewhat rare an infinite loop
in hash table probing while importing _socket, as triggered by
init_socket.c in Python 2.6, as seen/patched shipped with Ubuntu 10.04
LTS. The problem only reproduces on 32 bit machines, on both -O2 and
13 matches
Mail list logo
