On Saturday, 18 May 2013 10:58:13 UTC+2, Jurgens de Bruin wrote:
> This is my first script where I want to use the python threading module. I
> have a large dataset which is a list of dict this can be as much as 200
> dictionaries in the list. The final goal is a histogram for each dict 16
> h
On Tue, 21 May 2013 05:53:46 +0300, Carlos Nepomuceno wrote:
> BTW, why I didn't find the source code to the sys module in the 'Lib'
> directory?
Because sys is a built-in module. It is embedded in the Python
interpreter.
--
Steven
--
http://mail.python.org/mailman/listinfo/python-list
> On Tue, May 21, 2013 at 11:44 AM, 8 Dihedral
> wrote:
>> OK, if the python interpreter has a global hiden print out
>> buffer of ,say, 2to 16 K bytes, and all string print functions
>> just construct the output string from the format to this string
>> in an efficient low level way, then the
e source code to the sys module in the 'Lib' directory?
> Date: Tue, 21 May 2013 11:50:17 +1000
> Subject: Re: Please help with Threading
> From: ros...@gmail.com
> To: python-list@python.org
>
> On Tue, May 21, 2013 at 11:44 A
On Tue, May 21, 2013 at 11:44 AM, 8 Dihedral
wrote:
> OK, if the python interpreter has a global hiden print out
> buffer of ,say, 2to 16 K bytes, and all string print functions
> just construct the output string from the format to this string
> in an efficient low level way, then the next qu
Chris Angelico於 2013年5月20日星期一UTC+8下午5時09分13秒寫道：
> On Mon, May 20, 2013 at 6:35 PM, Cameron Simpson wrote:
>
> > _lock = Lock()
>
> >
>
> > def lprint(*a, **kw):
>
> > global _lock
>
> > with _lock:
>
> > print(*a, **kw)
>
> >
>
> > and use lprint() everywhere?
>
>
>
>
I didn't know that.
On 20 May 2013 12:10, "Dave Angel" wrote:
> Are you making function calls, using system libraries, or creating or
deleting any objects? All of these use the GIL because they use common
data structures shared among all threads. At the lowest level, creating an
object requires
=On Mon, May 20, 2013 at 8:46 PM, Ned Batchelder wrote:
> On 5/20/2013 6:09 AM, Chris Angelico wrote:
>>
>> Referencing a function's own name in a default has to have one of
>> these interpretations:
>>
>> 1) It's a self-reference, which can be used to guarantee recursion
>> even if the name is re
On 05/20/2013 03:55 AM, Fábio Santos wrote:
My use case was a tight loop processing an image pixel by pixel, or
crunching a CSV file. If it only uses local variables (and probably hold a
lock before releasing the GIL) it should be safe, no?
Are you making function calls, using system libraries
On 5/20/2013 6:09 AM, Chris Angelico wrote:
Referencing a function's own name in a default has to have one of
these interpretations:
1) It's a self-reference, which can be used to guarantee recursion
even if the name is rebound
2) It references whatever previously held that name before this def
On Mon, May 20, 2013 at 7:54 PM, Cameron Simpson wrote:
> On 20May2013 19:09, Chris Angelico wrote:
> | On Mon, May 20, 2013 at 6:35 PM, Cameron Simpson wrote:
> | > _lock = Lock()
> | >
> | > def lprint(*a, **kw):
> | > global _lock
> | > with _lock:
> | > print(*a, **kw)
> |
> Date: Mon, 20 May 2013 18:35:20 +1000
> From: c...@zip.com.au
> To: carlosnepomuc...@outlook.com
> CC: python-list@python.org
> Subject: Re: Please help with Threading
>
> On 20May2013 10:53, Carlos Nepomuceno wrote:
> | I just g
On 20May2013 19:09, Chris Angelico wrote:
| On Mon, May 20, 2013 at 6:35 PM, Cameron Simpson wrote:
| > _lock = Lock()
| >
| > def lprint(*a, **kw):
| > global _lock
| > with _lock:
| > print(*a, **kw)
| >
| > and use lprint() everywhere?
|
| Fun little hack:
|
| def print(*ar
It is pretty cool although it looks like a recursive function at first ;)
On 20 May 2013 10:13, "Chris Angelico" wrote:
> On Mon, May 20, 2013 at 6:35 PM, Cameron Simpson wrote:
> > _lock = Lock()
> >
> > def lprint(*a, **kw):
> > global _lock
> > with _lock:
> > print(*a, **kw
On Mon, May 20, 2013 at 6:35 PM, Cameron Simpson wrote:
> _lock = Lock()
>
> def lprint(*a, **kw):
> global _lock
> with _lock:
> print(*a, **kw)
>
> and use lprint() everywhere?
Fun little hack:
def print(*args,print=print,lock=Lock(),**kwargs):
with lock:
print(*args,**
On 20May2013 10:53, Carlos Nepomuceno wrote:
| I just got my hands dirty trying to synchronize Python prints from many
threads.
| Sometimes they mess up when printing the newlines.
| I tried several approaches using threading.Lock and Condition.
| None of them worked perfectly and all of them ma
My use case was a tight loop processing an image pixel by pixel, or
crunching a CSV file. If it only uses local variables (and probably hold a
lock before releasing the GIL) it should be safe, no?
My idea is that it's a little bad to have to write C or use multiprocessing
just to do simultaneous c
> Date: Mon, 20 May 2013 17:45:14 +1000
> From: c...@zip.com.au
> To: fabiosantos...@gmail.com
> Subject: Re: Please help with Threading
> CC: python-list@python.org; wlfr...@ix.netcom.com
>
> On 20May2013 07:25, Fábio Santos wrote:
> Date: Sun, 19 May 2013 13:10:36 +1000
> From: c...@zip.com.au
> To: carlosnepomuc...@outlook.com
> CC: python-list@python.org
> Subject: Re: Please help with Threading
>
> On 19May2013 03:02, Carlos Nepomuceno wrote:
> | Just be
On 20May2013 07:25, Fábio Santos wrote:
| On 18 May 2013 20:33, "Dennis Lee Bieber" wrote:
| > Python threads work fine if the threads either rely on intelligent
| > DLLs for number crunching (instead of doing nested Python loops to
| > process a numeric array you pass it to something lik
On 18 May 2013 20:33, "Dennis Lee Bieber" wrote:
> Python threads work fine if the threads either rely on intelligent
> DLLs for number crunching (instead of doing nested Python loops to
> process a numeric array you pass it to something like NumPy which
> releases the GIL while crunching
On 05/19/2013 05:46 PM, Dennis Lee Bieber wrote:
On Sun, 19 May 2013 10:38:14 +1000, Chris Angelico
declaimed the following in gmane.comp.python.general:
On Sun, May 19, 2013 at 10:02 AM, Carlos Nepomuceno
wrote:
I didn't know Python threads aren't preemptive. Seems to be something really
o
On Mon, May 20, 2013 at 7:46 AM, Dennis Lee Bieber
wrote:
> On Sun, 19 May 2013 10:38:14 +1000, Chris Angelico
> declaimed the following in gmane.comp.python.general:
>> With interpreted code eg in CPython, it's easy to implement preemption
>> in the interpreter. I don't know how it's actually do
On 19May2013 03:02, Carlos Nepomuceno wrote:
| Just been told that GIL doesn't make things slower, but as I
| didn't know that such a thing even existed I went out looking for
| more info and found that document:
| http://www.dabeaz.com/python/UnderstandingGIL.pdf
|
| Is it current? I didn't know
On Sun, May 19, 2013 at 10:02 AM, Carlos Nepomuceno
wrote:
> I didn't know Python threads aren't preemptive. Seems to be something really
> old considering the state of the art on parallel execution on multi-cores.
>
> What's the catch on making Python threads preemptive? Are there any ongoing
>
> To: python-list@python.org
> From: wlfr...@ix.netcom.com
> Subject: Re: Please help with Threading
> Date: Sat, 18 May 2013 15:28:56 -0400
>
> On Sat, 18 May 2013 01:58:13 -0700 (PDT), Jurgens de Bruin
> decla
On 05/18/2013 04:58 AM, Jurgens de Bruin wrote:
This is my first script where I want to use the python threading module. I have
a large dataset which is a list of dict this can be as much as 200 dictionaries
in the list. The final goal is a histogram for each dict 16 histograms on a
page ( 4x
Jurgens de Bruin wrote:
> I will post code - the entire scripts is 1000 lines of code - can I post
> the threading functions only?
Try to condense it to the relevant parts, but make sure that it can be run
by us.
As a general note, when you add new stuff to an existing longish script it
is alw
I will post code - the entire scripts is 1000 lines of code - can I post the
threading functions only?
--
http://mail.python.org/mailman/listinfo/python-list
Jurgens de Bruin wrote:
> This is my first script where I want to use the python threading module. I
> have a large dataset which is a list of dict this can be as much as 200
> dictionaries in the list. The final goal is a histogram for each dict 16
> histograms on a page ( 4x4 ) - this already w
This is my first script where I want to use the python threading module. I have
a large dataset which is a list of dict this can be as much as 200 dictionaries
in the list. The final goal is a histogram for each dict 16 histograms on a
page ( 4x4 ) - this already works.
What I currently do is
31 matches
Mail list logo
