[issue7434] general pprint rewrite

Nick Coghlan added the comment: With PEP 443 added for Python 3.4, I believe Łukasz intended to pursue a new pprint implementation based on functools.singledispatch. That has obviously missed feature freeze for Python 3.4, but it's still a reasonable idea to pursue for 3.5. In addition to Ord

[issue5131] pprint doesn't know how to print a defaultdict

Nick Coghlan added the comment: Closing this as a duplicate of issue 7434 (which is about redesigning pprint to make it easier to add support for new types) -- nosy: +ncoghlan resolution: accepted -> duplicate stage: patch review -> committed/rejected status: open -> closed superseder:

[issue8743] set() operators don't work with collections.Set instances

Nick Coghlan added the comment: Raymond, will you have a chance to look at this before 3.4rc1? Otherwise I'd like to take it. -- ___ Python tracker ___ __

[issue2226] Small _abcoll Bugs / Oddities

Nick Coghlan added the comment: Raymond, will you have a chance to look at this before 3.4rc1? Otherwise I'd like to take it. -- ___ Python tracker ___ __

[issue7475] codecs missing: base64 bz2 hex zlib hex_codec ...

Serhiy Storchaka added the comment: Docstrings for new codecs mention bytes.transform() and bytes.untransform() which are nonexistent. -- nosy: +serhiy.storchaka ___ Python tracker _

[issue20115] NUL bytes in commented lines

Serhiy Storchaka added the comment: Indeed. CPython parser reads first line '#\x00\n' and save it in the buffer. But because C strings are used here (result of decode_str()), the line is truncated to '#'. As far as this data is not ended by '\n', it considered incomplete and next line is read

[issue20121] quopri_codec newline handling

New submission from Fred Stober: While trying to encode some binary data, I encountered this behaviour of the quopri_codec: >>> '\r\n\n'.encode('quopri_codec').decode('quopri_codec') '\r\n\r\n' >>> '\n\r\n'.encode('quopri_codec').decode('quopri_codec') '\n\n' If this behaviour is really intend

[issue20115] NUL bytes in commented lines

Changes by Antoine Pitrou : -- stage: -> needs patch type: compile error -> behavior versions: +Python 3.3, Python 3.4 ___ Python tracker ___ ___

[issue13115] tp_as_{number, sequence, mapping} can't be set using PyType_FromSpec

Martin v. Löwis added the comment: Since 3.2 has seen its last bugfix release, this won't be added to 3.2 anymore. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue17432] PyUnicode_ functions not accessible in Limited API on Windows

Martin v. Löwis added the comment: This is now fixed for 3.3 and 3.4. Sorry it took so long. -- ___ Python tracker ___ ___ Python-bugs

[issue19526] Review additions to the stable ABI of Python 3.4

Changes by Martin v. Löwis : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue20120] Percent-signs (%) in .pypirc should not be interpolated

Thomas Levine added the comment: Hmm now it looks to me like this is the intended behavior. http://hg.python.org/cpython/file/ea0aa3e32ab5/Lib/test/test_configparser.py#l1541 Switching the single percent sign (%) to two (%%) in .pypirc makes it work. Maybe we can make a nicer error message thou

[issue20120] Percent-signs (%) in .pypirc should not be interpolated

Thomas Levine added the comment: The relevant section distutils/config.py seems no different in Python 2.7, so now I see this as a bug in configparser. -- ___ Python tracker __

[issue17432] PyUnicode_ functions not accessible in Limited API on Windows

Roundup Robot added the comment: New changeset ea0aa3e32ab5 by Martin v. Löwis in branch '3.3': Issue #17432: Drop UCS2 from names of Unicode functions in python3.def. http://hg.python.org/cpython/rev/ea0aa3e32ab5 New changeset 0ea09c824d9b by Martin v. Löwis in branch 'default': Merge with 3.3:

[issue20120] Percent-signs (%) in .pypirc should not be interpolated

New submission from Thomas Levine: This works fine in Python 2.7, but it fails in Python 3.3. [tlevine@wildebeest mailfest-scoreboard]$ python3 --version Python 3.3.3 [tlevine@wildebeest mailfest-scoreboard]$ python3 setup.py register sdist running register Traceback (most recent call last): F

[issue18960] First line can be executed twice

Serhiy Storchaka added the comment: Oh, I had not compiled the code after last change, so first patch is wrong. Here is fixed patch. -- Added file: http://bugs.python.org/file33307/source_encoding_second_line_2.patch ___ Python tracker

[issue19697] Document the possible values for __main__.__spec__

Nick Coghlan added the comment: I think we need to document this somewhere. Not exactly sure where though - a new subsection in the import reference, perhaps? -- title: refactor pythonrun.c to make use of specs (__main__.__spec__) -> Document the possible values for __main__.__spec__

[issue19697] refactor pythonrun.c to make use of specs (__main__.__spec__)

Eric Snow added the comment: I'm fine with leaving __spec__ as None for those remaining cases. It definitely simplifies this ticket. :) Do you see any reason to not close this one at this point? -- ___ Python tracker

<    1   2