Terry Reedy wrote:
Options 2) and 3) would ideally entail one backwards
incompatible bugfix: In 2.7 and 3.2 assignment to a memoryview
with format 'B' rejects integers but accepts byte objects, but
according to the struct syntax mandated by the PEP it should be
the other w
On Thu, Mar 1, 2012 at 11:48 AM, Terry Reedy wrote:
> * As for porting, my impression is that the PEP directly affects only C code
> and Python code using ctypes and only some fraction of those. If the
> bugfix-only patch is significantly different from complete patch, porting to
> 3.2 would be si
[erroneouly hit send button before instead of edit menu above it]
On 2/29/2012 2:34 PM, Stefan Krah wrote:
Greg Ewing wrote:
Options 2) and 3) would ideally entail one backwards
incompatible bugfix: In 2.7 and 3.2 assignment to a memoryview
with format 'B' rejects integers but accepts byte obj
On 2/29/2012 2:34 PM, Stefan Krah wrote:
Greg Ewing wrote:
Options 2) and 3) would ideally entail one backwards incompatible
bugfix: In 2.7 and 3.2 assignment to a memoryview with format 'B'
rejects integers but accepts byte objects, but according to the
struct syntax mandated by the PEP it sho
Greg Ewing wrote:
>> Options 2) and 3) would ideally entail one backwards incompatible
>> bugfix: In 2.7 and 3.2 assignment to a memoryview with format 'B'
>> rejects integers but accepts byte objects, but according to the
>> struct syntax mandated by the PEP it should be the other way round.
>
>
Antoine Pitrou wrote:
> Stefan Krah wrote:
> > In Python 3.3 most issues with the memoryview object have been fixed
> > in a recent commit (3f9b3b6f7ff0).
>
> Oh and congrats for doing this, of course.
Thanks!
Stefan Krah
___
Python-Dev mailing li
On Sun, 26 Feb 2012 14:27:21 +0100
Stefan Krah wrote:
> State of PEP-3118 (memoryview part)
>
> Hello,
>
> In Python 3.3 most issues with the memoryview object have been fixed
> in a recent commit (3f9b3b6f7ff0).
Oh and congrats for doing this, of course.
Regards
Antoine.
__
Stefan, thank you for the massive rewrite.
On 2/26/2012 11:21 AM, Paul Moore wrote:
On 26 February 2012 13:41, Antoine Pitrou wrote:
We have several options with regard to 2.7 and 3.2:
1) Won't fix.
Given the extent of the rewrite, this one has my preference.
+1 (although I'd word it a
Stefan Krah wrote:
Options 2) and 3) would ideally entail one backwards incompatible
bugfix: In 2.7 and 3.2 assignment to a memoryview with format 'B'
rejects integers but accepts byte objects, but according to the
struct syntax mandated by the PEP it should be the other way round.
Maybe a com
On 26 February 2012 13:41, Antoine Pitrou wrote:
>> We have several options with regard to 2.7 and 3.2:
>>
>> 1) Won't fix.
>
> Given the extent of the rewrite, this one has my preference.
+1 (although I'd word it as "fixed in 3.3" rather than "won't fix").
Paul.
__
+1 for won't fix.
On Feb 26, 2012 9:46 PM, "Antoine Pitrou" wrote:
> On Sun, 26 Feb 2012 14:27:21 +0100
> Stefan Krah wrote:
> >
> > The underlying problems with memoryview were intricate and required
> > a long discussion (issue #10181) that led to a complete rewrite
> > of memoryobject.c.
> >
On Sun, 26 Feb 2012 14:27:21 +0100
Stefan Krah wrote:
>
> The underlying problems with memoryview were intricate and required
> a long discussion (issue #10181) that led to a complete rewrite
> of memoryobject.c.
>
>
> We have several options with regard to 2.7 and 3.2:
>
> 1) Won't fix.
Gi
State of PEP-3118 (memoryview part)
Hello,
In Python 3.3 most issues with the memoryview object have been fixed
in a recent commit (3f9b3b6f7ff0). Many features have been added, see:
http://docs.python.org/dev/whatsnew/3.3.html
The underlying problems with memoryview were intricate and require
13 matches
Mail list logo
