[issue3676] Obsolete references to PEP 291 in py3k lib
New submission from Oren Tirosh <[EMAIL PROTECTED]>: The comments in the following modules contain references to PEP 291 or to remaining compatible with version 2.x. However, they all include non backward compatible python 3 syntax like "except x as y". decimal.py modulefinder.py pkgutil.py subprocess.py -- components: Library (Lib) messages: 71921 nosy: orent severity: normal status: open title: Obsolete references to PEP 291 in py3k lib versions: Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3676> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30156] PYTHONDUMPREFS segfaults on exit
New submission from Oren Tirosh: Reproduce: Py_DEBUG build PYTHONDUMPREFS=1 ./python -c pass (big dump of reference information) Segmentation fault git-bisected to commit 7822f151b68e40376af657d267ff774439d9adb9 -- components: Interpreter Core messages: 292232 nosy: orent, serhiy.storchaka priority: normal severity: normal status: open title: PYTHONDUMPREFS segfaults on exit type: crash versions: Python 3.6 ___ Python tracker <http://bugs.python.org/issue30156> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue30156] PYTHONDUMPREFS segfaults on exit
Oren Tirosh added the comment: In addition to fixing this - perhaps PYTHONDUMPREFS or something similar should be added to test automation? It is apparently capable of uncovering some bugs that none of the other reference and recnt debugging tools could find. -- ___ Python tracker <http://bugs.python.org/issue30156> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31839] datetime: add method to parse isoformat() output
New submission from Oren Tirosh : The object types in the datetime module can produce a standard string representation (rfc3339, a subset of iso8601) but they do not provide a method to parse it. Proposed method names: isoparse or fromisoformat. In addition, a constructor call with a single string argument may also be supported. This would make the behavior of datetime/date/time more similar to other value types such as int, str or float and maintain the same invariant of x == type(x)(str(x)) Requirements: support lossless round-tripping of all valid datetime object values to str and back, with the exception of objects having a custom tzinfo (not None or an instance of datetime.timezone). The _strptime format of '%Y-%m-%d %H:%M:S.%f%z' comes close, but fails to meet these requirements in the following ways: 1. %z matches +HHMM, not +HH:MM (addressed by issue 31800, currently discussed on datetime-sig) 2. %z does not match the empty string, indicating a naive datetime object (tzinfo=None) 3. .%f requires a fraction part, while isoformat drops it when the timestamp is an exact second (microsecond=0). -- messages: 304728 nosy: orent priority: normal severity: normal status: open title: datetime: add method to parse isoformat() output type: enhancement ___ Python tracker <https://bugs.python.org/issue31839> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
