Nick Coghlan wrote:
Indeed, PEP 380 is *really* hard to do properly without language
support. The language moratorium and lack of a Python 3 compatible
patch
Pardon? My original patch was for 3.1.2.
--
Greg
___
Python-Dev mailing list
Python-Dev@pyt
On Sat, Jun 25, 2011 at 9:27 PM, Greg Ewing wrote:
> Nick Coghlan wrote:
>
>> Indeed, PEP 380 is *really* hard to do properly without language
>> support. The language moratorium and lack of a Python 3 compatible
>> patch
>
> Pardon? My original patch was for 3.1.2.
My mistake. We must have chang
At 10:46 AM 6/25/2011 +1000, Nick Coghlan wrote:
Indeed, PEP 380 is *really* hard to do properly without language
support.
No, it isn't. You add a decorator, a 'from_' class, and a 'return_'
function, and there you go. (See my previous code sketches here in
early PEP 380 discussions.)
Pyt
On Sat, 25 Jun 2011 11:31:42 -0400, "P.J. Eby" wrote:
> At 10:46 AM 6/25/2011 +1000, Nick Coghlan wrote:
> >Indeed, PEP 380 is *really* hard to do properly without language
> >support.
>
> No, it isn't. You add a decorator, a 'from_' class, and a 'return_'
> function, and there you go. (See my
I recently started looking at some ctypes issues. I dug a bit into
http://bugs.python.org/issue6069 and then I found
http://bugs.python.org/issue11920. They both boil down to the fact that
bitfield allocation is up to the compiler, which is different in GCC and
MSVC. Currently we have hard-coded al
On Sat, Jun 25, 2011 at 9:32 AM, R. David Murray wrote:
> On Sat, 25 Jun 2011 11:31:42 -0400, "P.J. Eby" wrote:
>> At 10:46 AM 6/25/2011 +1000, Nick Coghlan wrote:
>> >Indeed, PEP 380 is *really* hard to do properly without language
>> >support.
>>
>> No, it isn't. You add a decorator, a 'from_'
On 6/25/2011 12:33 PM, Vlad Riscutia wrote:
I recently started looking at some ctypes issues. I dug a bit into
http://bugs.python.org/issue6069 and then I found
http://bugs.python.org/issue11920. They both boil down to the fact that
bitfield allocation is up to the compiler, which is different in
This is the cause of both bug reports and yes, it should improve interop
with GCC-compiled code on Windows. My point is that this is not a platform
thing, it's more of a compiler thing. Currently issues appear on Windows for
interop between MSVC Python and other GCC code but since bitfield allocati
P.J. Eby wrote:
At 10:46 AM 6/25/2011 +1000, Nick Coghlan wrote:
Indeed, PEP 380 is *really* hard to do properly without language
support.
No, it isn't. You add a decorator, a 'from_' class, and a 'return_'
function, and there you go. (See my previous code sketches here in
early PEP 380 d
Vlad Riscutia wrote:
Longer term though, I think it
would be better to add a property on the Structure class for
configurable allocation strategy, for example Native (default), GCC,
MSVC
It could also be good to have a mode which lets you specify
*exactly* how the bits are laid out, independe
On Sun, Jun 26, 2011 at 2:44 AM, Guido van Rossum wrote:
> Let me cut this short. PEP 380 is pretty much approved. I know there
> are a few details worth quibbling over, but they are not going to
> jeopardize acceptance of the PEP. We are waiting for an implementation
> in Python 3.3. In fact, I w
On Sun, Jun 26, 2011 at 1:16 PM, Nick Coghlan wrote:
> On Sun, Jun 26, 2011 at 2:44 AM, Guido van Rossum wrote:
>> Let me cut this short. PEP 380 is pretty much approved. I know there
>> are a few details worth quibbling over, but they are not going to
>> jeopardize acceptance of the PEP. We are
12 matches
Mail list logo
