Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #109057 > unrolled thread

Re: Spurious issue in CPython 2.7.5

Started byChris Angelico <rosuav@gmail.com>
First post2016-05-24 23:18 +1000
Last post2016-05-24 23:18 +1000
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Spurious issue in CPython 2.7.5 Chris Angelico <rosuav@gmail.com> - 2016-05-24 23:18 +1000

#109057 — Re: Spurious issue in CPython 2.7.5

FromChris Angelico <rosuav@gmail.com>
Date2016-05-24 23:18 +1000
SubjectRe: Spurious issue in CPython 2.7.5
Message-ID<mailman.53.1464095906.20402.python-list@python.org>
On Tue, May 24, 2016 at 8:22 PM, thomas povtal.org <thomas@povtal.org> wrote:
>  Please excuse me if this is not the right place, but I have some issues
>    with CPython on a NUMA machine.
>
>    We're using gevent and I'm suspecting some "threading" could cause this,
>    as I'm able to replicate it locally with the same data.

Perfectly good place to ask. Since you can replicate the problem, can
you post the code that will trigger this? There are a few
possibilities. I've once (not "once in a <time period>", once) seen a
Python installation with corruption in a .pyc file, which resulted in
really bizarre errors; but more likely, it's something that can be
shown on multiple systems.

It's definitely possible that threading can (a) introduce errors, or
(b) move errors around and make them less obvious. Try to cut your
example down as much as it can, but it wouldn't surprise me if
threading remains in it.

ChrisA

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web