On Sun, Nov 1, 2009 at 3:33 AM, Antoine Pitrou wrote:
>
> Hello again,
>
> Brett Cannon python.org> writes:
>>
>> I think it's worth it. Removal of the GIL is a totally open-ended problem
>> with no solution in sight. This, on the other hand, is a performance benefit
>> now. I say move forward wi
On 30Oct2009 20:43, Chris Bergstresser wrote:
| On Fri, Oct 30, 2009 at 8:29 PM, Steven D'Aprano wrote:
| >> > Iterating over an iterable is
| >> > what iterators are for.
| >
| > set.get(), or set.pick() as Wikipedia calls it, isn't for iterating over
| > sets. It is for getting an arbitrary ele
Curt Hagenlocher skrev:
Does that not happen on non-Windows platforms? 2**31 can't be
represented as a 32-bit signed integer, so it's automatically promoted
to a long.
Yes you are right.
I've now traced down the problem to an integer overflow in NumPy.
It seems to have this Pyrex code:
cd
On Sun, Nov 1, 2009 at 8:22 PM, Sturla Molden wrote:
>
> Why does this happen?
>
> >>> type(2**31-1)
>
Does that not happen on non-Windows platforms? 2**31 can't be
represented as a 32-bit signed integer, so it's automatically promoted
to a long.
--
Curt Hagenlocher
c...@hagenlocher.org
___
Why does this happen?
>>> type(2**31-1)
It seems to have broken NumPy's RNG on Win32.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/pyth
On Sun, Nov 1, 2009 at 13:39, Raymond Hettinger wrote:
>> As I said: Python 2 support is not only about supporting old versions of
>> Python,
>> but also supporting users of Python2-only modules. So 2.7 support will
>> for the most part be a case not of supporting Python versions, but
>> Python *u
Antoine Pitrou wrote:
> Christian Heimes cheimes.de> writes:
>> +1 from me. I trust you like Brett does.
>>
>> How much work would it cost to make your patch optional at compile time?
>
> Quite a bit, because it changes the logic for processing asynchronous pending
> calls (signals) and asynchron
Christian Heimes cheimes.de> writes:
>
> +1 from me. I trust you like Brett does.
>
> How much work would it cost to make your patch optional at compile time?
Quite a bit, because it changes the logic for processing asynchronous pending
calls (signals) and asynchronous exceptions in the eval lo
Antoine Pitrou wrote:
> Based on this whole discussion, I think I am going to merge the new GIL work
> into the py3k branch, with priority requests disabled.
>
> If you think this is premature or uncalled for, or if you just want to review
> the changes before making a judgement, please voice up :
As I said: Python 2 support is not only about supporting old versions of Python,
but also supporting users of Python2-only modules. So 2.7 support will
for the most part be a case not of supporting Python versions, but
Python *users*. And contrary to what Antoine said, that *is* a good
reason to b
2009/10/29 Nick Coghlan :
> Lennart Regebro wrote:
>> 2009/10/28 Antoine Pitrou :
>>> pobox.com> writes:
>> So 2.7 support will for the most part be a case not of supporting
>> Python versions, but Python *users*.
Antoine> That's still not a good reason to backport
On Sun, Nov 1, 2009 at 03:33, Antoine Pitrou wrote:
>
> Hello again,
>
> Brett Cannon python.org> writes:
>>
>> I think it's worth it. Removal of the GIL is a totally open-ended problem
>> with no solution in sight. This, on the other hand, is a performance benefit
>> now. I say move forward with
Le lundi 02 novembre 2009 à 08:02 +1100, Robert Collins a écrit :
>
> The FAT rounding issue is a possibility, but I didn't think reiserfs was
> short that much precision.
>
> I'd check that the work area you had really was reiser, not a mounted AT
> partition, and if its not look up the ReiserFS
On Sun, 2009-11-01 at 12:03 -0500, Eric Smith wrote:
> Antoine Pitrou wrote:
> > Adam Olsen gmail.com> writes:
> >> Looks like an OS bug to me. Linux I'm guessing?
> >
> > Yes, but only on certain boxes. I could never reproduce on my home box.
> > RDM (David)'s buildbot is a Gentoo vserver with
On 31 Oct, 08:13 pm, solip...@pitrou.net wrote:
Martin v. L�wis v.loewis.de> writes:
Not sure whether it's still relevant after the offers of individually
donated hardware.
We'll see, indeed.
However, if you want to look into this, feel free to
set up EC2 slaves.
I only know to setup main
Antoine Pitrou wrote:
Adam Olsen gmail.com> writes:
Looks like an OS bug to me. Linux I'm guessing?
Yes, but only on certain boxes. I could never reproduce on my home box.
RDM (David)'s buildbot is a Gentoo vserver with a reiserfs filesystem.
You'll occasionally see something similar on Wi
Adam Olsen gmail.com> writes:
>
> Looks like an OS bug to me. Linux I'm guessing?
Yes, but only on certain boxes. I could never reproduce on my home box.
RDM (David)'s buildbot is a Gentoo vserver with a reiserfs filesystem.
___
Python-Dev mailing l
On Sun, Nov 1, 2009 at 08:23, Antoine Pitrou wrote:
> Hello,
>
> I wondered if someone had a clue about the following behaviour.
> While debugging an erratic test_mailbox failure on RDM's buildbot (and other
> machines), it turned out that the system sometimes set the wrong mtime on a
> directory:
Hello,
I wondered if someone had a clue about the following behaviour.
While debugging an erratic test_mailbox failure on RDM's buildbot (and other
machines), it turned out that the system sometimes set the wrong mtime on a
directory:
$ date && python -c 'import os; os.link("setup.py", "t/c")' &&
Am Sonntag, 1. November 2009 12:21:15 schrieben Sie:
> It seems that even those originally asking for set retrieval have gone
> silent
Nope. Stilll following and waiting for the verdict of the community after
having filed the corpus delicti [1]
wr
[1]: http://bugs.python.org/issue7212
__
Hello again,
Brett Cannon python.org> writes:
>
> I think it's worth it. Removal of the GIL is a totally open-ended problem
> with no solution in sight. This, on the other hand, is a performance benefit
> now. I say move forward with this. If it happens to be short-lived because
> some actua
It seems that even those originally asking for set retrieval have gone
silent, so I guess this isn't going anywhere.
However, for the benefit of future discussions (because I'm sure this
question will be raised again), I'd like to answer a couple of points
raised by Stephen.
On Sat, 31 Oct 200
22 matches
Mail list logo
