[Docutils-develop] [docutils:patches] #189 Remove 'prest'

[Adam T. <aa-...@us...>]

> If it does not complicate this future separation, we may put "prest" to a rest now (maybe leaving prest/README).

I don't think it would, you'd just have one less repository.

> The plan here is, to split "prest" into a separate repository when moving to Git.

Ahh perfect, I didn't realise moving to Git had been agreed! Very happy to help out if you'd like.

If you wanted to keep 'prest' as you say it could just be split out into a different repository.

A



---

** [patches:#189] Remove 'prest'**

**Status:** open
**Group:** None
**Created:** Thu Jan 06, 2022 02:23 PM UTC by Adam  Turner
**Last Updated:** Thu Jan 06, 2022 02:23 PM UTC
**Owner:** nobody


xref sourceforge.net/p/docutils/mailman/message/36748625 -- an earlier attempt.

It has now been 11 years (08/12/2010), and no changes. The code will remain in the souce control history should anyone want to revive it.

The first commit removes all the files under /prest and the second removes a final reference in the docs.

This code was quite confusing to me when I was first looking throuh the Docutils source tree - I hestitated to contribute for a while as I thought I might need to know Perl or need to translate any contributions. 

As a current contributor, when searching through the full codebase, there are spurious results from prest that are annoying -- not insurmountable, but a common annoyance, and I think dropping this would solve both issues of clarity (Docutils is purely a Python project) and developer experience.

A

https://github.com/AA-Turner/docutils/pull/5 // https://github.com/AA-Turner/docutils/pull/5.patch


---

Sent from sourceforge.net because doc...@li... 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.