[docutils:patches] #190 Move to native `unittest`

- **status**: open-accepted --> closed-accepted



---

** [patches:#190] Move to native `unittest`**

**Status:** closed-accepted
**Group:** None
**Created:** Thu Jan 20, 2022 01:10 AM UTC by Adam  Turner
**Last Updated:** Wed Nov 30, 2022 01:00 PM UTC
**Owner:** nobody


From FR81 https://sourceforge.net/p/docutils/feature-requests/81/#fc55/3d8d by Günter Milde

> I had a quick look and the work looks promising, so yes, I would like to
> give it a try.
> 
> What is the effect on the test time and on the output if there are, e.g.,
> differences between output and expected in functional tests?
> 
> To avoid wasted work (and the sunken-cost fallacy), I propose to split
> the project into smaller changesets (of 1 to ca. 7 commits) which we can
> discuss and adapt before pushing to origin/master and then move to the
> next step.
> I expect some rounds of discussion per step, so there is no
> need to invest heavily in polishing in the first round.
> A link to a patch that I can apply with git am -3 to a local branch
> would be fine.
> The discussion could move to docutils-develop or a new ticket,
> whatever you prefer.

This is the proposed tracking issue for moving to native unittest

A


---

Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/docutils/patches/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/patches/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.