[issue458771] unittest things to be doc'd

Change by admin : -- github: None -> 35113 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue418489] unittest string format error

Change by admin : -- github: None -> 34407 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue423224] unittest fixture finder

Change by admin : -- github: None -> 34493 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47133] enhance unittest to show test name and docstring on one line

test output formatting desires have simply adopted pytest and never looked back. --- Other python unittest derivative concepts to get clear output of results: We add a reliably machine parsable XML report of test outcomes in absl-py https://github.com/abseil/abseil-py/tree/main/absl/testing. It's

[issue46126] Unittest output drives developers to avoid docstrings

miss-islington added the comment: New changeset 84acb5cad1b871bb8729cbf1d036b84cbe1636f0 by Jason R. Coombs in branch 'main': bpo-46126: Restore 'descriptions' when running tests internally. (GH-32128) https://github.com/python/cpython/commit/84acb5cad1b871bb8729cbf1d036b84cbe1636f0

[issue46126] Unittest output drives developers to avoid docstrings

Change by Jason R. Coombs : -- pull_requests: +30349 pull_request: https://github.com/python/cpython/pull/32288 ___ Python tracker ___

[issue47133] enhance unittest to show test name and docstring on one line

Steven D'Aprano added the comment: Rather than an option for this, it would be cleaner to deprecate the current output in 3.11, and fix it in 3.12 or 3.13. Otherwise we have to maintain the old (bad?) output and the new output both forever. --

[issue47133] enhance unittest to show test name and docstring on one line

specified tests. And full path to the test's source which I can copy to run in editor. pytest output looks more user-friendly to me. But it may break other's test output parsers so we perhaps need an option for this. Options for unittest and libregrtest. I am not sure that it is a task for an average

[issue47133] enhance unittest to show test name and docstring on one line

Steven D'Aprano added the comment: I have no problem with pinging Python-Dev, or any other forum, asking for interested parties. I just don't think we should be intentionally spliting the discussion more than it's going to get split organically. (If this is interesting to people, they will

[issue47133] enhance unittest to show test name and docstring on one line

to python-dev is that issue 46126 had been active for three months and had a PR merged before another dev mentioned that verbose tests with docstrings just printed on two lines instead of one. Thank you for pointing out the possible disruption caused by unittest outpu

[issue47133] enhance unittest to show test name and docstring on one line

Steven D'Aprano added the comment: I don't think this change of behaviour should be accepted without discussion, and I'm not sure why you think Python-Dev is the right place, rather than here. Messing around with unittest and docstrings has already caused issues in the past: https

[issue47133] enhance unittest to show test name and docstring on one line

Serhiy Storchaka added the comment: Issue14265, issue46126. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list

[issue47133] enhance unittest to show test name and docstring on one line

Itay Yeshaya added the comment: I would like to work on this. -- nosy: +itay.yeshaya ___ Python tracker ___ ___ Python-bugs-list

[issue47133] enhance unittest to show test name and docstring on one line

Change by Irit Katriel : -- keywords: +easy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue47133] enhance unittest to show test name and docstring on one line

Change by Ethan Furman : -- assignee: -> ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46126] Unittest output drives developers to avoid docstrings

Ethan Furman added the comment: That makes sense. issue47133 created. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue47133] enhance unittest to show test name and docstring on one line

New submission from Ethan Furman : When running unittest with the -v flag, if a test has errors, and has a docstring, the test name is shown on one line, and the docstring is shown on the next line -- and the ERROR word is shown with the docstring. What this means is that: - the test name

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: My goal with this issue is to simply unblock the use of docstrings in Python tests. I believe with the work above and the proposed published post, I've accomplished that goal. I've already spent more time than I'd hoped on this issue and would like to

[issue46126] Unittest output drives developers to avoid docstrings

Ethan Furman added the comment: Perhaps we could make an enhancement then? Having the extra information on a separate line is, at least for me, very jarring -- as in, I hadn't figured out that that was the way it was done until Inadasan pointed it out. Perhaps a command-line switch to

[issue46126] Unittest output drives developers to avoid docstrings

Change by Jason R. Coombs : -- pull_requests: +30208 pull_request: https://github.com/python/cpython/pull/32128 ___ Python tracker ___

[issue46126] Unittest output drives developers to avoid docstrings

Change by Jason R. Coombs : -- resolution: -> works for me ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: I've confirmed that prior to the patch in PR 30194, the location of the failure was indeed reported. It was just not reported on the same line: ``` cpython main $ git log -1 commit 3e93af0b06cada874c4a16868b6f863b599919f2 (HEAD -> main) Author: Jason R.

