[issue8269] Missing return values for PyUnicode C/API functions

Arnaud Fontaine added the comment: I meant whether it returns a new reference or not. For instance, documentation for PyUnicode_FromObject() and PyUnicode_AsWideChar() states that a new reference is returned, but this is most specified for most functions in Unicode Object (at least). ---

[issue8269] Missing return values for PyUnicode C/API functions

Arnaud Fontaine added the comment: I meant whether it returns a new reference or not. For instance, documentation for PyUnicode_FromObject() and PyUnicode_AsWideChar() states that a new reference is returned, but this is not specified for most functions in Unicode Object (at least).

[issue3445] Ignore missing attributes in functools.update_wrapper

Changes by Yoann Aubineau : -- nosy: +yaubi ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8240] ssl.SSLSocket.write may fail on non-blocking sockets

Cyril added the comment: I had a look at how M2Crypto and pyOpenSSL handled this: - M2Crypto has wrappers around SSL_set_mode that let you set the modes you want. From their changelog [1], it was required to be able to operate with Twisted. By default, though, they only set SSL_MODE_AUTO_RET

[issue8260] When I use codecs.open(...) and f.readline() follow up by f.read() return bad result

Amaury Forgeot d'Arc added the comment: Buffering applies when writing, not when reading a file. There is indeed a problem in codecs.py: after a readline(), read() will return the content of the internal buffer, and not more. The "size" parameter is a hint, and should not be used to decide wh

[issue8260] When I use codecs.open(...) and f.readline() follow up by f.read() return bad result

Marc-Andre Lemburg added the comment: Amaury Forgeot d'Arc wrote: > > Amaury Forgeot d'Arc added the comment: > > Buffering applies when writing, not when reading a file. > > There is indeed a problem in codecs.py: after a readline(), read() will > return the content of the internal buffer,

[issue4256] optparse: provide a simple way to get a programmatically useful list of options

Filip Gruszczyński added the comment: Are you saying, that for example for this: grusz...@gruszczy-laptop:~/Programs/logbuilder$ ./logbuilder --help Usage: logbuilder [options] repo Options: --version show program's version number and exit -h, --helpshow this help m

[issue8260] When I use codecs.open(...) and f.readline() follow up by f.read() return bad result

Amaury Forgeot d'Arc added the comment: Updated patch. [I also tried to avoid reading the underlying file if len(self.bytebuffer)>=size, but it does not work with multibytes chars when size=1] -- Added file: http://bugs.python.org/file16706/codecs_read-2.patch __

[issue8273] move test_support into the unittest package

New submission from Tarek Ziadé : Let's move test_support in unittest ! Then maybe, let's expose some of test_support functions into a new class on the top of unittest.TestCase, so they can be used via methods. The purpose is power up people when it comes to write test fixtures or work in a

[issue8273] move test_support into the unittest package

Michael Foord added the comment: Hmmm... I'm not sure moving everything as is is a good idea. Any parts in particular you want? -- ___ Python tracker ___ ___

[issue8273] move test_support into the unittest package

Tarek Ziadé added the comment: Basically, all the APIs in test_support could live in unittest and the test package could only contain the test modules written for Python. IOW, these tests helpers can help more people than the core devs -- ___ Pytho

[issue8273] move test_support into the unittest package

Michael Foord added the comment: Not all the APIs are appropriate though, for example TestFailed and TestSkipped are not needed. Some of the APIs only make sense for the test_support runner and unittest has its own runner now. I think the proposal needs to be more specific about which APIs yo

[issue8273] move test_support into the unittest package

Tarek Ziadé added the comment: Sure, no need to have the test runner parts. -- ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue8273] move test_support into the unittest package

Michael Foord added the comment: So which parts, can you list the ones you think are most important? At the moment we don't have to maintain backwards compatibility with test.test_support as it isn't a 'public' API - so the cost in adding it to the standard library is the same as adding any c

[issue8273] move test_support into the unittest package

