[issue45347] datetime subject to rounding?

Change by Daniel Fortunov : -- nosy: +dfortunov ___ Python tracker <https://bugs.python.org/issue45347> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7105] weak dict iterators are fragile because of unpredictable GC runs

Change by Daniel Fortunov : -- nosy: +dfortunov nosy_count: 15.0 -> 16.0 pull_requests: +19902 pull_request: https://github.com/python/cpython/pull/20687 ___ Python tracker <https://bugs.python.org/iss

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

Change by Daniel Fortunov : -- keywords: +patch pull_requests: +19901 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20687 ___ Python tracker <https://bugs.python.org/issu

[issue31254] WeakKeyDictionary/Mapping doesn't call __missing__

Change by Daniel Fortunov : -- keywords: +patch nosy: +dfortunov nosy_count: 4.0 -> 5.0 pull_requests: +19900 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20687 ___ Python tracker <https://bugs.python.org/i

[issue40895] weakref documentation contains cautions about dictionary mutation problems that have been solved in the implementation

New submission from Daniel Fortunov : The doccumentation at https://docs.python.org/3.10/library/weakref.html cautions that the WeakKeyDictionary and WeakValueDictionary are susceptible to the problem of dictionary mutation during iteration. These notes present the user with a problem

[issue25436] argparse.ArgumentError missing error message in __repr__

Daniel Fortunov added the comment: As Paul points out, Python 3 gives a more sensible default repr so this becomes a non-issue. Closing... -- stage: patch review -> resolved status: open -> closed versions: +Python 2.7 -Python 3.4, Python 3.5, Pyth

[issue36824] Refactor str tests to reflect that str and unicode are merged in Python 3

Change by Daniel Fortunov : -- keywords: +patch pull_requests: +13088 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36824> ___ _

[issue36824] Refactor str tests to reflect that str and unicode are merged in Python 3

Daniel Fortunov added the comment: PS opened here: https://github.com/python/cpython/pull/13172 I've tried to break down the changes into individual steps, with justification in commit messages. Happy to collapse these down into fewer commits before merge if preferred. I haven't done

[issue36824] Refactor str tests to reflect that str and unicode are merged in Python 3

Daniel Fortunov added the comment: Agreed. This functionality is in `BaseTest` (which is the base for `CommonTest`) and I don't propose to change this. -- ___ Python tracker <https://bugs.python.org/issue36

[issue36824] Refactor str tests to reflect that str and unicode are merged in Python 3

New submission from Daniel Fortunov : Unit tests of `str` and related types (e.g. `UserString`) contain nomenclature and structure that dates back to the Python 2 distinction between `str` and `unicode`. Previously it was undesirable to disturb the structure of these tests too much

[issue36582] collections.UserString encode method returns a string

Daniel Fortunov added the comment: PR submitted here: https://github.com/python/cpython/pull/13138 Rather than adding three different tests for the different code paths I chose to collapse the three different code paths by surfacing the underlying str.encode() defaults in the method

[issue36582] collections.UserString encode method returns a string

Change by Daniel Fortunov : -- keywords: +patch pull_requests: +13051 stage: needs patch -> patch review ___ Python tracker <https://bugs.python.org/issu

[issue36582] collections.UserString encode method returns a string

Daniel Fortunov added the comment: I'll pick this up in the PyCon US 2019 sprint this afternoon. -- nosy: +dfortunov ___ Python tracker <https://bugs.python.org/issue36

[issue35226] mock.call equality surprisingly broken

Change by Daniel Fortunov : -- nosy: +dfortunov ___ Python tracker <https://bugs.python.org/issue35226> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25436] argparse.ArgumentError missing error message in __repr__

Daniel Fortunov added the comment: Paul, Thanks for your comprehensive reply. I agree with everything you've said and the reason I've taken so long to reply is that I've been racking my brains to remember exactly how I came across this scenario. I did at some point see an ArgumentError

[issue25436] argparse.ArgumentError missing error message in __repr__

New submission from Daniel Fortunov: ArgumentError's __init__() fails to call super(), meaning that the base exception doesn’t get a message, and thus repr() always returns “argparse.ArgumentError()” with no message. Not very helpful if that repr gets logged, or included in another error

[issue12862] ConfigParser does not implement comments need to be preceded by a whitespace character correctly

New submission from Daniel Fortunov pythonbugtrac...@danielfortunov.com: ConfigParser does not implement comments need to be preceded by a whitespace character correctly and in most cases will treat a value beginning with a comment character as a comment, even though it is not preceded