On 26 March 2015 at 12:40, Zachary Ware wrote:
> On Mar 25, 2015 9:28 PM, "Nick Coghlan" wrote:
>>
>> On 26 March 2015 at 01:57, Steve Dower wrote:
>> > Zachary Ware wrote:
>> >> On Mar 25, 2015 4:22 AM, "Paul Moore" wrote:
>> >>> On a related note, is there any information available on how the
On Mar 25, 2015 9:28 PM, "Nick Coghlan" wrote:
>
> On 26 March 2015 at 01:57, Steve Dower wrote:
> > Zachary Ware wrote:
> >> On Mar 25, 2015 4:22 AM, "Paul Moore" wrote:
> >>> On a related note, is there any information available on how the
> >>> "externals" repo is maintained? In particular, s
On 26 March 2015 at 01:57, Steve Dower wrote:
> Zachary Ware wrote:
>> On Mar 25, 2015 4:22 AM, "Paul Moore" wrote:
>>> On a related note, is there any information available on how the
>>> "externals" repo is maintained? In particular, should things in there
>>> be exact copies of upstream, or is
Zachary Ware wrote:
> On Mar 25, 2015 4:22 AM, "Paul Moore" wrote:
>> On a related note, is there any information available on how the
>> "externals" repo is maintained? In particular, should things in there
>> be exact copies of upstream, or is it OK to include extra data (in
>> this case, the re
>> I don't think the compiler can determine the order in
>> all cases. Consider:
>>
>> class Spam:
>>
>> if moon_is_full:
>> alpha = 1
>> beta = 2
>> else:
>> beta = 2
>> alpha = 1
>
> This is also expected to work in class namespaces:
>
> locals()["alpha"] = 1
On Mar 25, 2015 4:22 AM, "Paul Moore" wrote:
>
> On 25 March 2015 at 09:09, Antoine Pitrou wrote:
> > I'm not sure we guarantee anything. In any case, it's only a small
> > proportion of the kind of crashes you can get by messing the signature.
>
> Fair point. I guess what I'm asking is, would it
On 24 March 2015 at 08:22, Greg Ewing wrote:
> Martin Teichmann wrote:
>>
>> maybe
>> we could just change the compiler to leave the order in which things are
>> defined
>> in a class in the class namespace, say as a member __order__? Then we
>> could
>> use plain-old dicts for the class namespace
On Wed, 25 Mar 2015 09:22:01 +
Paul Moore wrote:
> On 25 March 2015 at 09:09, Antoine Pitrou wrote:
> > I'm not sure we guarantee anything. In any case, it's only a small
> > proportion of the kind of crashes you can get by messing the signature.
>
> Fair point. I guess what I'm asking is, w
On 25 March 2015 at 09:09, Antoine Pitrou wrote:
> I'm not sure we guarantee anything. In any case, it's only a small
> proportion of the kind of crashes you can get by messing the signature.
Fair point. I guess what I'm asking is, would it be OK to remove the
code that checks for a stack size di
On Wed, 25 Mar 2015 08:15:18 +
Paul Moore wrote:
> On 25 March 2015 at 08:05, Maciej Fijalkowski wrote:
> > Linux crashes. The mechanism for detecting the number of arguments is
> > only available on windows (note that this is a band-aid anyway, since
> > if your arguments are of the wrong ki
On 24 Mar 2015 07:59, "Gregory P. Smith" wrote:
>
>
> On Wed, Mar 18, 2015 at 9:48 AM Barry Warsaw wrote:
>>
>> On Mar 18, 2015, at 05:31 PM, Victor Stinner wrote:
>>
>> >Does it work to pass command line options to Python in the shebang?
>>
>> Yes, but only one "word", thus -Es or -I.
>>
>> We'v
On 25 March 2015 at 08:05, Maciej Fijalkowski wrote:
> Linux crashes. The mechanism for detecting the number of arguments is
> only available on windows (note that this is a band-aid anyway, since
> if your arguments are of the wrong kind you segfault anyway). We do
> have two copies of libffi one
On Tue, Mar 24, 2015 at 11:31 PM, Paul Moore wrote:
> On 12 March 2015 at 17:44, Paul Moore wrote:
>> On 12 March 2015 at 17:26, Brett Cannon wrote:
I'm all for ditching our 'libffi_msvc' in favor of adding libffi as
another 'external' for the Windows build. I have managed to get
13 matches
Mail list logo