R. David Murray added the comment: Actually, the list Terek posted a link to is a public doc page, and as was made clear in the recent issue about the check_warnings helper, we do have to maintain backward compatibility. There (should be) undocumented stuff in test_support, purposely left

[issue8273] move test_support into the unittest package

Florent Xicluna added the comment: > Maybe we could move the appropriate stuff and get rid of the > test_support doc page altogether. And when we move stuff to unittest > maybe we could take the opportunity to clean up any warts in the > interfaces. +1 I don't like the burden of backward comp

[issue8273] move test_support into the unittest package

Michael Foord added the comment: Right - that is exactly why I want a specific proposal as to which APIs are generally useful and should be considered for moving into unittest. -- ___ Python tracker __

[issue8193] test_zlib fails with zlib 1.2.4

R. David Murray added the comment: Nick's point is that we should be testing both the value 0 and the value -1, but that we should expect 0 to fail only if zlib.ZLIB_VERSION is less than 1.2.4. So you'll need to update your patch to keep the 0 test but put it inside an appropriate conditiona

[issue8273] move test_support into the unittest package

Michael Foord added the comment: Sorry, missed David's comment: > Maybe we could move the appropriate stuff and get rid of the > test_support doc page altogether. And when we move stuff to unittest > maybe we could take the opportunity to clean up any warts in the > interfaces. This I agree w

[issue8273] move test_support into the unittest package

Tarek Ziadé added the comment: Yes, let's make things explicit as David said: - "test" package: tests for Python itself, with private stuff, undocumented. - "unittest" package: the test framework that is used by the test package and that is public I'd add a support module in unittest, conta

[issue8233] extend py_compile to compile files from stdin

Changes by Matthias Klose : -- nosy: +doko ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue8233] extend py_compile to compile files from stdin

Changes by Matthias Klose : -- keywords: +needs review -patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue8193] test_zlib fails with zlib 1.2.4

Valerio added the comment: This was clear. Now i make a new patch and then upload it. -- ___ Python tracker ___ ___ Python-bugs-list m

[issue8273] move test_support into the unittest package

Michael Foord added the comment: A 'support' sub-module in unittest is ok. I wonder if it is the best name? - is_jython This is too specific and ignores the other implementations. This information is also available from sys / platform modules. -1 - TESTFN This is a global for setting the

[issue8273] move test_support into the unittest package

Tim Golden added the comment: On 31/03/2010 14:20, Michael Foord wrote: > - TESTFN > > This is a global for setting the directory temporary files are created in? > Don't think I like the global approach. Which functions is it used by? It's used *all over the place*. I started trying to rip it

[issue8193] test_zlib fails with zlib 1.2.4

Changes by Valerio : Removed file: http://bugs.python.org/file16691/8193.patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue1083] Confusing error message when dividing timedelta using /

Miki Tebeka added the comment: It's marked on 2.7 due to the following (this is svn 79528) >>> from datetime import timedelta >>> d = timedelta(1) >>> d / 2 datetime.timedelta(0, 43200) >>> d // 2 datetime.timedelta(0, 43200) >>> from __future__ import division >>> d / 2 Traceback (most recent

[issue8273] move test_support into the unittest package

Tarek Ziadé added the comment: about : cpython_only / is_jython I think the idea here is to mark some tests as being specific to some implementations. I remember a discussion where we said that we could add in sys or platform the name of the implementation and make this somehow future-proof.

[issue8273] move test_support into the unittest package

Michael Foord added the comment: Something like this was discussed at the language summit. Now we have the skip decorators it is easy to skip tests on certain platforms or only run them on certain platforms. The cpython_only decorator is fine - but I'd prefer a general solution rather than i

[issue8193] test_zlib fails with zlib 1.2.4

Valerio added the comment: Here's the new patch. It's ok? -- Added file: http://bugs.python.org/file16707/8193.patch ___ Python tracker ___ __

[issue8193] test_zlib fails with zlib 1.2.4

