Stephen Finucane

On this point (2) what the concerns for doing a migration. For me, the main concern is a monopoly in the hand of a commercial corporation. While I am personally not a fan of GitHub and its pull request workflow (OpenStack uses their own Gerrit and Gitea instance), it's worth noting that the distributed nature of Git means lock in is not a huge issue as far as the code itself is concerned. As long as someone has an up-to-date clone of the repo, you could always move to a new home in no time. Of course...

On Wed, 2021-10-20 at 18:07 +0000, engelbert gruber via Docutils-develop wrote: hei sorry I must have missed Pradyun's question maybe it was on sphinx-doc ? https://github.com/live-clones/docutils/tree/master/docutils should be uptodate as far as I understand, github maintains this repo, doesnt it ? No, this is an independent mirror of the repo maintained by a third-party. It doesn't seem particularly wise to suggest contributors rely on a non- authoritative mirror, or to rely on a volunteer with...

On Tue, 2021-10-19 at 07:04 +0000, Juan Luis Cano Rodríguez wrote: Hi everyone, I have been reading this conversation mostly from the sidelines. I am a big proponent of using GitHub or any other equivalent service for the reasons I'll state below. However, before going any further, I would like to make an urgent call for civility. Pradyun initial message was very well framed and asked very specific questions in a positive tone, and I think that is the only way to carry this discussion forward. People...

I've resubmitted the setuptools conversion patch in case you want to apply it. I think previous discussions suggested this was okay to do unless anyone objected, and I haven't seen any objections yet.

The only thing I can see that's missing is the distutils -> setuptools conversion patch, but I guess that's a separate issue that can be handled as such.

I've done this and then some. Just sent a large, 39 patch series to the list. Please let me know if you receive it. I'm sure I can upload it a different way if necessary. Stephen On Wed, 2019-08-21 at 12:35 +0000, Günter Milde wrote: As some of the changes in the patch are already done in current master, it would be simpler if you rebase and re-create the patch. [patches:#150] Drop support for Python 2.6, Python 3.3 Status: open Group: None Created: Wed Jan 30, 2019 10:55 AM UTC by Stephen Finucane...

Add native Python 3 support

Can this patch land now?