Re: OT: What's up with the starship?

rurpy@xxxxxxxxx wrote:

Then perhaps you or he could explain it to us less intelligent
people in very simple terms?

the security advisory explains that the cause of the problem is a bug
in the source code used to implement repr() for 32-bit Unicode strings, on all Python versions from 2.2 and onwards.

Python 2.2 was released in 2001.

</F>

.

Relevant Pages

  • lxml 2.1 beta3 released
    ... I'm proud to release lxml 2.1beta3 to PyPI. ... with XML and HTML in the Python language. ... the third beta contains more new features than bug ... Support for parsing from file-like objects that return unicode strings. ...
    (comp.lang.python.announce)
  • Re: Any reason why cStringIO in 2.5 behaves different from 2.4?
    ... *never* parse python unicode strings as by definition XML must be ... which is what a python string is. ... I don't care about the definition of XML at this point of the ... parseString() a convenience function. ...
    (comp.lang.python)
  • Re: Any reason why cStringIO in 2.5 behaves different from 2.4?
    ... *never* parse python unicode strings as by definition XML must be ... which is what a python string is. ... I don't care about the definition of XML at this point of the ... A sequence of unicode characters, ...
    (comp.lang.python)
  • Re: A Byte of Python - Python Book / Tutorial
    ... >>guide for anyone who wants to learn Python. ... like using Unicode strings even before you "have" to. ... you could say that a Japanese coder should just use some ... native character set that only has Japanese characters, ...
    (comp.lang.python)
  • Re: Unicode conversion in print
    ... > the 'print' statement converts Unicode strings into the encoding ... It uses the encoding of you console. ... > print 'Python encoding:', sys.getdefaultencoding ... > If stdout is a terminal, ...
    (comp.lang.python)