Michael Foord added the comment: Looks good to me. -- nosy: +michael.foord ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue8274] test_run failing

New submission from Zubin Mithra : == FAIL: test_run (distutils2.tests.test_build_clib.BuildCLibTestCase) -- Traceback (most recent call last): File "/media/d

[issue8193] test_zlib fails with zlib 1.2.4

Antoine Pitrou added the comment: Shouldn't it be zlib.ZLIB_VERSION < '1.2.4' rather than zlib.ZLIB_VERSION <= '1.2.4' ? -- nosy: +pitrou ___ Python tracker ___ _

[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0

Changes by Daniel Graña : -- nosy: +dangra ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0

Daniel Graña added the comment: Some background for this report at http://stackoverflow.com/questions/2547262/why-is-python-decode-replacing-more-than-the-invalid-bytes-from-an-encoded-string/2548480 -- ___ Python tracker

[issue8193] test_zlib fails with zlib 1.2.4

R. David Murray added the comment: Are we safe using string comparison here? How likely is zlib to get into double digit release numbers? (Too bad the version comparison stuff Tarek is working on isn't already available.) -- ___ Python tracker <

[issue8193] test_zlib fails with zlib 1.2.4

Amaury Forgeot d'Arc added the comment: Note that the exact version which changed the behavior is 1.2.3.5, see http://www.zlib.net/ChangeLog.txt - Use zlib header window size if windowBits is 0 in inflateInit2() -- ___ Python tracker

[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0

Changes by R. David Murray : -- nosy: +lemburg ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue8193] test_zlib fails with zlib 1.2.4

R. David Murray added the comment: The else branch of the test should also check that 0 does *not* raise an error. -- ___ Python tracker ___ _

[issue8193] test_zlib fails with zlib 1.2.4

Antoine Pitrou added the comment: Ok, actually Python is only echoing the error return from zlib here, so I don't seen the point of the conditional. Just always test against -1 and we're done. -- ___ Python tracker

[issue8225] Wrong link in xml.etree documentation

Éric Araujo added the comment: Hello Is it ok that the code checks “object.__name__ not in ('xml.etree')”? Looks like a failed single-item tuple to me. Besides, what about using a simple “!=”? Regards -- nosy: +merwok ___ Python tracker

[issue1771] Remove cmp parameter to list.sort() and builtin.sorted()

METAL XXX added the comment: I have a tree: A / \ B C / \ D E which is implemented as a dict tree = { 'A': set(['B', 'C']), 'B': set(['D', 'E']), 'C': set(), 'D': set(), 'E': set(), } I want to sort the nodes. and I don't know how to write a key function for sort() in thi

[issue8193] test_zlib fails with zlib 1.2.4

Valerio added the comment: @pitrou: because the op have the problem with 1.2.4 version of zlib. By the way i had just always test against -1 in my first patch. Make i a new patch with a simple correction with -1 in place of 0? @david: i know, but i'm learning now the TDD, so excuse me if i ma

[issue8225] Wrong link in xml.etree documentation

Brian Curtin added the comment: Good catch. That was intended to be a single tuple because the other check above is a tuple, but because this really only checks one thing it could be a != until its necessary to be a tuple. I'll fix it. -- ___ Pytho

[issue1771] Remove cmp parameter to list.sort() and builtin.sorted()

David Albert Torpey added the comment: > sorted(tree, cmp=lambda x, y: 1 if x in tree[y] else -1 if y in tree[x] else > 0) > > and it gets ['A', 'C', 'B', 'E', 'D']. That cmp function is nonsense and isn't even close to being correct: >>> from random import shuffle >>> for i in range(10): ...

[issue8225] Wrong link in xml.etree documentation

Brian Curtin added the comment: Made the change in r79529 through 79532. -- ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0

Marc-Andre Lemburg added the comment: I guess the term "failing" byte somewhat underdefined. Page 95 of the standard PDF (http://www.unicode.org/versions/Unicode5.2.0/ch03.pdf) suggests to "Replace each maximal subpart of an ill-formed subsequence by a single U+FFFD". Fortunately, they expla

[issue8269] Missing return values for PyUnicode C/API functions

Marc-Andre Lemburg added the comment: Arnaud Fontaine wrote: > > Arnaud Fontaine added the comment: > > I meant whether it returns a new reference or not. For instance, > documentation for PyUnicode_FromObject() and PyUnicode_AsWideChar() states > that a new reference is returned, but this

[issue8273] move test_support into the unittest package

Brett Cannon added the comment: I take the blame on documenting the handful of things in test.support; I thought it was a good idea to expose the handful of things that had an actual design to them. =) But yes, we should probably shift to test.support to being private and simply exposing the

[issue1771] Remove cmp parameter to list.sort() and builtin.sorted()

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue8273] move test_support into the unittest package

Michael Foord added the comment: I think namespacing utility functions / classes inside unittest is fine (even good), but agree that there needs to be careful thinking about APIs that are made public in this way. To a certain extent this code has already proved its utility, but up until now i

[issue8275] callback function on win64 results in bad behavior. mem leak?

New submission from Jasmit : I am testing a wrapper on Windows 64 and it seems to result in an null pointer access error ONLY when I insert a print statement in the C code. I have tested the wrapper with Python 2.6 and Python 2.7a4. In addition, I have compiled Python 2.6.5 source code and O

[issue7347] Add {Create|Delete}KeyEx to _winreg, doc and test updates

Brian Curtin added the comment: Gabriel, besides the *Ex naming, do you see anything wrong with the rest of the patch? I'd like to try and get this into 2.7 before the upcoming beta. -- ___ Python tracker

[issue1771] Remove cmp parameter to list.sort() and builtin.sorted()

METAL XXX added the comment: Sorry I ripped the code from a mess and I forget the tree is "leaflized" as tree = { 'A': set(['B', 'C', 'D', 'E']), 'B': set(['D', 'E']), 'C': set(), 'D': set(), 'E': set(), } I don't want to talk about the actual problem. I think sometime it's hard to

[issue8275] callback function on win64 results in bad behavior. mem corruption?

Changes by Jasmit : -- title: callback function on win64 results in bad behavior. mem leak? -> callback function on win64 results in bad behavior. mem corruption? ___ Python tracker

[issue1771] Remove cmp parameter to list.sort() and builtin.sorted()

R. David Murray added the comment: cmp is gone. It's chances of coming back are close enough to zero that an assertAlmostEqual test will pass :). The rest of the discussion should move to one of the general python lists. -- nosy: +r.david.murray

[issue8233] extend py_compile to compile files from stdin

Barry A. Warsaw added the comment: Slightly modified, patch committed to trunk in r79533 -- keywords: +patch -needs review ___ Python tracker ___

[issue8273] move test_support into the unittest package

Ezio Melotti added the comment: I agree that some things can be moved in unittest, however several of the function in test_support are designed specifically for being used for the python test suite. For example temp_cwd is something that could be really useful in unittest in my opinion, howev

[issue8233] extend py_compile to compile files from stdin

Barry A. Warsaw added the comment: r79536 in py3k -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue8268] Make old-style classes weak referenceable

