[issue41083] plistlib can't decode date from year 0

2020-06-23 Thread Michael Shields
Michael Shields added the comment: You're correct that there is no year 0, but as you see Apple does use -12-30T00:00:00Z in their plists. I did not set that in order to test plistlib; it's what I found on my system. If it's a goal that plistlib be able to parse system-g

[issue41083] plistlib can't decode date from year 0

2020-06-22 Thread Michael Shields
New submission from Michael Shields : On macOS 10.5.5: /tmp $ defaults export com.apple.security.KCN - http://www.apple.com/DTDs/PropertyList-1.0.dtd";> absentCircleWithNoReason applicationDate -12-30T00:00:00Z lastCircleStatus

[issue39446] Documentation should reflect that all dicts are now ordered

2020-01-24 Thread Michael Shields
New submission from Michael Shields : As of Python 3.7, dicts always preserve insertion order. This is mentioned briefly in the release notes, but it would also be helpful to mention it in the language reference, and in the discussion of collections.OrderedDict. -- assignee: docs

[issue10076] Regex objects became uncopyable in 2.5

2012-08-27 Thread Michael Shields
Michael Shields added the comment: It's not strictly necessary that re objects be copyable, but there's no reason to break it either. It's not strictly necessary that str or int be copyable either. This came up in code that had objects with a number of members, one of whic

[issue10076] Regex objects became uncopyable in 2.5

2010-10-12 Thread Michael Shields
Michael Shields added the comment: Here's the patch. I updated the test case and release notes also. I'm a Google employee, so this patch is covered by whatever usual copyright arrangement we have with the PSF. -- keywords: +patch Added file: http://bugs.python.org/file

[issue10076] Regex objects became uncopyable in 2.5

2010-10-12 Thread Michael Shields
New submission from Michael Shields : For many years now, the sre module has provided __copy__ and __deepcopy__ modules that raise an exception ("cannot copy this pattern object") by default, with an #ifdef to enable their implementations. Until Python 2.5, these were simply unus

[issue6169] Important comparison bug in ipaddr

2009-06-01 Thread Michael Shields
New submission from Michael Shields : The open source version of ipaddr had an important comparison bug in which it was possible for x > y and x < y. The fix for this should be applied to the Python standard library version as well. http://code.google.com/p/ipaddr-py/source/detai

[issue3959] Add Google's ipaddr.py to the stdlib

2008-09-24 Thread Michael Shields
Changes by Michael Shields <[EMAIL PROTECTED]>: -- nosy: +shields ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3959> ___ __