Pradyun Gedam
0771dd31cc
Mark PEP 518 as Final ( #1358 )
2020-04-06 08:24:22 +10:00
Brett Cannon
1542941b34
PEP 518: Clarify how tools should treat the absence of things
2019-12-13 15:27:42 -08:00
Weiliang Li
4b5c173663
Update pep-0518.txt ( #1150 )
...
.e.g => e.g.
2019-08-23 17:22:30 +10:00
Min ho Kim
cfb7bd74db
Fix typos ( #1113 )
2019-07-03 11:20:45 -07:00
Ethan Smith
b5a4f071d5
PEP 518: Clarify any tool can use the tool table ( #1054 )
...
Context: https://discuss.python.org/t/pep-518-clarify-scope-of-tool-section/1682
2019-05-15 23:33:02 -07:00
Brett Cannon
af73627e58
Specify that the build-system table is optional
...
The 'requires' key in the build-system table is still required if the table is specified, though.
2018-07-20 17:00:13 -07:00
Nick Coghlan
307dda38d4
PEP 1: Add a separate "Provisional" PEP status ( #577 )
...
This adds an explicit "Provisional" status for PEPs, making
it easier to track which PEPs are truly Final, and which
are pending further further public feedback based on
their initially published reference implementations.
2018-07-08 11:50:57 +10:00
Pradyun Gedam
5c7c89ca54
PEP 518: Reword paragraphs describing defined tables ( #682 )
2018-06-22 15:05:43 -07:00
Pradyun Gedam
d2b5d8087a
PEP 518: Add subsections to Specification section ( #677 )
...
It is common to reference to different parts of the specification when
discussing the changes brought about by this PEP. This change makes it
easier to do so by introducing subsections to the main specification.
2018-06-20 21:01:17 +10:00
Nick Coghlan
dfd9cf15aa
PEP 518: Cite @njsmith's config file format review ( #668 )
...
* PEP 518: Cite @njsmith's config file format review
* Add a file format feature summary table
2018-06-06 00:04:09 +10:00
Brett Cannon
fb657c73da
Fix a spelling mistake
2018-06-04 11:49:43 -07:00
Brett Cannon
da09c9243a
Explain why we didn't use setup.cfg ( #667 )
2018-06-01 17:29:36 -07:00
5j9
a790b3821c
PEP 517: Fix typo in the word "community" (GH-532)
2018-01-06 10:23:14 -08:00
Mariatta
cf3bad5ab3
Revert "Rename all .txt PEP files to .rst (GH-462)" (GH-464)
...
This reverts commit bb0e518ed3
.
2017-11-11 11:28:55 -08:00
Huang Huang
bb0e518ed3
Rename all .txt PEP files to .rst (GH-462)
...
For https://github.com/python/peps/issues/1
2017-11-11 10:30:43 -08:00
Serhiy Storchaka
07c157552d
Replace tabs with spaces and fix identation errors. ( #230 )
2017-03-24 00:57:19 +02:00
Brett Cannon
9cc8974581
Make PEP 518 an informational PEP ( #94 )
...
* Move to LF line endings
* Mark PEP 518 as informational
2016-09-05 15:04:04 -07:00
Marti Raudsepp
04a6af2ab1
Fix various typos, spelling and grammar errors
...
Errors detected using Topy (https://github.com/intgr/topy ), all changes
verified by hand.
2016-07-11 18:35:35 +03:00
Nick Coghlan
ca65ae89e6
PEP 518: Add resolution link
2016-05-17 12:55:23 +10:00
Brett Cannon
c856ebcc9e
Accept PEP 518: https://mail.python.org/pipermail/distutils-sig/2016-May/028969.html
2016-05-16 07:37:38 -07:00
Brett Cannon
0b0a0a5451
Add PEP 518: Specifying minimum build requirements for Python projects
2016-05-16 07:35:09 -07:00