Antoine Pitrou added the comment: Fixed in r79535. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue2521] ABC caches should use weak refs

Antoine Pitrou added the comment: > Make old-style classes weak-referenceable Now done (r79535). -- ___ Python tracker ___ ___ Python

[issue2521] ABC caches should use weak refs

Daniel Stutzbach added the comment: Cool! I will revise the patch based on your comments about my test case. -- ___ Python tracker ___ __

[issue8276] useless PyEval_CallObject function

New submission from Maciek Fijalkowski : In ceval.c there is such code: PyObject * PyEval_CallObject(PyObject *func, PyObject *arg) { return PyEval_CallObjectWithKeywords(func, arg, (PyObject *)NULL); } #define PyEval_CallObject(func,arg) \ PyEval_CallObjectWithKeywords(func, arg

[issue8276] useless PyEval_CallObject function

Antoine Pitrou added the comment: Well, #defines are not exported in shared libraries. I suppose PyEval_CallObject() was part of an old definition of the Python C-API and it was kept for compatibility. -- nosy: +pitrou ___ Python tracker

[issue8276] useless PyEval_CallObject function

Antoine Pitrou added the comment: The #define dates back from 2007, this changeset: branch: trunk user:guido date:Sat Aug 30 17:02:50 1997 +0200 files: Include/ceval.h Python/ceval.c description: [svn r8683] Inline PyObject_CallObject (Marc-Andre Lemburg). --

