[Docutils-develop] [docutils:bugs] Re: #451 Deprecate PEP 263 coding slugs support

[Günter M. <mi...@us...>]

> The underlying thrust of my argument is that this is very fragile --

True, this method only works with ASCII compatible encodings.
(This is one of the reasons why Docutils as well as PEP 263 complement it
with BOM mark recognition.)

...

> If the need arises [...], we would accept a feature request for
> `buildhtml.py` to have some enumeration of files and their input
> encodings.

IMO, it is more safe keep "source code encoding both visible and
changeable on a per-source file basis". [PEP 263]

Python3 still supports the encoding slug. 
I vote to keep this option as well.


---

** [bugs:#451] Deprecate PEP 263 coding slugs support**

**Status:** open
**Created:** Thu Jun 09, 2022 10:48 PM UTC by Adam  Turner
**Last Updated:** Sat Jun 11, 2022 01:13 AM UTC
**Owner:** nobody
**Attachments:**

- [0001-Deprecate-PEP-263-coding-slugs.patch](https://sourceforge.net/p/docutils/bugs/451/attachment/0001-Deprecate-PEP-263-coding-slugs.patch) (5.5 kB; application/octet-stream)


Python 3 uses utf-8 as the encoding for Python source files, there is no longer a compelling use-case for the support, which adds complexity to the IO implementation.

I propose deprecating support for removal in 1.0, but 2.0 might be a better option.

Support was added in [r4506].

A


---

Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/bugs/

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