On Wed, 11 Dec 2013 21:00:38 -0500, Roy Smith wrote:
I believe I started off the chain of responses you're referring to. I
meant it semi-humorously, but also with a point. It is clear it turned
out to be harmful, and for that I apologize.
I share your dismay at where this group is
On Tue, 10 Dec 2013 17:57:50 +, Walter Hurry wrote:
On Tue, 10 Dec 2013 11:21:32 -0500, dan.rose wrote:
PLEASE NOTE: The preceding information may be confidential or
privileged. It only should be used or disseminated for the purpose of
conducting business with Parker. If you are not an
On Tue, 10 Dec 2013 11:21:32 -0500, dan.rose wrote:
I am running PYTHON 2.7.3 and executing a PYTHON program that uses
multi-threading. I am running this on a 64-bit Windows 2008 R2 server
(Service Pack 1).
Hi Dan, and despite the emails from a few others, welcome. My further
comments
On 11/12/2013 11:37, Steven D'Aprano wrote:
When did this forum become so intolerant of even the tiniest, most
minor breaches of old-school tech etiquette?
[... Giant Snip...]
Well said Steven. I've only been member of this list for (maybe) a
year, mainly lurking to learn about Python and
In article 52a84061$0$29992$c3e8da3$54964...@news.astraweb.com,
Steven D'Aprano steve+comp.lang.pyt...@pearwood.info wrote:
When did this forum become so intolerant of even the tiniest, most minor
breaches of old-school tech etiquette? Have we really got nothing better
to do than to go on
On Thursday, December 12, 2013 7:30:38 AM UTC+5:30, Roy Smith wrote:
In article Steven D'Aprano wrote:
When did this forum become so intolerant of even the tiniest, most minor
breaches of old-school tech etiquette? Have we really got nothing better
to do than to go on the war path over
If you really want to have a discussion on multi-threading, then look at
quantum bits/computers, and let's see where python can go from the real
future of prototyping language, to the expert in it.
On Wed, Dec 11, 2013 at 11:26 PM, rusi rustompm...@gmail.com wrote:
On Thursday, December 12,
I am running PYTHON 2.7.3 and executing a PYTHON program that uses
multi-threading. I am running this on a 64-bit Windows 2008 R2 server
(Service Pack 1).
Three months ago, I was able to execute this program just fine. I ran the
program and opened Task Manager and verified that the program
On Tue, Dec 10, 2013 at 8:21 AM, dan.r...@parker.com wrote:
I am running PYTHON 2.7.3 and executing a PYTHON program that uses
multi-threading. I am running this on a 64-bit Windows 2008 R2 server
(Service Pack 1).
Three months ago, I was able to execute this program just fine. I ran the
In article mailman.3837.1386693350.18130.python-l...@python.org,
dan.r...@parker.com wrote:
PLEASE NOTE: The preceding information may be confidential or
privileged. It only should be used or disseminated for the purpose
of conducting business with Parker. If you are not an intended
On Tue, 10 Dec 2013 11:21:32 -0500, dan.rose wrote:
PLEASE NOTE: The preceding information may be confidential or
privileged. It only should be used or disseminated for the purpose of
conducting business with Parker. If you are not an intended recipient,
please notify the sender by replying
On 10/12/2013 16:21, dan.r...@parker.com wrote:
* 216-896-3351* PLEASE NOTE: The preceding information may be
confidential or privileged. It only should be used or disseminated for
the purpose of conducting business with Parker. If you are not an
intended recipient, please notify the sender by
Am Dienstag, 10. Dezember 2013 17:21:32 UTC+1 schrieb dan@parker.com:
PLEASE NOTE: The preceding information may be confidential or
privileged. It only should be used or disseminated for the purpose
of conducting business with Parker. If you are not an intended
recipient, please notify the
13 matches
Mail list logo
