Commit Graph

15 Commits

Author SHA1 Message Date
Jelle Zijlstra 8bd3c28aa0
PEP 675: Mark as accepted (#2452) 2022-03-21 14:36:53 -07:00
CAM Gerlach 185aedc4ce
PEP 675: Add link to official discussion thread (#2333) 2022-02-21 23:49:13 +00:00
Pradeep Kumar f7bba0160b
PEP 675: use semicolon instead of comma (#2330) 2022-02-15 19:20:15 -08:00
Pradeep Kumar 49ec965e65
PEP 675: fix wording in a couple of places (#2326)
+ Add newlines to make code samples easier to read.
+ s/argument/parameter/.
2022-02-15 17:08:01 -08:00
Pradeep Kumar b57ebdbd81
PEP 675: add "Type" to title and add post history (#2325)
Also adjust the wording of the first line of the Abstract. I changed
"static type annotations" to "type annotations" since the "static" part
is redundant.
2022-02-15 12:40:49 -08:00
Petr Viktorin ba2a9295dd
PEP 675; Establish typing context in the Abstract (#2324) 2022-02-15 01:14:45 +00:00
Pradeep Kumar 389e8bd43e
PEP 675: nest sections under Specification (#2313)
They were top-level sections.

I also moved up the Runtime Behavior section to answer the question of
where LiteralString lives, since right now it's buried in the PEP.
2022-02-07 17:14:26 -08:00
Pradeep Kumar 6b5bfdb1c4
PEP 675: remove unnecessary reference to Self type PEP (#2297) 2022-02-02 13:43:20 -08:00
Graham Bleaney 74272d5238
Minor formatting and wording fixes (#2293) 2022-02-02 12:49:27 +00:00
Pradeep Kumar 51c6246c7e
PEP 675: Switch to the name `LiteralString` (#2292)
* Switch to the name LiteralString
* Reject ``LiteralBytes``
* Address nits
* Set off "such as" phrases with commas
2022-02-01 13:00:27 -06:00
Pradeep Kumar 6f11197188
PEP 675: Updates (#2282) 2022-01-31 19:20:47 -08:00
CAM Gerlach e43f567e93
Upgrade lint infra & add a few more conservative built-in checks (#2286) 2022-01-31 18:49:58 -08:00
Pradeep Kumar 9f8179aaa2
PEP 675: Clarify wording in various sections (#2279)
* PEP 675: gentler intro for the Motivation section.

* PEP 675: explain usage stats.

* PEP 675: remove duplicate Backwards Compatibility heading.

There was already a Backwards Compatibility heading for Type Inference.
So, I just inlined the second one into the Runtime Behavior section.

* PEP 675: link to Other Uses in the Motivation.

* PEP 675: clarify that we insert a new type in the hierarchy.

* PEP 675: Make Backwards Compatibility a top-level section.

We had two "sections" - one for the type inference and one for the
runtime behavior. Move them both into one top-level section.

* PEP 675: Change case of Runtime Behavior.

* PEP 675: Fix and widen hyperlink text.
2022-01-26 16:57:26 -08:00
Adam Turner 113e490701
Several PEPs: Use explicit `:pep:` and `:rfc:` roles (#2209) 2022-01-21 11:03:51 +00:00
Pradeep Kumar 21f6993114
PEP 675: Arbitrary literal strings (#2167) 2021-12-01 09:57:41 -08:00