[issue20192] pprint chokes on set containing frozenset

Serhiy Storchaka added the comment: Python 2.7 is no longer supported. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___

[issue20192] pprint chokes on set containing frozenset

Serhiy Storchaka added the comment: Here is reproducible on 2.7 example: import pprint, datetime, test.test_datetime naive = datetime.datetime.utcnow() aware = datetime.datetime.utcnow().replace(tzinfo=test.test_datetime.FixedOffset(-300, EST, 1)) pprint.pprint({naive, aware})

[issue20192] pprint chokes on set containing frozenset

Serhiy Storchaka added the comment: For now sets and frozensets are comparable with other types in Python 2. frozenset(xrange(10)) 1 False set(xrange(10)) 1 False The only known to me uncomparable types in Python 2 are naive and aware datetime. -- nosy: +serhiy.storchaka

[issue20192] pprint chokes on set containing frozenset

New submission from Joseph Bylund: Expected: pprint the object Observed: crash with: set([Traceback (most recent call last): File ./test.py, line 7, in module pp.pprint(myset) File /usr/lib/python2.7/pprint.py, line 117, in pprint self._format(object, self._stream, 0, 0, {}, 0)

[issue20192] pprint chokes on set containing frozenset

R. David Murray added the comment: FYI, 'crash' is for when the CPython interpreter segfaults, not when python produces a traceback. Sets and frozensets are not comparable to anything except themselves, unlike most other Python2 datatypes. In Python3, most disparate types are not