[issue44309] Add support for yescrypt in crypt.

2021-09-23 Thread David Mandelberg 


Change by David Mandelberg :


--
nosy: +dseomn

___
Python tracker 
<https://bugs.python.org/issue44309>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue45156] mock.seal has infinite recursion with int class attributes

2021-09-09 Thread David Mandelberg 


New submission from David Mandelberg :

The code below seems to have infinite recursion in the mock.seal call with 
python 3.9.2.

from unittest import mock
class Foo:
  foo = 0
foo = mock.create_autospec(Foo)
mock.seal(foo)

--
components: Library (Lib)
messages: 401525
nosy: dseomn
priority: normal
severity: normal
status: open
title: mock.seal has infinite recursion with int class attributes
type: crash
versions: Python 3.9

___
Python tracker 
<https://bugs.python.org/issue45156>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

2021-04-09 Thread David Mandelberg 


Change by David Mandelberg :


--
nosy: +dseomn

___
Python tracker 
<https://bugs.python.org/issue24959>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue42247] unittest hides traceback frames in chained exceptions

2020-11-02 Thread David Mandelberg 


New submission from David Mandelberg :

The traceback in the output of the attached test (see below) doesn't include 
line 5, which is where the original exception is raised. I think this is 
because 
https://github.com/python/cpython/blob/b9ee4af4c643a323779fd7076e80b29d611f2709/Lib/unittest/result.py#L180-L186
 uses the `limit` parameter to try to hide the implementation of `self.fail()` 
from the traceback, but `traceback.TracebackException.format()` applies the 
limit to the chained exception. I'm not sure if that's a bug in unittest or 
traceback, but from the comment in the above part of unittest, I don't think 
it's intentional.


F
==
FAIL: test_foo (__main__.FooTest)
--
Traceback (most recent call last):
  File "foo.py", line 12, in test_foo
foo()
ValueError: foo

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "foo.py", line 14, in test_foo
self.fail('foo() raised ValueError')
AssertionError: foo() raised ValueError

--
Ran 1 test in 0.000s

FAILED (failures=1)

--
components: Library (Lib)
files: foo.py
messages: 380244
nosy: dseomn
priority: normal
severity: normal
status: open
title: unittest hides traceback frames in chained exceptions
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file49563/foo.py

___
Python tracker 
<https://bugs.python.org/issue42247>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com