#155 test_iolib fails on Ubuntu 13.04 python 2.7.4

v2.6
closed-fixed
Chris Liechti
None
5
2013-10-16
2013-09-18
Matt
No

More specifically it looks like when using loop:// with the io module buffers somehow what gets written to the port is the text "<memory at="" blah="">" instead of actually writing the contents of the memory location. This problem doesn't occur with a physical and real live port, but does make the loop:// less useful.

Discussion

  • Matt
    Matt
    2013-09-19

    That was suppose to read - what gets written to the port is the text "<Memory at blah>"

     
  • Chris Liechti
    Chris Liechti
    2013-10-16

    • status: open --> closed-fixed
    • assigned_to: Chris Liechti
    • Group: v1.0 (example) --> v2.6
     
  • Chris Liechti
    Chris Liechti
    2013-10-16

    fix committed.

    The problem is the memoryview object that was introduced with Python 2.7. Calling bytes(some_memoryview_instance) returns "<memory at..="">" instead of the contents. It has a tobytes() method, which is now called. It's not that i wanted to have those isinstance() tests, but it seems to be required due to this :-(