Mailman 3 November 2003 - Python-Dev

RE: list.sort, was Re: [Python-Dev] decorate-sort-undecorate
by Raymond Hettinger Nov. 15, 2003

Nov. 15, 2003

[Armin Rigo] > from heapq import * > def isorted(iterable): > heap = list(iterable) > heapify(heap) > while heap: > yield heappop(heap) > > This generator is similar to the new list.sorted() but starts yielding > elements after only O(n) operations (in heapify). Certainly not a > candidate > for itertools, but it could be added to heapqmodule.c. There are numerous > cases where this kind of lazy-sorting is interesting, if done … [View More]

2 3

Re: set() and frozenset()
by Magnus Lie Hetland Nov. 15, 2003

Nov. 15, 2003

Great to see that these two will be in place soon! -- Magnus Lie Hetland "In this house we obey the laws of http://hetland.org thermodynamics!" Homer Simpson

1 0

Re: [Python-checkins] python/dist/src/Modules heapqmodule.c, 1.1, 1.2
by Guido van Rossum Nov. 15, 2003

Nov. 15, 2003

> + if (!PyList_Check(heap)) { > + PyErr_SetString(PyExc_ValueError, "heap argument must be a list"); > + return NULL; > + } > + As Tim suggested, this should be a TypeError. --Guido van Rossum (home page: http://www.python.org/~guido/)

3 3

Version number in the release-maint23 branch
by Thomas Heller Nov. 15, 2003

Nov. 15, 2003

I'd like to change the version number in the CVS release-maint23 branch to be able to do correct version checks. Currently it is this: /* Version parsed out into numeric values */ #define PY_MAJOR_VERSION 2 #define PY_MINOR_VERSION 3 #define PY_MICRO_VERSION 2 #define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_FINAL #define PY_RELEASE_SERIAL 0 /* Version as a string */ #define PY_VERSION "2.3.2+" Is it ok to change it to the following: /* Version parsed out into numeric values */ #define … [View More]

5 4

Small bug -- direct check-in allowed?
by Armin Rigo Nov. 15, 2003

Nov. 15, 2003

Hello, Just asking because I'm not sure about this rule: is it ok if I just make a check-in without first posting a SF bug or patch report for small bugs with an obvious solution ? In this case: >>> import heapq >>> heapq.heappop(5) Segmentation fault Armin

4 3

RE: list.sort, was Re: [Python-Dev] decorate-sort-undecorate
by Raymond Hettinger Nov. 15, 2003

Nov. 15, 2003

> Getting the 25 smallest elements: > > min_and_remove_repeatedly(lst, 25) 7.4 > list(itertools.islice(heapsort(lst), 25)) 1.05 > list(itertools.islice(isorted(lst), 25)) 1.03 > list.sorted(lst)[:25] 6.65 > > Getting all elements: > > list(heapsort(lst)) 22.49 > list(isorted(lst)) 26.06 > list.sorted(lst) 6.65 … [View More]

1 0

RE: [Python-checkins] python/dist/src/Modules heapqmodule.c, 1.1, 1.2
by Tim Peters Nov. 15, 2003

Nov. 15, 2003

> Modified Files: > heapqmodule.c > Log Message: > Verify heappop argument is a list. > > Index: heapqmodule.c > =================================================================== > RCS file: /cvsroot/python/python/dist/src/Modules/heapqmodule.c,v > retrieving revision 1.1 > retrieving revision 1.2 > diff -C2 -d -r1.1 -r1.2 > *** heapqmodule.c 8 Nov 2003 10:24:38 -0000 1.1 > --- heapqmodule.c 15 Nov 2003 12:33:01 -0000 1.2 > *************** > *** … [View More]

1 0

Getting socket information from socket objects
by Pavel Pergamenshchik Nov. 14, 2003

Nov. 14, 2003

Hi. It appears that the easiest way to retrieve family/type/protocol fields from socket objects is this: def getsockinfo(sock): s = `sock._sock` sp = s[1:-1].split(",")[1:] g = {} d = {} for i in sp: exec i.strip() in g, d return (d["family"], d["type"], d["protocol"]) Wouldn't it be nice to have accessors for these fields? My particular use-case is Windows-specific (IO completion port proactor), so winsock API provides this, but I'd rather avoid that crud. Also, … [View More]

2 1

RE: [Python-Dev] subtype_dealloc needs rethinking
by Tim Peters Nov. 13, 2003

Nov. 13, 2003

[Armin Rigo] > If all these ways involve the GC, Jim's problem does not, but all the "subtype_dealloc vs weakref callback vs cyclic gc" segfaults did. > a solution that would avoid similar problems in potentially other > deallocators might be to fix the GC instead: > >> incref >> call tp_clear >> decref > > This is the only place where the GC explicitely changes reference > counters. > It could just be skipped for objects with null … [View More]

1 0

which sleepycat versions do we support in 2.3.* ?
by Alex Martelli Nov. 13, 2003

Nov. 13, 2003

Somebody just wrote to help(a)python.org asking for guidance in resolving some conflicts in comments in 2.3.2 files regarding sleepycat versions we support. In Modules/Setup we say: """ The earliest supported version of that library is 3.0, the latest supported version is 4.0 (4.1 is specifically not supported, """ In README we say: """ Only versions 3.1 through 4.1 of Sleepycat's libraries provide the necessary API """ In setup.py we say: """ The earliest supported version of that library … [View More]

3 4