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

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

> 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 see still a reason to keep (and properly document) a way to specify the
encoding of an rST source in the document itself.

Use cases: 

* A collection of files, where one file for whatever reason must be in a
  different encoding. Compilation with "buildhtml.py".
  
* Documents in an 8-bit or 16-bit encoding intended for compilation 
  anywhere. Avoids shipping a separate configuration file.
  
The "coding slug" might become obsoleted by a more generic "in-document configuration" 
(cf. TODO item [misc.settings directive](https://docutils.sourceforge.io/docs/dev/todo.html#misc-settings)
but this is still a long way off.
  


---

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

**Status:** open
**Created:** Thu Jun 09, 2022 10:48 PM UTC by Adam  Turner
**Last Updated:** Thu Jun 09, 2022 10:48 PM 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.