Issue1190

classification
Title: array unsigned char use size 2 instead of 1 on cpython
Type: behaviour Severity: major
Components: Library Versions: 2.5b0
Milestone:
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: cocoon, zyasoft
Priority: Keywords:

Created on 2008-12-04.17:35:59 by cocoon, last changed 2009-03-24.15:40:18 by cocoon.

Files
File name Uploaded Description Edit Remove
unnamed cocoon, 2009-03-19.15:46:48
unnamed cocoon, 2009-03-24.15:40:17
Messages
msg3871 (view) Author: cocoon (cocoon) Date: 2008-12-04.17:35:59
on jython: 
import array
a=array.array('B') # unsigned char
print a.sizeitem   
give 2 on jython and 1 on cpython 2.5.2
I encounter this bug in tryng to run part of google appengine on jython
msg4199 (view) Author: Jim Baker (zyasoft) Date: 2009-03-08.07:28:27
In our reading, this is implementation dependent. The actual size is now
1 byte (since we can play tricks with the underlying storage of
signed/unsigned), however, if we were to use itemsize=1, this causes
other code to fail because outside of the storage size, it can only be
properly be manipulated as a 2-byte short.
msg4312 (view) Author: cocoon (cocoon) Date: 2009-03-19.15:46:49
It's a sad news because it means i cant use google protobuf on jython !!!
i couldn't t find a workaround for it!

2009/3/8 Jim Baker <report@bugs.jython.org>

>
> Jim Baker <zyasoft@users.sourceforge.net> added the comment:
>
> In our reading, this is implementation dependent. The actual size is now
> 1 byte (since we can play tricks with the underlying storage of
> signed/unsigned), however, if we were to use itemsize=1, this causes
> other code to fail because outside of the storage size, it can only be
> properly be manipulated as a 2-byte short.
>
> ----------
> nosy: +zyasoft
> resolution:  -> wont fix
> status: open -> closed
>
> _______________________________________
> Jython tracker <report@bugs.jython.org>
> <http://bugs.jython.org/issue1190>
> _______________________________________
>
msg4318 (view) Author: Jim Baker (zyasoft) Date: 2009-03-20.23:50:07
Probably the best course of action is to use the Java version of
Google's protocol buffers. There might be some additional wrapping
involved. Regardless, it's likely to be more efficient.
msg4347 (view) Author: cocoon (cocoon) Date: 2009-03-24.15:40:18
thanks for the tip

2009/3/21 Jim Baker <report@bugs.jython.org>

>
> Jim Baker <zyasoft@users.sourceforge.net> added the comment:
>
> Probably the best course of action is to use the Java version of
> Google's protocol buffers. There might be some additional wrapping
> involved. Regardless, it's likely to be more efficient.
>
> _______________________________________
> Jython tracker <report@bugs.jython.org>
> <http://bugs.jython.org/issue1190>
> _______________________________________
>
History
Date User Action Args
2009-03-24 15:40:18cocoonsetfiles: + unnamed
messages: + msg4347
2009-03-20 23:50:07zyasoftsetmessages: + msg4318
2009-03-19 15:46:49cocoonsetfiles: + unnamed
messages: + msg4312
2009-03-08 07:28:27zyasoftsetstatus: open -> closed
resolution: wont fix
messages: + msg4199
nosy: + zyasoft
2008-12-04 17:36:00cocooncreate