Am 11.09.2014 23:32 schrieb Ervin Hegedüs:
There is no upper limit to the thread name other than that you will
eventually run out of memory ;)
thanks - I hope that the memory will not run out by these
threads... :)
Anyway, that means, on my system:
import sys
print sys.maxint
9223372036854
On Sat, Sep 13, 2014 at 12:09:28PM +0200, Martin Skjöldebrand wrote:
> Unfortunately we will never know 😢
hehe :), joke of the day :)
thanks,
a.
--
I � UTF-8
--
https://mail.python.org/mailman/listinfo/python-list
Unfortunately we will never know 😢
Sent from Blue Mail
On 12 Sep 2014 07:43, at 07:43, Chris Angelico wrote:
>On Fri, Sep 12, 2014 at 1:41 PM, Cameron Simpson wrote:
>> On 12Sep2014 11:29, Steven D'Aprano
>
>> wrote:
>>>
>>> [...]maxint. I know that some Linux
>>> systems can have an uptime o
dieter wrote:
> Ervin Hegedüs writes:
>> ...
> What is used as thread id is platform dependent. Likely, it depends
> on the thread support of the underlying C libary (i.e. the
> operating system thread support).
>
> Under Linux, thread ids seem to be addresses - i.e. very large
> integers.
$ gr
Ervin Hegedüs writes:
> ...
What is used as thread id is platform dependent. Likely, it depends
on the thread support of the underlying C libary (i.e. the
operating system thread support).
Under Linux, thread ids seem to be addresses - i.e. very large
integers.
--
https://mail.python.org/mailma
Hi Steven,
On Fri, Sep 12, 2014 at 11:29:56AM +1000, Steven D'Aprano wrote:
> import sys
> print sys.maxint
> > 9223372036854775807
> >
> > the couter could be 9223372036854775807?
> >
> > And after? :)
>
> Suppose you somehow managed to create 9223372036854775807 threads. If your
> c
On Fri, Sep 12, 2014 at 1:41 PM, Cameron Simpson wrote:
> On 12Sep2014 11:29, Steven D'Aprano
> wrote:
>>
>> [...]maxint. I know that some Linux
>> systems can have an uptime over a year, perhaps even two years, but I
>> think
>> that nearly 300 years is asking a bit much.
>
>
> 2 years is nothin
On 12Sep2014 11:29, Steven D'Aprano
wrote:
[...]maxint. I know that some Linux
systems can have an uptime over a year, perhaps even two years, but I think
that nearly 300 years is asking a bit much.
2 years is nothing. Unless they have a particularly buggy kernel, most UNIX
systems, Linux in
On Fri, Sep 12, 2014 at 11:29 AM, Steven D'Aprano
wrote:
> I know that some Linux
> systems can have an uptime over a year, perhaps even two years, but I think
> that nearly 300 years is asking a bit much. Your hardware probably won't
> keep working that long.
I've had over two years of uptime. C
On Thu, Sep 11, 2014 at 8:29 PM, Steven D'Aprano
wrote:
> Suppose you somehow managed to create 9223372036854775807 threads. If your
> computer has 16 GB of RAM available, that means that at most each thread
> can use:
>
> py> 16*1024*1024*1024/9223372036854775807
> 1.862645149230957e-09
>
> bytes
Ervin Hegedüs wrote:
[...]
>> > My question is: how much thread ID could be totally? Is there any
>> > maximum number? And if the thread reached that, what will be
>> > done? Overlflowed? Couting from 0 again?
[...]
>> There is no upper limit to the thread name other than that you will
>> eventual
Ervin Hegedüs wrote:
> Hi Peter,
>
> thanks for the reply,
>
> On Thu, Sep 11, 2014 at 09:48:18PM +0200, Peter Otten wrote:
>> Ervin Hegedüs wrote:
>>
>> > Exception in thread Thread-82:
>> > ...
>> > My question is: how much thread ID could be totally? Is there any
>> > maximum number? And if
Hi Peter,
thanks for the reply,
On Thu, Sep 11, 2014 at 09:48:18PM +0200, Peter Otten wrote:
> Ervin Hegedüs wrote:
>
> > Exception in thread Thread-82:
> > ...
> > My question is: how much thread ID could be totally? Is there any
> > maximum number? And if the thread reached that, what will be
Ervin Hegedüs wrote:
> I've made a long-time running daemon, which uses threads. Looks
> like that works perfectly, now I'm looking at the exceptions :).
>
> In the log, I found an interesting message:
>
> Exception in thread Thread-82:
> ...
>
> The main function allows 2 thread to run simulta
Hello,
I've made a long-time running daemon, which uses threads. Looks
like that works perfectly, now I'm looking at the exceptions :).
In the log, I found an interesting message:
Exception in thread Thread-82:
...
The main function allows 2 thread to run simultaniously, and if
the thread finis
15 matches
Mail list logo