[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > Unfortunately, there's no way to fix this now, since the > bug has been around since Python 1.6. Actually, there is a way to fix that: pickle could start emitting \u escapes for characters in the range 128..256. Older pickle implementation

[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: On 2008-05-28 00:21, Martin v. Löwis wrote: > Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > >> How can a data format be printable ASCII and at the same time use >> non-ASCII characters ? > > The "format" is the frame defining

[issue2877] Backport UserString move from 3.0

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: Nice patch. Thanks. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mai

[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > How can a data format be printable ASCII and at the same time use > non-ASCII characters ? The "format" is the frame defining the structure. In the binary formatter, it's a binary format. In the standard pickle format, it's ASCII (I for in

[issue2877] Backport UserString move from 3.0

Changes by Quentin Gallet-Gilles <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10455/userstring_import_fixer.patch __ Tracker <[EMAIL PROTECTED]> __ _

[issue2877] Backport UserString move from 3.0

Quentin Gallet-Gilles <[EMAIL PROTECTED]> added the comment: Attaching a patch for the deprecation warning in 2.6 of the MutableString class. The import fixer for 2to3 is coming next. -- keywords: +patch Added file: http://bugs.python.org/file10454/userstring_2.6.patch _

[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: I can't follow you, Martin. How can a data format be printable ASCII and at the same time use non-ASCII characters ? __ Tracker <[EMAIL PROTECTED]> _

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Hans Ulrich Niedermann <[EMAIL PROTECTED]> added the comment: I have written this patch because urlparse could not retrieve the hostname or port components of URIs such as http://[:::192.168.13.37]/ or http://[dead:beef::1]:/ This problem happens with Python 2.5.1 in Fedora 9, and I have

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Changes by Hans Ulrich Niedermann <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10453/python-urlparse-rfc2732-test.patch __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Changes by Hans Ulrich Niedermann <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10452/python-urlparse-rfc2732-rfc-list.patch __ Tracker <[EMAIL PROTECTED]> __ __

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

New submission from Hans Ulrich Niedermann <[EMAIL PROTECTED]>: The urlparse module's ways of splitting the location into hostname and port breaks with RFC2732 style URIs with IPv6 addresses in them: >>> import urlparse >>> urlparse.urlparse('http://[::1]:80/').hostname '[' >>> urlparse.urlparse

[issue2394] [Py3k] Finish the memoryview object implementation

Georg Brandl <[EMAIL PROTECTED]> added the comment: Raising priority. -- assignee: -> teoliphant nosy: +georg.brandl priority: -> critical __ Tracker <[EMAIL PROTECTED]> __ _

[issue2986] difflib.SequenceMatcher not matching long sequences

New submission from Nate <[EMAIL PROTECTED]>: The following code shows no matches though the strings clearly match. from difflib import * a = '''39043203381559556628573221727792187279924711093861125152794523529732793117520068565885125032447020125028126531603069277213510312502702798781521250210

[issue2985] xmlrpclib doesn't support 64bit integer replies

Riku Lindblad <[EMAIL PROTECTED]> added the comment: I attached a patch that seems to fix the problem, needs proper testing though. -- keywords: +patch Added file: http://bugs.python.org/file10450/xmlrpclib-64bitsupport.diff __ Tracker <[EMAIL PROTECTED]>

[issue2985] xmlrpclib doesn't support 64bit integer replies

New submission from Riku Lindblad <[EMAIL PROTECTED]>: When querying a XML-RPC server that returns a 64 bit integer, the python interface always returns an empty tuple. When running with verbose=True the response is still intact, the library just can't parse the result between the tags. Exampl

[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: I think the documentation is fine as it stands. The format is ASCII - even though the payload might not be. -- nosy: +loewis __ Tracker <[EMAIL PROTECTED]> _

[issue2940] Building Python fails on SunOS

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Closing the report as "invalid" then (and I strongly recommend to remove gcc 2.6.3 right away. It obviously cannot be used to compile software on your system). -- resolution: -> invalid status: open -> closed __

[issue2984] test_dbm fails on Darwin

New submission from Ismail Donmez <[EMAIL PROTECTED]>: test test_dbm failed -- Traceback (most recent call last): File "/Users/cartman/Sources/py3k/Lib/test/test_dbm.py", line 121, in test_whichdb self.assertEqual(name, dbm.whichdb(_fname)) AssertionError: 'dbm.gnu' != 'dbm.ndbm' This hap

[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: Actually, I was wrong: protocol 0 is the default if you don't specify the protocol. This set the binary flag to false, which should result in ASCII-only data. The Unicode save routine uses the raw-unicode-escape codec, but this only esca

[issue2980] Pickle stream for unicode object may contain non-ASCII characters.

Marc-Andre Lemburg <[EMAIL PROTECTED]> added the comment: Only pickle protocol 0 is ASCII. The other two are binary protocols. Protocol 2 is default in Python 2.5. This should probably be made clear in the documentation, so I'd consider this a documentation bug. -- nosy: +lemburg

[issue2877] Backport UserString move from 3.0

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: Yes. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue2983] Ttk support for Tkinter

New submission from Guilherme Polo <[EMAIL PROTECTED]>: Hello, this issue could be considered an extension of issue2618 and maybe I should have continued there but.. continuing, I'm proposing the inclusion of a ttk module (should be renamed to Ttk for python 2.x) that would fit inside lib-tk or

[issue1948] Cant open python gui using VISTA

safe alattar <[EMAIL PROTECTED]> added the comment: still cant get it to work On Thu, May 22, 2008 at 9:33 AM, Kurt B. Kaiser <[EMAIL PROTECTED]> wrote: > > Kurt B. Kaiser <[EMAIL PROTECTED]> added the comment: > > No response from OP, closing. > > -- > resolution: -> works for me > st

[issue2878] Backport UserList move in 3.0

Quentin Gallet-Gilles <[EMAIL PROTECTED]> added the comment: Attaching a patch for the import fixer of UserList. -- keywords: +patch nosy: +quentin.gallet-gilles Added file: http://bugs.python.org/file10448/userlist_import_fixer.patch __ Tracker <[EMAIL P

[issue2877] Backport UserString move from 3.0

Quentin Gallet-Gilles <[EMAIL PROTECTED]> added the comment: I only see UserString in the collections module. Has MutableString been removed in 3.0 ? -- nosy: +quentin.gallet-gilles __ Tracker <[EMAIL PROTECTED]> ___

[issue2613] inconsistency with bare * in parameter list

Buck Golemon <[EMAIL PROTECTED]> added the comment: If there's no difference then they should work the same? I agree there's probably little value in 'fixing' it. __ Tracker <[EMAIL PROTECTED]> __

[issue2613] inconsistency with bare * in parameter list

Guido van Rossum <[EMAIL PROTECTED]> added the comment: I see it differently. The rule is simply that if you use a bare * you *must* follow it with at least one argument (that's not **k). This makes sense since otherwise the * is redundant. Think about it; there is nothing different between de