[issue8276] useless PyEval_CallObject function

Marc-Andre Lemburg added the comment: Antoine Pitrou wrote: > > Antoine Pitrou added the comment: > > The #define dates back from 2007, this changeset: > > branch: trunk > user:guido > date:Sat Aug 30 17:02:50 1997 +0200 > files: Include/ceval.h Python/ceval.c > de

[issue2636] Regexp 2.7 (modifications to current re 2.2.2)

Matthew Barnett added the comment: issue2636-20100331.zip is a new version of the regex module. It includes speed-ups and a minor bugfix. -- Added file: http://bugs.python.org/file16709/issue2636-20100331.zip ___ Python tracker <h

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Nir Aides : Removed file: http://bugs.python.org/file16680/bfs.patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue7946] Convoy effect with I/O bound threads and New GIL

Nir Aides added the comment: I upload a new update to bfs.patch which improves scheduling and reduces overhead. -- Added file: http://bugs.python.org/file16710/bfs.patch ___ Python tracker

[issue8193] test_zlib fails with zlib 1.2.4

Changes by Valerio : Removed file: http://bugs.python.org/file16707/8193.patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue8193] test_zlib fails with zlib 1.2.4

Valerio added the comment: While i wait for what i have to do, i corrected the patch. But there is a problem: the version of zlib '1.2.3.3' raise an error on "distutils.version" module. The problem is caused by the regex expression in the "distutils.version" module: version_re = re.compile(r

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Florent Xicluna added the comment: Now the "-Wd" and "-3" flags are active on some buildbots. And the first failures ... Need to backport fixes from py3k branch for: - cgitb "SyntaxWarning: tuple parameter unpacking has been removed in 3.x" - idlelib "reduce() not supported in 3.x; use functoo

[issue7583] doctest should normalize tabs when comparing output

Changes by anatoly techtonik : -- keywords: +patch Added file: http://bugs.python.org/file16712/issue7583.doctest.tabs.diff ___ Python tracker ___

[issue7583] [patch] doctest should normalize tabs when comparing output

Changes by anatoly techtonik : -- title: doctest should normalize tabs when comparing output -> [patch] doctest should normalize tabs when comparing output ___ Python tracker ___

[issue7585] [patch] difflib should separate filename from timestamp with tab

anatoly techtonik added the comment: depends on issue #7583 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue2521] ABC caches should use weak refs

Changes by Daniel Stutzbach : Added file: http://bugs.python.org/file16713/abc_leak.patch ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue2521] ABC caches should use weak refs

Daniel Stutzbach added the comment: New patches uploaded. I separated out the patch to add the test case, to make it easier to test before and after applying the fix. -- Added file: http://bugs.python.org/file16714/leak_test.patch ___ Python tracke

[issue2521] ABC caches should use weak refs

Changes by Daniel Stutzbach : Removed file: http://bugs.python.org/file16690/abc_leak.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7583] [patch] doctest should normalize tabs when comparing output

anatoly techtonik added the comment: http://codereview.appspot.com/848043/show -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7443] test.support.unlink issue on Windows platform

anatoly techtonik added the comment: It would be nice to see standalone test case that illustrates the problem. -- nosy: +techtonik ___ Python tracker ___ ___

[issue8276] useless PyEval_CallObject function

Maciek Fijalkowski added the comment: Yeah, I meant the function. Sorry for not being specific enough. I suppose the function is there to preserve ABI, but definitely code needed recompilation since 2007. -- ___ Python tracker

[issue8277] ElementTree won't parse comments

New submission from Patrick W. : When using xml.etree.ElementTree to parse external XML files, all XML comments within that file are being stripped out. I guess that happens because there is no comment handler in the expat parser. Example: test.xml test.py --- from xm

[issue8218] Fix typos and phrasing in the Web servers howto

Ezio Melotti added the comment: There's also an invalid link to an image just after the title "The low-level view": -.. .. image:: http.png +.. image:: http.png The image is not there though, and in r66294 only the document has been added. -- ___ P

[issue8218] Fix typos and phrasing in the Web servers howto

Éric Araujo added the comment: This is a reST comment. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue8218] Fix typos and phrasing in the Web servers howto

