Commit Graph

8286 Commits

Author SHA1 Message Date
Guido van Rossum 841188a45f PEP 614: Accepted by SC 2020-03-03 14:20:05 -08:00
Brett Cannon 172c06e0f1
Clarify that the CDATA for a repo index should match the project name, not the normalized name (#1324) 2020-03-03 10:19:37 -08:00
Brett Cannon ea2d7a97ee
Fix the year when the last council election occurred 2020-03-02 14:53:23 -08:00
Paul Ganssle 37a7083660
PEP 615: Changes to TZPATH and str, plus minor tweaks (#1323)
* Change fallback behavior for __str__

Per Petr's suggestion in the discourse thread. Turns out this was
basically what the reference implementation does anyway.

* Rename `set_tzpath` to `reset_tzpath`

* Adjust TZPATH strategy

Partially in response to Petr's comment on the discourse thread, and
partially from further reflection.

* Fix typo in RFC 8536 reference

* Add path traversal to security implications.

Seems like a minor concern, but possibly worth noting.
2020-03-01 09:23:37 -05:00
Brett Cannon 6b5dd00bf1
Update PEP 13 for the latest steering council (#1322) 2020-02-28 14:15:03 -08:00
Paul Ganssle 632742d2d7
PEP 615: Windows support, address first round of feedback (#1320)
* Address some of Petr's feedback

https://discuss.python.org/t/pep-615-support-for-the-iana-time-zone-database-in-the-standard-library/3468/3

* Update with description of update behavior

This is in response to Paul Eggert's insightful comments:

https://mm.icann.org/pipermail/tz/2020-February/028843.html

* Add note on leap seconds

Leap seconds are out of scope for the proposal, but several people have
asked about them, so it seems prudent to note this.

* Move Windows support to Open Issues

Based on comments sent privately by e-mail from Matt Johnson-Pint, who
suggested this approach.

* Make cache behavior explicit

Per Guido's comments, this was not previously explicit:

https://discuss.python.org/t/pep-615-support-for-the-iana-time-zone-database-in-the-standard-library/3468/10?u=pganssle

* Address Jelle's comment about type

* Update the pickle behavior to serialize by key

Per the discussion here (and the chain of posts that this replies to):
https://discuss.python.org/t/3468/17
2020-02-27 15:16:57 -05:00
Ned Deily e709487ed6 accelerate 3.7.7 schedule to fix regressions 2020-02-26 15:29:38 -05:00
Łukasz Langa 4be860c1ca
[pep-569][pep-596] Actual dates for 3.8.2 and 3.9.0a4; shuffle some other dates 2020-02-26 02:21:15 +01:00
Guido van Rossum 4ecaa6c00a
PEP 585: Explain the choice of GenericAlias over GenericType (#1319)
Per Nick's explanation on python-dev.
2020-02-26 00:54:57 +01:00
Paul Ganssle b674d3ae26
PEP 615: Add PEP proposing zoneinfo module (#1316)
* Add IANA Time Zone Support PEP

* Add section rejecting Windows native time zones

* Normalize code-block and drop python3

Apparently this is rendered without pygments support, which is causing
the build to fail.

* Add justification for a separate module

* Clean up and reorganize footnotes and citations

This adds headlines / citations for each footnote, rather than bare
links, and tries to put them in a more logical grouping, and makes
them all render without issues.

* Add / adjust proposal targets

* Add justification for set_tzpath

Basically, "people are going to do this anyway, might as well have them
use a function that we can at least deprecate if it causes major
problems."

* Add citation for rearguard format

* Fix typos and formatting in abstract

Fixes a few typos and reformats the abstract using semantic newlines.

* Update location of reference implementation

* Tweaks to motivation section

* Clarify wording about PEP organization

* Tweaks to section on the ZoneInfo class

This adjusts the wording and fixes typos in the constructors and pickle
sections.

* Tweaks 'Sources for time zone data'

These are typos, clarifications and wording adjustments in the section
on time zone data sources.

* Use semantic newlines in 'Security implications'

* Clarify what 'no special verification' means

* Add clarification to custom compiler section

* Tweaks to wording on 'tzdata' in the standard library

* Tweaks to Windows section

* Adjust the justification for rejecting pytz

* Add quotation marks around blog titles

* Abandon semantic newlines

* Rename title

* Move module name into 'Open issues'

* Comment out temporarily unused headers

* Add open issue about TZPATH structure

* Remove erroneous blockquotes

* Add discourse link and Post-History
2020-02-25 10:56:05 -05:00
Guido van Rossum 2e5c584c6b
PEP 594: Mention removing uu_codec (#1244) 2020-02-24 20:33:49 -08:00
Guido van Rossum 67642567c6 PEP 484: Fix other occurrences of 'parametriz' 2020-02-24 20:21:41 -08:00
Guido van Rossum 8a5fe7b15c PEP 585: Fix other occurrences of 'parametriz' 2020-02-24 20:21:22 -08:00
Guido van Rossum cfbbb26936 PEP 482: Fix other occurrences of 'parametriz' 2020-02-24 20:20:33 -08:00
Ethan Smith 73b35bb7ff
PEP 483, 484, 585: Use parameterized instead of parametrized (#1318)
Google prefers "parameterize" and PEP 484 uses it in a majority of cases. So does the stdlib. So PEP 585 has to follow.
2020-02-24 20:18:17 -08:00
Brandt Bucher 96d6d4beaa
PEP 584: Mark as Accepted (#1317) 2020-02-24 17:43:06 -08:00
Éric Araujo 4d29a24fa6
clarify status of implmentation notes in PEP 376 (#1307) 2020-02-24 13:23:09 +00:00
Barry Warsaw 3609ef5483
Add the original Zen (Way) of Python link (#1313) 2020-02-20 15:50:16 -08:00
Nick Coghlan af0691db4b
PEP 458: Use 'signed repository metadata' terminology (#1308)
James Bennett pointed out that "package signing" is widely misunderstood
as referring specifically to end-to-end signing with individual
publisher keys, rather than to metdata signing in general.

This updates the title and abstract to instead use the term "signed
repository metadata", and also updates a few other sections that
still gave the impression that implementing PEP 458 would be
enough to give the full end-to-end signing support that is actually
covered in PEP 480.
2020-02-21 08:31:29 +10:00
Łukasz Langa 5d778373ea
[pep-585] Disallow isinstance([1, 2], list[str]) (#1311) 2020-02-19 12:17:19 +01:00
Christopher Hunt 229df87c1f
PEP 581: Fix switched reference links (#1312) 2020-02-18 20:06:01 -08:00
Hugo van Kemenade 763ba2acc4
[pep-596] Update note now that PEP 602 is accepted (#1310) 2020-02-18 22:11:50 +01:00
Łukasz Langa 4ac42462f5
[pep-596] Postpone 3.9.0a4 2020-02-18 01:17:24 +01:00
Łukasz Langa 87c71713f2
[pep-569] Actual date of 3.8.2rc1 and 3.8.2rc2 2020-02-18 01:01:11 +01:00
Brandt Bucher 718b393887
PEP 584: Apply feedback from the Python-Dev discussion. (#1309) 2020-02-17 12:07:40 -08:00
Nick Coghlan 37889fb456
PEP 558: Update proposed C API (#1302)
Also removes the exec() and eval() caveats on the reference implementation
(those have been migrated now, albeit not using a code structure that we
would genuinely want to merge).
2020-02-16 22:10:19 +10:00
Sumana Harihareswara a409487450
PEP 373: Use past tense since sunset date has passed (#1304) 2020-02-15 21:17:13 +10:00
Nick Coghlan 4751318c7e
PEP 458: Mark as Accepted (#1306) 2020-02-15 19:22:42 +10:00
Brandt Bucher b34adc092e
PEP 614: Remove matmul section and clarify the current restrictions (#1305) 2020-02-13 11:55:28 -08:00
Brandt Bucher 85c431c827
PEP 614: Relaxing Grammar Restrictions On Decorators (#1303) 2020-02-10 22:47:06 -08:00
Guido van Rossum 0fcb222a7c
PEP 612: Guido as sponsor, and two minor edits (#1301) 2020-02-06 21:18:37 -08:00
Guido van Rossum 7f402aef96
PEP 585: updates green-lighted by Lukasz (#1289)
* Rename __parameters__ to __args__, for typing.py compatibility
* Genericize, re.{Pattern,Match} and io.IO
* list != list[int], but list[int] == list[int] (and list[str] != list[int])
* Add a lazy __parameters__ that contains the unique type vars in __args__ (also for typing.py compatibility)
* make dict[str][str] fail, but dict[T, str][int] return dict[int, str]
* expose proxy type as types.GenericAlias
* Link to implementation
* Explicitly state that pickling or copying should work
2020-02-06 17:37:46 +01:00
Brandt Bucher d52d55964a
Post-publishing cleanup for PEP 584 (#1298) 2020-02-05 11:14:58 -08:00
Brandt Bucher f4a6bfaa98
PEP 584: Next Draft (#1290)
Change from '+' to '|', and a lot of editing.
2020-02-04 15:21:25 -08:00
Petr Viktorin f52d345112
Pep 376: Use ReST syntax for code, rather than Markdown syntax (#1297)
* PEP 376: Use ReST code syntax for literal characters

Without markup, it is very easy to confuse code with adjoining
punctuation.

* PEP 376: Use ReST syntax for code, rather than Markdown syntax
2020-02-05 05:02:40 +11:00
Trishank Karthik Kuppusamy 5a9de97e0d
PEP 458: update list of authors (#1295)
* update authors

* update email address & acknowledgements
2020-02-05 04:57:22 +11:00
Inada Naoki 57ca4dc015
PEP 597: Rewrite (#1296) 2020-02-04 20:35:06 +11:00
Georg Brandl 89b0b69863
Fix example description (#1293)
With two elements, the starred middle expression just is an empty list.
2020-02-03 20:50:41 +11:00
Stéphane Bidoul 56268fbbeb
PEP 610: support well-known users in URLs (#1292)
* PEP 610: a well-known user may be used in URL

* PEP 610: correct errors wrt resolved_revision(_type)
2020-02-02 01:17:06 +11:00
Shannon Zhu 5cd06a20bf
Update PEP 0613 status to Accepted (#1291) 2020-01-31 15:38:40 -08:00
Jason Fried 565b6778dc
Fixed bad TypeVar definition (#1288)
Identifier must match TypeVar name
2020-01-29 15:21:31 -08:00
mnm678 202ab85bde
PEP 458: Consistency & clarification edit (#1284)
* Made various edits and clarifications to the pep including:

* letting the PSF appoint offline key holders
* moving content from abstract to motivation to make the abstract more succinct
* updating the threat model
* resolving some minor inconsistencies
* add link to cncf blog post
2020-01-30 08:08:21 +10:00
dkg 17710b8798
PEP 458: use "OpenPGP" instead of "GPG" (#1287)
* PEP 458: use "OpenPGP" instead of "GPG".  The signature format is OpenPGP.  Other
OpenPGP implementations exist aside from gpg, the OpenPGP tool from the GnuPG project.
2020-01-30 06:02:31 +11:00
Mark Shannon a65ee4d2ad
PEP 611: relax hard limits and make 1 million a soft limit. Include recursion depth in limits. (GH-1279)
* PEP 611: relax hard limits and make 1 million a soft limit. Include recursion depth in limits.

* Reorganize part of motivation to account for soft vs. hard limits. Add qualification about recursion depth.
2020-01-29 11:31:28 +00:00
Shannon Zhu 2aea60e07c PEP 613: remove last open issue; some edits in response to feedback (#1285) 2020-01-28 12:58:47 -08:00
Stéphane Bidoul bf9d3a51cc PEP 610: add canonical URL and minor clarification (#1283) 2020-01-26 23:29:59 +10:00
mnm678 d6fa383389 PEP 458: Allow compression of json metadata (#1281)
* Allow compression of json metadata

* Update pep-0458.txt

Co-Authored-By: Trishank Karthik Kuppusamy <33133073+trishankatdatadog@users.noreply.github.com>

Co-authored-by: Trishank Karthik Kuppusamy <33133073+trishankatdatadog@users.noreply.github.com>
2020-01-26 09:39:36 +10:00
Stéphane Bidoul 2ff0cc2ad2 PEP 610: specification will live on packaging.python.org (#1282)
Also add note about reproducibility

As suggested by Nick Coghlan at https://discuss.python.org/t/draft-pep-recording-the-origin-of-distributions-installed-from-direct-url-references/1535/41?u=sbidoul

* PEP 610: amending must be done by writing a new PEP

As suggested by NIck Coghlan
2020-01-26 09:38:13 +10:00
Łukasz Langa 7ecaee9478
[pep-596] Put actual date of 3.9.0a3 2020-01-25 14:55:14 +01:00
Łukasz Langa 31dca33dbf
[pep-101] Use @pablogsal's new Release Dashboard 2020-01-24 22:44:39 +01:00