9d9fae78f3
keyword fix
2003-04-01 17:41:34 +00:00
e564707d7a
added PEP 313, Adding Roman Numeral Literals to Python, by Mike Meyer
2003-04-01 17:38:03 +00:00
61029fe234
Add REQUIRES and PROVIDES sections
2003-03-30 16:52:11 +00:00
9c4d42499a
Use SHA1, not MD5
2003-03-30 15:01:31 +00:00
2fc84d184a
Bring PEP 262 back from the dead
2003-03-30 14:46:55 +00:00
4af20ba859
one more fix
2003-03-22 06:39:54 +00:00
4a0299b061
fixed lists
2003-03-22 06:38:51 +00:00
7c050568e2
Reference the itertools module
2003-03-21 19:57:09 +00:00
49afb661db
update from Peter Harris, plus spell-check & edit
2003-03-11 04:49:44 +00:00
9ddde8f432
Add advisory to replace apply().
2003-03-07 00:21:42 +00:00
bf79d7da5f
Add some hopeful PEPS.
2003-02-26 14:58:11 +00:00
5c0f2e9923
Fix grammar nit
2003-02-21 15:24:41 +00:00
1d9e85d7a2
Explain feature freeze.
...
Mention IDLE.
2003-02-19 19:36:27 +00:00
247c1e1073
Adjust schedule. Add some issues that might be resulved before 2.3b1.
2003-02-19 19:10:33 +00:00
10b912421d
Document __reduce_ex__.
2003-02-19 01:59:59 +00:00
d378d4b7c3
title change to PEP 309
2003-02-19 00:53:08 +00:00
2c9fa04926
update from Peter Harris, with editorial tweaks
2003-02-19 00:46:51 +00:00
ef58cb550d
updated
2003-02-14 15:37:24 +00:00
1791352db4
updated
2003-02-14 14:51:50 +00:00
512f402bb4
editorial tweaks
2003-02-14 14:51:27 +00:00
fc14790f4c
rejected by the author
2003-02-14 14:50:54 +00:00
2999ba93f7
"Simple Implicit Lambda", by Suzi & Martelli
2003-02-14 05:49:58 +00:00
a63e791682
New PEP 311: Simplified Global Interpreter Lock acquisition for extensions
2003-02-14 04:03:52 +00:00
71edeec4dc
posted again
2003-02-13 19:01:17 +00:00
6f28699bc4
Added info about the new HIGHEST_PROTOCOL module constant.
2003-02-13 16:08:06 +00:00
fa6660b886
Avoid 'I' now there's more than one author. Other minor nits.
2003-02-13 15:01:53 +00:00
a975337001
Amended the PEP to reflect some convergence on the newgroup:
...
* Listed the downsides of the current proposal.
* Listed why '<cond> then <expr1> else <expr2>' is starting to
be preferred over '<cond> and <expr1> or <expr2>'.
* After BDFL comments, I withdrew my proposed c??a||b syntax
and deleted the rejected c?a!b syntax. The remaining
punctuation based contender is c?a:b.
* After BDFL rejection of non-short-circuiting options,
advocacy dropped sharply. Removed it from the list of
contenders.
The leading options on the table are:
* (if <cond>: <expr1> else: <expr2>)
* <cond> then <expr1> else <expr2>
* <cond> ? <expr1> : <expr2>
* no change
2003-02-13 06:59:58 +00:00
5ef89e80a2
Put variables in correct order.
2003-02-12 12:35:59 +00:00
400ec56439
Chris Tismer's proposal is also being well received.
2003-02-12 04:09:14 +00:00
578b6df698
* Add Holger's new, well-received idea.
...
* Fixed typo.
2003-02-12 01:38:25 +00:00
85fb287b33
I just thought of something: now the syntax looks like if C:E1 else:E2,
...
we can also allow one or more elif parts.
2003-02-11 22:34:52 +00:00
1d3b81205e
Implemented list batching in cPickle.
2003-02-11 21:23:59 +00:00
b3de48b5bb
Several people requested that the parenthesis requirement be emphasized.
2003-02-11 19:48:20 +00:00
ef2c13772f
Typo (foo -> good).
2003-02-11 15:53:20 +00:00
a192075d59
Minor nits.
2003-02-11 14:59:18 +00:00
37e79f5901
Added note about new datetime module in Python 2.3.
2003-02-11 13:19:51 +00:00
ce2804d8fc
Add name of updater.
2003-02-11 06:32:52 +00:00
294fd7ade7
Updated the PEP for GvR.
...
* Out of order evaluation is out of favor.
* So are ideas that do not provide for short-circuiting.
* (if <condition>: <expression1> else: <condition2>) is in vogue.
* <condition> ?? <expression1> || <expression2> is a new contender.
* cond(<condition>, <expression1>, <condition2>) is viable if implemented
as a keyword and has short-circuit behavior.
* Added a summary of a few ideas from the last couple hundred posts
from comp.lang.python.
2003-02-11 05:43:56 +00:00
1264fe2202
Cleared up the XXX comments I added earlier today, and fixed some
...
additional typos.
2003-02-11 04:50:59 +00:00
5b6409adaf
+ Add XXX comments. I'll clean those up later (or Guido and I both will).
...
+ Minor typo repair.
+ Added very brief sections about the other stuff that's new in protocol 2.
2003-02-10 23:21:03 +00:00
586a9c30cc
Clarified the distinction between pickling time and unpickling time
...
where that seemed to help, and made explicit where "the object" came
from originally in the descriptions of the optional __reduce__ tuple
elements.
2003-02-10 22:13:34 +00:00
ae56c6a44c
Bozo __getstate__ is gone.
2003-02-10 21:44:25 +00:00
1857c40946
Mostly paragraph relowing, after typographical fiddling to make it
...
screamingly obvious which state tuple elements are required, which
obvious, and which new in this PEP.
2003-02-10 21:39:25 +00:00
e5c7b99c0b
Clarify __reduce__ and classic classes more.
2003-02-10 21:34:28 +00:00
50955157ae
Tried to clarify the point about classic classes and __reduce__.
2003-02-10 21:25:25 +00:00
0429311d5a
update title, same as in PEP 0
2003-02-10 15:34:54 +00:00
eb0e9894fb
updated
2003-02-10 14:54:10 +00:00
a7cd5f569e
Reliable Acquisition/Release Pairs, by Michael Hudson and Paul Moore
2003-02-10 14:52:51 +00:00
d49ecf85a2
Built-in Closure Type, by Peter Harris
2003-02-10 14:51:45 +00:00
67273248cc
a number of changes to keep more-or-less up-to-date.
2003-02-10 04:03:49 +00:00
David Goodger
Andrew M. Kuchling
Raymond Hettinger
Guido van Rossum
Mark Hammond
Skip Montanaro
Tim Peters
Marc-André Lemburg