Ezio Melotti added the comment: If the image is missing, then the whole line can be removed. -- ___ Python tracker ___ ___ Python-bugs

[issue8218] Fix typos and phrasing in the Web servers howto

Éric Araujo added the comment: Is there a main author for this fileN? If so, they can say whether they left the link as a reminder to put the image back later, or if they were just afraid of real version control <0.4 wink> -- ___ Python tracker

[issue8218] Fix typos and phrasing in the Web servers howto

Ezio Melotti added the comment: The author is Marek Kubica, but he doesn't seem to be registered to this tracker. -- ___ Python tracker ___ _

[issue1578269] Add os.symlink() and os.path.islink() support for Windows

Brian Curtin added the comment: One last issue to solve before this goes in and I start the backport...test_tarfile.test_extract_hardlink is intermittently failing for me, which was an issue for Eric and I on an earlier version of Jason's patch. Sometimes it fails when run as a part of the wh

[issue8032] Add gdb7 hooks to make it easier to debug Python

Dave Malcolm added the comment: I'm attaching a new version of the patch (v5), against svn trunk (r79517) I've been testing these hooks by using "gdb attach" to attach to real-world python programs. When doing this with earlier versions of the hooks, gdb would pause for many seconds when pri

[issue8032] Add gdb7 hooks to make it easier to debug Python

Dave Malcolm added the comment: Adding diff from v4 to v5, for ease of review. For my reference, md5sum of v5's hooks: d3e039bb1279e71e847cc7ade10d3272 python-gdb.py -- Added file: http://bugs.python.org/file16716/diff-of-gdb7-hooks-v5-relative-to-v4.diff ___

[issue7885] test_distutils fails if Python built in separate directory

Dan Dever added the comment: Adding version 2.6 This fails for me with 2.6.5 in the same way. -- nosy: +dedded versions: +Python 2.6 ___ Python tracker ___ _

[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0

John Machin added the comment: @lemburg: "failing byte" seems rather obvious: first byte that you meet that is not valid in the current state. I don't understand your explanation, especially "does not have the high bit set". I think you mean "is a valid starter byte". See example 3 below. Ex

[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0

Ezio Melotti added the comment: Having the 'high bit set' means that the first bit is set to 1. All the continuation bytes (i.e. the 2nd, 3rd or 4th byte in a sequence) have the first two bits set to 1 and 0 respectively, so if the first bit is not set to 1 then the byte shouldn't be considere

[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0

Changes by Ezio Melotti : -- assignee: -> ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0

John Machin added the comment: @ezio.melotti: Your second sentence is true, but it is not the whole truth. Bytes in the range C0-FF (whose high bit *is* set) ALSO shouldn't be considered part of the sequence because they (like 00-7F) are invalid as continuation bytes; they are either starter

[issue8271] str.decode('utf8', 'replace') -- conformance with Unicode 5.2.0

Ezio Melotti added the comment: Yes, right now I'm considering valid all the bytes that start with '10...'. C2 starts with '11...' so it's a "failing byte". -- ___ Python tracker __