[issue6430] array.array falsely advertises support for 'w' in documentation

2009-07-11 Thread Georg Brandl
Georg Brandl added the comment: OK, fixed this in r73940, r73941, r73942. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue6430] array.array falsely advertises support for 'w' in documentation

2009-07-07 Thread Ezio Melotti
Ezio Melotti added the comment: The problem seems to affect Python 2 too. See also #1268. In the online doc 'w' is not mentioned but a note about the size of 'u' that changes depending on the build should be added too. Also in the table in the Python 2 doc [1] the "Python Type" for 'unsigned int

[issue6430] array.array falsely advertises support for 'w' in documentation

2009-07-07 Thread Ezio Melotti
Ezio Melotti added the comment: Apparently 'w' and 'u' were used for wide and narrow builds respectively. In r58441 the distinction was removed and now 'u' can be either 2 or 4 bytes, depending on the build. I think that 'w' can be removed. -- nosy: +ezio.melotti __

[issue6430] array.array falsely advertises support for 'w' in documentation

2009-07-06 Thread Alexandre Vassalotti
New submission from Alexandre Vassalotti : It looks like either array's 'w' support got lost in a merge, or the documentation is just wrong. >>> import array >>> array.array('w', "hello") Traceback (most recent call last): File "", line 1, in ValueError: bad typecode (must be b, B, u, h, H,