[I18n-sig] sys.(set|get)_string_encoding in 1.6

[Tamito KAJIYAMA]

"M.-A. Lemburg" <mal@lemburg.com> writes:
|
| Tamito KAJIYAMA wrote:
| > 
| > I found that sys.(get|set)defaultencoding() defined in the
| > Unicode proposal version 1.6 were implemented with different
| > names sys.(get|set)_string_encoding() in the 1.6 final release.
| > Is this an intended change?  If so, why is this incompatibility
| > introduced?
| 
| These APIs were first introduced as experiment to the CVS tree
| under the names you find in the 1.6 release. They were meant
| to provide an easy way to experiment with different default
| encodings. 
| 
| After some discussions on python-dev the outcome
| was to keep the APIs for use by site.py to set a locale
| dependent default encoding. 
| 
| This idea was then retracted some weeks later and replaced
| with the now standard ASCII default encoding which you find
| in both 1.6 and 2.0.

I see.

| So to answer your question: the sys APIs in 1.6 are to be
| considered undocumented features and should *not* be used.

Then, is there no way to set/get the default encoding in 1.6?

-- 
KAJIYAMA, Tamito <kajiyama@grad.sccs.chukyo-u.ac.jp>