mal> Here's an updated version which clarifies some issues...
...
mal> I propose to make the Unicode literal encodings (both standard
mal> and raw) a per-source file option which can be set using the
mal> "directive" statement proposed in PEP 244 in a slightly
mal> extended form (by adding the '=' between the directive name and
mal> it's value).
I think you need to motivate the need for a different syntax than is defined
in PEP 244. I didn't see any obvious reason why the '=' is required.
Also, how do you propose to address /F's objections, particularly that the
directive can't syntactically appear before the module's docstring (where it
makes sense that the module author would logically want to use a non-default
encoding)?
Skip
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4