[issue46126] Unittest output drives developers to avoid docstrings

Éric Araujo added the comment: I think the situation and the discussion should be summarized on python-dev! -- ___ Python tracker ___

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: And indeed, after removing the `grep ERROR` part of the repro, even the repro seems to be invalid: ``` cpython main $ ./python.exe -m test.test_importlib -v -k test_entry_points_unique test_entry_points_unique_packages

[issue46126] Unittest output drives developers to avoid docstrings

is clearly reported in the case of launching with `-m unittest`. I'm now suspicious that my report in https://bugs.python.org/issue46126#msg408882 was also flawed as it uses `grep ERROR`, which could easily mask lines that adjacent to the error. I now believe that there are no concerns

[issue46126] Unittest output drives developers to avoid docstrings

Inada Naoki added the comment: > As you can see, the location of the failing test in the log is masked, and > instead the description is present. Could you elaborate? ``` test_index_empty (idlelib.idle_test.test_text.MockTextTest) Failing test with bad description. ... ERROR (snip)

[issue46126] Unittest output drives developers to avoid docstrings

rror() ^^ ValueError -- Ran 14 tests in 0.001s FAILED (errors=1, skipped=14) ``` As you can see, the location of the failing test in the log is masked, and instead the description is present. I've pushed https://github.com/python/cpython/tree/bpo-46126/disable-descriptions-

[issue46421] unittest ValueError when invoking as module

Change by Jelle Zijlstra : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue46421] unittest ValueError when invoking as module

Jelle Zijlstra added the comment: New changeset 1cab44d8650ae3eece90b04fca373908205e7ee0 by Miss Islington (bot) in branch '3.9': [3.9] bpo-46421: Fix unittest filename evaluation when called as a module (GH-30654) (GH-31970) https://github.com/python/cpython/commit

[issue46421] unittest ValueError when invoking as module

miss-islington added the comment: New changeset 0b5f99ad1af0892a2d6043abd8aeb10d685d3844 by Miss Islington (bot) in branch '3.10': bpo-46421: Fix unittest filename evaluation when called as a module (GH-30654) https://github.com/python/cpython/commit/0b5f99ad1af0892a2d6043abd8aeb10d685d3844

[issue46421] unittest ValueError when invoking as module

Change by miss-islington : -- pull_requests: +30060 pull_request: https://github.com/python/cpython/pull/31970 ___ Python tracker ___

[issue46421] unittest ValueError when invoking as module

Change by miss-islington : -- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +30059 pull_request: https://github.com/python/cpython/pull/31969 ___ Python tracker

[issue46421] unittest ValueError when invoking as module

Jelle Zijlstra added the comment: New changeset a0db11b10fca0fee6bb2b8d6277e266bad8c0fdb by Bader Zaidan in branch 'main': bpo-46421: Fix unittest filename evaluation when called as a module (GH-30654) https://github.com/python/cpython/commit/a0db11b10fca0fee6bb2b8d6277e266bad8c0fdb

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

Change by Irit Katriel : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.11 -Python 3.8 ___ Python tracker ___

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

Irit Katriel added the comment: New changeset f3ea249569bbce8417c55d421521bb672c202552 by Irit Katriel in branch '3.9': bpo-24959: fix unittest.assertRaises bug where traceback entries are dropped from chained exceptions (GH-23688) (GH-31776)

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

miss-islington added the comment: New changeset 26fa25a9a73f0e31bf0f0d94103fa4de38c0a3cc by Miss Islington (bot) in branch '3.10': bpo-24959: fix unittest.assertRaises bug where traceback entries are dropped from chained exceptions (GH-23688)

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

Change by Irit Katriel : -- pull_requests: +29883 pull_request: https://github.com/python/cpython/pull/31776 ___ Python tracker ___

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

Irit Katriel added the comment: New changeset 88b7d86a73da9388aa65c96401c2984c8c16f8db by Irit Katriel in branch 'main': bpo-24959: fix unittest.assertRaises bug where traceback entries are dropped from chained exceptions (GH-23688)

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

Change by miss-islington : -- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +29882 pull_request: https://github.com/python/cpython/pull/31775 ___ Python tracker

[issue23882] unittest discovery doesn't detect namespace packages when given no parameters

Change by Inada Naoki : -- resolution: -> not a bug stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue23882] unittest discovery doesn't detect namespace packages when given no parameters

Change by Géry : -- nosy: +maggyero ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45162] Remove old deprecated unittest features

Change by Gregory P. Smith : -- assignee: gregory.p.smith -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45162] Remove old deprecated unittest features

Gregory P. Smith added the comment: New changeset b50322d20337ca468f2070eedb051a16ee1eba94 by Gregory P. Smith in branch 'main': bpo-45162: Revert "Remove many old deprecated unittest features" (GH-30935) https://github.com/python/cpython/commit/b50322d20337ca468f2070eedb051a

[issue45162] Remove old deprecated unittest features

Change by Gregory P. Smith : -- pull_requests: +29114 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/30935 ___ Python tracker ___

[issue45162] Remove old deprecated unittest features

Change by Gregory P. Smith : -- assignee: -> gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45162] Remove old deprecated unittest features

Gregory P. Smith added the comment: Per https://mail.python.org/archives/list/python-...@python.org/thread/GJTREADEXYAETECE5JDTPYWK4WMTKYGR/ we want to revert this change for 3.11 as it causes adoption pain for little benefit. To determine if we should proceed with this in 3.12 or future

[issue46421] unittest ValueError when invoking as module

Change by Bader Zaidan : -- versions: +Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46126] Unittest output drives developers to avoid docstrings

Change by Jason R. Coombs : -- assignee: -> jaraco ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: I've merged the fix for regrtest and I'll explore Terry's concerns and see what I can devise for those concerns as well. -- ___ Python tracker

[issue46126] Unittest output drives developers to avoid docstrings

miss-islington added the comment: New changeset a941e5927f7f2540946813606c61c6aea38db426 by Jason R. Coombs in branch 'main': bpo-46126: Disable 'descriptions' when running tests internally. (GH-30194) https://github.com/python/cpython/commit/a941e5927f7f2540946813606c61c6aea38db426

[issue46421] unittest ValueError when invoking as module

Change by Kumar Aditya : -- nosy: +kumaraditya303, serhiy.storchaka type: -> behavior versions: +Python 3.11, Python 3.9 ___ Python tracker ___

[issue46421] unittest ValueError when invoking as module

Change by Terry J. Reedy : -- nosy: +ezio.melotti, michael.foord, rbcollins ___ Python tracker ___ ___ Python-bugs-list mailing

[issue46421] unittest ValueError when invoking as module

Change by Bader Zaidan : -- keywords: +patch pull_requests: +28855 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30654 ___ Python tracker ___

[issue46421] unittest ValueError when invoking as module

Bader Zaidan added the comment: For reference, this is the error request: ``` python3 -m unittest ./tests/*.py Traceback (most recent call last): File "/usr/lib64/python3.10/runpy.py", line 196, in _run_module_as_main return _run_code(code, main_globals, None, File &

[issue46421] unittest ValueError when invoking as module

New submission from Bader Zaidan : When running a local unittest as a module (for example, `python -m unittest ./tests/*.py`), the command fails with a ValueError. However, if we remove the local directory definition, and call it as `python -m unittest tests/*.py`, it runs without issue

[issue23882] unittest discovery doesn't detect namespace packages when given no parameters

Inada Naoki added the comment: New changeset 0b2b9d251374c5ed94265e28039f82b37d039e3e by Inada Naoki in branch 'main': bpo-23882: unittest: Drop PEP 420 support from discovery. (GH-29745) https://github.com/python/cpython/commit/0b2b9d251374c5ed94265e28039f82b37d039e3e

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: > > I presume I don't need to explain why docstrings are nice and preferable > > over comments. > Actually, can you? I searched around and didn't find any good treatise or thorough overview of reasons _why_ docstrings should be preferred, so I performed

[issue46126] Unittest output drives developers to avoid docstrings

Change by Terry J. Reedy : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46126] Unittest output drives developers to avoid docstrings

Terry J. Reedy added the comment: I also use comments in lieu of docstrings for text_xyx methods because I find the addition of the first line of the docstring in error reports to be useless, distracting, and sometimes, depending on the content, confusing. If the error is in the test

[issue46126] Unittest output drives developers to avoid docstrings

Éric Araujo added the comment: > I presume I don't need to explain why docstrings are nice and preferable over > comments. Actually, can you? Docstrings to document regular modules, classes or functions are a fine tool, especially with tools that extract them (pydoc, sphinx). I don’t see

[issue45865] Old syntax in unittest

Serhiy Storchaka added the comment: Not worth the hassle. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45865] Old syntax in unittest

Adam Johnson added the comment: Okay, I updated the PR to only remove inheritance from object. Should I reopen the ticket? (Not sure of the etiquette.) Perhaps I could later submit a second patch for use of `super()`, and so on? -- ___ Python

[issue46126] Unittest output drives developers to avoid docstrings

Change by Jason R. Coombs : -- keywords: +patch pull_requests: +28415 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30194 ___ Python tracker ___

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: After some investigation (and tracing calls through a dozen or more layers), I found that Python's own regression tests can disable this behavior thus: ``` diff --git a/Lib/test/support/testresult.py b/Lib/test/support/testresult.py index

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: It looks like that 'descriptions' attribute is passed through from TextTestRunner, which sets it to True by default (https://github.com/python/cpython/blob/9b52920173735ac609664c6a3a3021d24a95a092/Lib/unittest/runner.py#L163). It seems that behavior isn't

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: Looks like the code, I believe here's where the reporting happens: https://github.com/python/cpython/blob/9b52920173735ac609664c6a3a3021d24a95a092/Lib/unittest/runner.py#L48-L51 I see a "description" property there that may already provide t

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: My guess is the tests were run with something like this: ``` ./python.exe -E -We -m test -v test_importlib | grep '... ERROR' Entry points should only be exposed for the first package ... ERROR test test_importlib failed ``` In that case, the location of

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: I created this diff: ```diff diff --git a/Lib/test/test_importlib/test_metadata_api.py b/Lib/test/test_importlib/test_metadata_api.py index e16773a7e8..92aacd5ad5 100644 --- a/Lib/test/test_importlib/test_metadata_api.py +++

[issue46126] Unittest output drives developers to avoid docstrings

Jason R. Coombs added the comment: Absolutely. I was thinking to do just that. -- ___ Python tracker ___ ___ Python-bugs-list

[issue46126] Unittest output drives developers to avoid docstrings

Ethan Furman added the comment: Could you give a couple examples for those of us not familiar with the problem? -- nosy: +ethan.furman ___ Python tracker ___

[issue46126] Unittest output drives developers to avoid docstrings

New submission from Jason R. Coombs : In https://github.com/python/importlib_metadata/issues/302, I learned that the way unittest reports failures in tests is incentivizing the replacement of docstrings with comments in order not to make resolution of the relevant failing test more difficult

[issue12681] unittest expectedFailure could take a message argument like skip does

Serhiy Storchaka added the comment: Such change would break a lot of existing interfaces. * addUnexpectedSuccess() has a single parameter. The change will add the second parameter and will break subclasses of TestResult. * addExpectedFailure() has two parameter. The change will add the third

[issue20165] unittest TestResult wasSuccessful returns True when there are unexpected successes

Serhiy Storchaka added the comment: See also issue22815. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list

[issue22858] unittest.__init__:main shadows unittest.main

Change by Irit Katriel : -- versions: +Python 3.11 -Python 3.5 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue13236] unittest needs more flush calls

Łukasz Langa added the comment: Thanks, Serhiy! ✨  ✨ -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue13236] unittest needs more flush calls

Łukasz Langa added the comment: New changeset d55a03e02e69fb7f639998de71ed3f44c2f4f999 by Miss Islington (bot) in branch '3.9': [3.10] bpo-13236: Flush the output stream more often in unittest (GH-29929) (GH-30039) https://github.com/python/cpython/commit

[issue13236] unittest needs more flush calls

Łukasz Langa added the comment: New changeset 83fa1291fd0a25216a4a9e990f423682fda67cbe by Serhiy Storchaka in branch '3.10': [3.10] bpo-13236: Flush the output stream more often in unittest (GH-29864) (GH-29929) https://github.com/python/cpython/commit

[issue13236] unittest needs more flush calls

Change by miss-islington : -- nosy: +miss-islington nosy_count: 9.0 -> 10.0 pull_requests: +28265 pull_request: https://github.com/python/cpython/pull/30039 ___ Python tracker

[issue46012] unittest AsyncConnection not described

Change by Andrew Svetlov : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue46012] unittest AsyncConnection not described

Serhiy Storchaka added the comment: There is no AsyncConnection in unittest nor anywhere in the stdlib. It is just an example illustrating the order of calling setup and teardown methods and cleanup callbacks. -- nosy: +serhiy.storchaka

[issue46012] unittest AsyncConnection not described

: unittest AsyncConnection not described versions: Python 3.10 ___ Python tracker <https://bugs.python.org/issue46012> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue13236] unittest needs more flush calls

Change by Serhiy Storchaka : -- pull_requests: +28153 pull_request: https://github.com/python/cpython/pull/29929 ___ Python tracker ___

[issue13236] unittest needs more flush calls

Serhiy Storchaka added the comment: New changeset f42a06ba279c916fb67289e47f9bc60dc5dee4ee by Serhiy Storchaka in branch 'main': bpo-13236: Flush the output stream more often in unittest (GH-29864) https://github.com/python/cpython/commit/f42a06ba279c916fb67289e47f9bc60dc5dee4ee

[issue13236] unittest needs more flush calls

Serhiy Storchaka added the comment: I do not remember details, but I encountered this issue (maybe when run tests in subprocesses?). -- ___ Python tracker ___

[issue13236] unittest needs more flush calls

Change by Serhiy Storchaka : -- versions: +Python 3.10, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue13236] unittest needs more flush calls

Change by Serhiy Storchaka : -- keywords: +patch nosy: +serhiy.storchaka nosy_count: 7.0 -> 8.0 pull_requests: +28091 stage: test needed -> patch review pull_request: https://github.com/python/cpython/pull/29864 ___ Python tracker

[issue13236] unittest needs more flush calls

Irit Katriel added the comment: Reproduced on 3.11. -- nosy: +iritkatriel versions: +Python 3.11 -Python 2.7, Python 3.2 ___ Python tracker ___

[issue15010] unittest: _top_level_dir is incorrectly persisted between calls to different load_test methods

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.11 -Python 2.7, Python 3.7, Python 3.8 ___ Python tracker ___ ___

[issue23882] unittest discovery doesn't detect namespace packages when given no parameters

Change by Inada Naoki : -- versions: +Python 3.11 -Python 3.10, Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list

[issue23882] unittest discovery doesn't detect namespace packages when given no parameters

Change by Inada Naoki : -- pull_requests: +27982 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/29745 ___ Python tracker ___

[issue45865] Old syntax in unittest

Serhiy Storchaka added the comment: Concur with Eric. -- nosy: +serhiy.storchaka resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue45865] Old syntax in unittest

Eric V. Smith added the comment: As a general rule, we don't accept large patches with changes like this. The chance for breakage somewhere in the 27 files is too high. I could see maybe dropping inheriting from object, since that's relatively safe. -- nosy: +eric.smith

[issue23882] unittest discovery doesn't detect namespace packages when given no parameters

Adam Johnson added the comment: I just reported https://bugs.python.org/issue45864 , and closed as duplicate of this. -- nosy: +adamchainz ___ Python tracker ___

[issue45864] unittest does not discover tests in PEP420 packages

Change by Adam Johnson : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue45864] unittest does not discover tests in PEP420 packages

Adam Johnson added the comment: It's exactly that ticket. I missed that when searching for duplicates - I only searched for "pep420" and not "namespace packages". Mea culpa. -- resolution: -> duplicate ___ Python tracker

[issue45864] unittest does not discover tests in PEP420 packages

Karthikeyan Singaravelan added the comment: This seems to be similar to https://bugs.python.org/issue23882 -- nosy: +methane, xtreak ___ Python tracker ___

[issue45865] Old syntax in unittest

Change by Adam Johnson : -- keywords: +patch pull_requests: +27934 stage: -> patch review pull_request: https://github.com/python/cpython/pull/29698 ___ Python tracker ___

[issue45865] Old syntax in unittest

New submission from Adam Johnson : I often browse the unittest code in order to write extensions. It still uses some Python 2-isms like classes inheriting from object, it would be nice to clean that up. -- components: Tests messages: 406757 nosy: adamchainz priority: normal severity

[issue45864] unittest does not discover tests in PEP420 packages

isionError: division by zero ``` But unittest does not discover it: ``` $ python -m unittest -- Ran 0 tests in 0.000s OK ``` But, after creating an empty `__init__.py`, the tests doth fail: ``` $ touch tests/__init__.py $

[issue44556] ctypes unittest crashes with libffi 3.4.2

Ned Deily added the comment: Yes, this does appear to be a result of the problem described in Issue45350. As noted there, the problem was caused by running autoreconf to regerenerate the ./configure script in an environment where pkg-config wasn't installed which caused some pkg-config code

  1   2   3   4   5   6   7   8   9   10   >