From: Adam T. <aa-...@us...> - 2022-01-15 21:57:40
|
> The current locale docs still say I went through the history, and it appears that snippet has remained almost unchanged for ~24 years ( https://github.com/python/cpython/blob/bc12f78bb3d774260444c76bc22507e9a5844bde/Doc/lib/liblocale.tex#L31-L36 ). `click`, which is perhaps the most popular CLI library outside of the stdlib has a guide on unicode considerations at https://click.palletsprojects.com/en/8.0.x/unicode-support/ They don't use `setlocale` anywhere in the code base, and instead if users have issues ask them to change the locale explicitly. Also of note is https://www.python.org/dev/peps/pep-0538/, which was implemented for Python 3.7. In short, I think it is a safe change to make. > default HTML writer I understand your argument, thanks for the explanation. I would probably vote for switching the default to `html5`, Sphinx uses it by default, so there would be no breaking change there. Another discussion, though. A --- ** [patches:#186] Modernise packaging** **Status:** open **Group:** None **Created:** Fri Dec 31, 2021 03:16 AM UTC by Adam Turner **Last Updated:** Sat Jan 15, 2022 08:47 PM UTC **Owner:** nobody **Attachments:** - [0001-Use-flit-and-pyproject.toml.patch](https://sourceforge.net/p/docutils/patches/186/attachment/0001-Use-flit-and-pyproject.toml.patch) (12.2 kB; application/octet-stream) - [0002-Use-entry-points.patch](https://sourceforge.net/p/docutils/patches/186/attachment/0002-Use-entry-points.patch) (20.7 kB; application/octet-stream) - [0003-update-docs-etc-after-packaging-changes.patch](https://sourceforge.net/p/docutils/patches/186/attachment/0003-update-docs-etc-after-packaging-changes.patch) (49.3 kB; application/octet-stream) Hi, I had a go at modernising the packaging stack. `setup.py` based invocations have been deprecated (https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html), and setuptools may remove them in the future. This takes the opportunity to move to a PEP 621 based declarative config, and also fixes a longstanding TODO item about providing script wappers for the frontend tools on windows, by migrating them to entry points. I've updated install and development docs with the new guidance, and updated references to the frontend tools to remove `.py`, given they are now installed as proper scripts. Hope this is appreciated -- happy to make revisions etc to help getting this merged. A --- 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. |