summaryrefslogtreecommitdiffstats
path: root/Misc/NEWS
Commit message (Collapse)AuthorAgeFilesLines
* Make 'x in y' and 'x not in y' (PySequence_Contains) play nice w/ iterators.Tim Peters2001-05-051-2/+2
| | | | | | | | | | | | | NEEDS DOC CHANGES A few more AttributeErrors turned into TypeErrors, but in test_contains this time. The full story for instance objects is pretty much unexplainable, because instance_contains() tries its own flavor of iteration-based containment testing first, and PySequence_Contains doesn't get a chance at it unless instance_contains() blows up. A consequence is that some_complex_number in some_instance dies with a TypeError unless some_instance.__class__ defines __iter__ but does not define __getitem__.
* Make unicode.join() work nice with iterators. This also required a changeTim Peters2001-05-051-1/+1
| | | | | | | | to string.join(), so that when the latter figures out in midstream that it really needs unicode.join() instead, unicode.join() can actually get all the sequence elements (i.e., there's no guarantee that the sequence passed to string.join() can be iterated over *again* by unicode.join(), so string.join() must not pass on the original sequence object anymore).
* Mark string.join() as done. Turns out string_join() works "for free" now,Tim Peters2001-05-051-1/+2
| | | | | | because PySequence_Fast() started working for free as soon as PySequence_Tuple() learned how to work with iterators. For some reason unicode.join() still doesn't work, though.
* Generalize tuple() to work nicely with iterators.Tim Peters2001-05-051-2/+2
| | | | | | | | | | | | | | | | | | | | | NEEDS DOC CHANGES. This one surprised me! While I expected tuple() to be a no-brainer, turns out it's actually dripping with consequences: 1. It will *allow* the popular PySequence_Fast() to work with any iterable object (code for that not yet checked in, but should be trivial). 2. It caused two std tests to fail. This because some places used PyTuple_Sequence() (the C spelling of tuple()) as an indirect way to test whether something *is* a sequence. But tuple() code only looked for the existence of sq->item to determine that, and e.g. an instance passed that test whether or not it supported the other operations tuple() needed (e.g., __len__). So some things the tests *expected* to fail with an AttributeError now fail with a TypeError instead. This looks like an improvement to me; e.g., test_coercion used to produce 559 TypeErrors and 2 AttributeErrors, and now they're all TypeErrors. The error details are more informative too, because the places calling this were *looking* for TypeErrors in order to replace the generic tuple() "not a sequence" msg with their own more specific text, and AttributeErrors snuck by that.
* Add TODO item about x in y -- this should use iterators too, IMO.Guido van Rossum2001-05-041-0/+1
|
* Added reminders to make some remaining functions iterator-friendly. FeelTim Peters2001-05-041-1/+3
| | | | free to do one!
* Generalize reduce() to work with iterators.Tim Peters2001-05-041-0/+1
| | | | NEEDS DOC CHANGES.
* Generalize map() to work with iterators.Tim Peters2001-05-031-0/+1
| | | | | | | | | | | NEEDS DOC CHANGES. Possibly contentious: The first time s.next() yields StopIteration (for a given map argument s) is the last time map() *tries* s.next(). That is, if other sequence args are longer, s will never again contribute anything but None values to the result, even if trying s.next() again could yield another result. This is the same behavior map() used to have wrt IndexError, so it's the only way to be wholly backward-compatible. I'm not a fan of letting StopIteration mean "try again later" anyway.
* Generalize max(seq) and min(seq) to work with iterators.Tim Peters2001-05-031-0/+2
| | | | NEEDS DOC CHANGES.
* Generalize filter(f, seq) to work with iterators. This also generalizesTim Peters2001-05-021-8/+9
| | | | | filter() to no longer insist that len(seq) be defined. NEEDS DOC CHANGES.
* Add more news about iterators.Guido van Rossum2001-05-011-0/+12
|
* Generalize list(seq) to work with iterators. This also generalizes list()Tim Peters2001-05-011-0/+10
| | | | | | | | | | | | | to no longer insist that len(seq) be defined. NEEDS DOC CHANGES. This is meant to be a model for how other functions of this ilk (max, filter, etc) can be generalized similarly. Feel encouraged to grab your favorite and convert it! Note some cute consequences: list(file) == file.readlines() == list(file.xreadlines()) list(dict) == dict.keys() list(dict.iteritems()) = dict.items() list(xrange(i, j, k)) == range(i, j, k)
* Noted what's new in 2.1 (final).Guido van Rossum2001-04-161-0/+21
| | | | Hopefully this is the last checkin for 2.1!
* Added news for 2.1c2.Guido van Rossum2001-04-161-11/+192
| | | | Greatly updated news for 2.1c1 (!).
* Note additions to pydoc and pstats.Guido van Rossum2001-04-131-0/+5
|
* Note that __debug__ assignments are legal again.Guido van Rossum2001-04-121-0/+3
|
* Noted the improved RISCOS port and the new Unixware 7 port.Guido van Rossum2001-04-111-0/+4
|
* Added news about the updated python-mode.elBarry Warsaw2001-04-111-0/+10
|
* Remove the backed-out version requirementAndrew M. Kuchling2001-03-311-2/+1
|
* News items for my recent checkinsJeremy Hylton2001-03-231-0/+16
|
* A small change to the C API for weakly-referencable types: Such typesFred Drake2001-03-221-0/+6
| | | | | | | | must now initialize the extra field used by the weak-ref machinery to NULL themselves, to avoid having to require PyObject_INIT() to check if the type supports weak references and do it there. This causes less work to be done for all objects (the type object does not need to be consulted to check for the Py_TPFLAGS_HAVE_WEAKREFS bit).
* Added news items for the DistutilsAndrew M. Kuchling2001-03-221-0/+21
|
* Add some news for 2.1b2. I'd still like someone else to add newsGuido van Rossum2001-03-221-3/+55
| | | | | | | | about these packages: - distutils - xml
* Add section on 2.1b2.Martin v. Löwis2001-03-211-0/+11
| | | | Report the addition of the Tix module.
* Add some more info about pydoc. (Can you see I'm excited?)Guido van Rossum2001-03-021-1/+6
|
* Add big news item about nested scopes, __future__, and compile-timeGuido van Rossum2001-03-021-0/+36
| | | | warnings.
* ROSCOS change.Guido van Rossum2001-03-021-0/+8
|
* Thank Jason Tishler and Steven Majewski for their help in the Cygwin andTim Peters2001-03-011-2/+10
| | | | MacOS X ports. Change section header to beta 1.
* Added blurbs about difflib, doctest and Windows import (PEP 235).Tim Peters2001-03-011-4/+29
|
* Mention pydocAndrew M. Kuchling2001-02-281-0/+7
|
* Add Vladimir Marangozov's object allocator. It is disabled by default. ThisNeil Schemenauer2001-02-271-0/+9
| | | | closes SF patch #401229.
* Document XML changes.Martin v. Löwis2001-02-271-0/+42
|
* Mention the removal of soundex.cAndrew M. Kuchling2001-02-221-0/+2
|
* Take a tour of hell's seedier neighborhoods to try to make winsound.Beep()Tim Peters2001-02-191-0/+7
| | | | | do something non-useless on Win9X boxes. WinME unknown to me. Someone with NT/2000 make sure it still works there!
* Fixed misspelling.Tim Peters2001-02-181-1/+1
|
* Bug #132921: None treated differently in cmp() / sort() in 2.1a2.Tim Peters2001-02-181-0/+7
| | | | Just mentioning that in the NEWS file.
* Fix binfmt_register documentation to always register the right magic.Martin v. Löwis2001-02-041-1/+4
|
* Renamed _testXXX to _testcapiXXX. Jack is my hero -- good call!Tim Peters2001-02-041-0/+11
|
* Clarify the news item about "from M import X" if "M is not a realGuido van Rossum2001-02-031-3/+3
| | | | module" after a complaint from Tim.
* Teach Windows build and installer about new _symtable module/DLL.Tim Peters2001-02-021-1/+4
|
* Fix spelling errors.Jeremy Hylton2001-02-021-7/+12
| | | | | | Add note about _symtable. Add note that 'from ... import *' restriction may go away -- and move the whole entry closer to the top, because it might bite people.
* Patch derived from Trent's 101162: a Python/C API testing framework.Tim Peters2001-02-021-2/+11
| | | | STILL NEEDS UNIX BUILD CHANGES.
* add info about Grant Edwards' raw packet supportJeremy Hylton2001-02-021-0/+3
|
* continue now allowed in try blockJeremy Hylton2001-02-011-0/+4
|
* Add item about nested scopes.Jeremy Hylton2001-02-011-6/+39
| | | | | Revise item about restriction on 'from ... import *'. It was in the wrong section and the section restriction was removed.
* Added comments about the weak reference support.Fred Drake2001-02-011-0/+6
|
* Change random.seed() so that it can get at the full range of possibleTim Peters2001-02-011-0/+10
| | | | | | | | internal states. Put the old .seed() (which could only get at about the square root of the # of possibilities) under the new name .whseed(), for bit-level compatibility with older versions. This occurred to me while reviewing effbot's book (he found himself stumbling over .seed() more than once there ...).
* Document the two changes to the mailbox.py module:Barry Warsaw2001-01-311-0/+7
| | | | | | | | | | | | - All constructors grow an optional argument `factory' which is a callable used when new message instances are created by the next() methods. Defaults to the rfc822.Message class. - A new subclass of UnixMailbox is added, called PortableUnixMailbox. It's identical to UnixMailbox, but uses a more portable test for From_ delimiter lines. With PortableUnixMailbox, any line that starts with "From " is considered a delimiter (this should really check for two newlines before the F, but it doesn't.
* Docs for new Windows zlib build procedure.Tim Peters2001-01-311-1/+6
|
* add note about two kinds of illegal imports that are now checkedJeremy Hylton2001-01-301-0/+6
|
generated by cgit v0.12 at 2025-02-23 02:33:35 (GMT)