Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.lang.python
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Unicode thing that causes a traceback in 2.6 and 2.7 but not in 2.5, and only when writing to a pipe, not to the terminal
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dan Stromberg  
View profile  
 More options Dec 2 2010, 1:14 am
Newsgroups: comp.lang.python
From: Dan Stromberg <drsali...@gmail.com>
Date: Wed, 1 Dec 2010 22:14:19 -0800
Local: Thurs, Dec 2 2010 1:14 am
Subject: Unicode thing that causes a traceback in 2.6 and 2.7 but not in 2.5, and only when writing to a pipe, not to the terminal
Print | Individual message | Show original | Report this message | Find messages by this author
What is this about?  It's another n~ thing, but this time in 2.x.
All I'm doing is printing a str containing a character > 127.

It works fine in 2.5, to a terminal or to a pipe.  In 2.6 and 2.7, it
fails when writing to a pipe but works fine writing to my terminal -
an mrxvt.\

I really kind of want octets to just be octets, since I'm on a Linux
system - it probably should be up to the user and their related
software to decide how those octets are interpreted.  I'm assuming
that the bytes() workarounds I'm using in 3.x aren't going to work in
2.x - it looks like bytes() is just an alias for str() in 2.6 and 2.7.

BTW, the print(line) in the traceback looks like Python 3 syntax, and
it is I guess, but it's also Python 2 compatible.  In 3.x, it's a
function with a single argument, in 2.x it's a statement with a
parenthesized expression.

Thanks!

benchbox-dstromberg:~/src/home-svn/readline0/trunk i686-pc-linux-gnu
17932 - above cmd done 2010 Wed Dec 01 09:40 PM

$ find /usr/share/jpilot -print0 | /usr/local/cpython-2.5/bin/python
./test-readline0 2>&1 | cat
/usr/share/jpilot
/usr/share/jpilot/CalendarDB-PDat.pdb
/usr/share/jpilot/MañanaDB.pdb
/usr/share/jpilot/jpilotrc.green
/usr/share/jpilot/jpilotrc.purple
/usr/share/jpilot/ContactsDB-PAdd.pdb
/usr/share/jpilot/MemoDB.pdb
/usr/share/jpilot/jpilotrc.blue
/usr/share/jpilot/ExpenseDB.pdb
/usr/share/jpilot/jpilotrc.default
/usr/share/jpilot/AddressDB.pdb
/usr/share/jpilot/ToDoDB.pdb
/usr/share/jpilot/TasksDB-PTod.pdb
/usr/share/jpilot/DatebookDB.pdb
/usr/share/jpilot/Memo32DB.pdb
/usr/share/jpilot/MemosDB-PMem.pdb
/usr/share/jpilot/jpilotrc.steel
benchbox-dstromberg:~/src/home-svn/readline0/trunk i686-pc-linux-gnu
17932 - above cmd done 2010 Wed Dec 01 09:40 PM

$ find /usr/share/jpilot -print0 | /usr/local/cpython-2.6/bin/python
./test-readline0 2>&1 | cat
/usr/share/jpilot
/usr/share/jpilot/CalendarDB-PDat.pdb
Traceback (most recent call last):
  File "./test-readline0", line 22, in <module>
    print(line)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xf1' in
position 20: ordinal not in range(128)
benchbox-dstromberg:~/src/home-svn/readline0/trunk i686-pc-linux-gnu
17932 - above cmd done 2010 Wed Dec 01 09:40 PM

$ find /usr/share/jpilot -print0 | /usr/local/cpython-2.6/bin/python
./test-readline0 2>&1
/usr/share/jpilot
/usr/share/jpilot/CalendarDB-PDat.pdb
/usr/share/jpilot/MañanaDB.pdb
/usr/share/jpilot/jpilotrc.green
/usr/share/jpilot/jpilotrc.purple
/usr/share/jpilot/ContactsDB-PAdd.pdb
/usr/share/jpilot/MemoDB.pdb
/usr/share/jpilot/jpilotrc.blue
/usr/share/jpilot/ExpenseDB.pdb
/usr/share/jpilot/jpilotrc.default
/usr/share/jpilot/AddressDB.pdb
/usr/share/jpilot/ToDoDB.pdb
/usr/share/jpilot/TasksDB-PTod.pdb
/usr/share/jpilot/DatebookDB.pdb
/usr/share/jpilot/Memo32DB.pdb
/usr/share/jpilot/MemosDB-PMem.pdb
/usr/share/jpilot/jpilotrc.steel
benchbox-dstromberg:~/src/home-svn/readline0/trunk i686-pc-linux-gnu
17932 - above cmd done 2010 Wed Dec 01 09:41 PM

$


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Piet van Oostrum  
View profile  
 More options Dec 2 2010, 12:03 pm
Newsgroups: comp.lang.python
From: Piet van Oostrum <p...@vanoostrum.org>
Date: Thu, 02 Dec 2010 13:03:58 -0400
Local: Thurs, Dec 2 2010 12:03 pm
Subject: Re: Unicode thing that causes a traceback in 2.6 and 2.7 but not in 2.5, and only when writing to a pipe, not to the terminal
Print | Individual message | Show original | Report this message | Find messages by this author

Dan Stromberg <drsali...@gmail.com> writes:
> What is this about?  It's another n~ thing, but this time in 2.x.
> All I'm doing is printing a str containing a character > 127.

> It works fine in 2.5, to a terminal or to a pipe.  In 2.6 and 2.7, it
> fails when writing to a pipe but works fine writing to my terminal -
> an mrxvt.\

> I really kind of want octets to just be octets, since I'm on a Linux
> system - it probably should be up to the user and their related
> software to decide how those octets are interpreted.  I'm assuming
> that the bytes() workarounds I'm using in 3.x aren't going to work in
> 2.x - it looks like bytes() is just an alias for str() in 2.6 and 2.7.

Strings are indeed byte strings (or octet strings if you prefer) in Python 2.x.

> Traceback (most recent call last):
>   File "./test-readline0", line 22, in <module>
>     print(line)
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xf1' in
> position 20: ordinal not in range(128)

This message shows that line is not a byte string but a unicode string.
If you want to output a unicode string it has to be converted to bytes
first, and Python must know which encoding to use. For output to the
terminal it can usually get that information from the system, but not
for a pipe. You will have to supply it.

By the way, if you just want to work with octets, why is the variable
line in unicode? If you keep everything in byte strings your problem may
disappear. In Python 3 you have to do this explicitely as the default is unicode.
--
Piet van Oostrum <p...@vanoostrum.org>
WWW: http://pietvanoostrum.com/
PGP key: [8DAE142BE17999C4]
Nu Fair Trade woonartikelen op http://www.zylja.com


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google