- 27 Haz, 2001 9 kayıt (commit)
-
-
Martin v. Löwis yazdı
-
Fredrik Lundh yazdı
-
Fred Drake yazdı
Python interpreter. This change adds two new C-level APIs: PyEval_SetProfile() and PyEval_SetTrace(). These can be used to install profile and trace functions implemented in C, which can operate at much higher speeds than Python-based functions. The overhead for calling a C-based profile function is a very small fraction of a percent of the overhead involved in calling a Python-based function. The machinery required to call a Python-based profile or trace function been moved to sysmodule.c, where sys.setprofile() and sys.setprofile() simply become users of the new interface. As a side effect, SF bug #436058 is fixed; there is no longer a _PyTrace_Init() function to declare.
-
Fred Drake yazdı
Python interpreter. This change adds two new C-level APIs: PyEval_SetProfile() and PyEval_SetTrace(). These can be used to install profile and trace functions implemented in C, which can operate at much higher speeds than Python-based functions. The overhead for calling a C-based profile function is a very small fraction of a percent of the overhead involved in calling a Python-based function. The machinery required to call a Python-based profile or trace function been moved to sysmodule.c, where sys.setprofile() and sys.setprofile() simply become users of the new interface.
-
Fredrik Lundh yazdı
tests.
-
Barry Warsaw yazdı
-
Thomas Wouters yazdı
-
Tim Peters yazdı
that required explicitly calling LazyList.clear() in the two tests that use LazyList (I added a LazyList Fibonacci generator too). A real bitch: the extremely inefficient first version of the 2-3-5 test *looked* like a slow leak on Win98SE, but it wasn't "really": it generated so many results that the heap grew over 4Mb (tons of frames! the number of frames grows exponentially in that test). Then Win98SE malloc() starts fragmenting address space allocating more and more heaps, and the visible memory use grew very slowly while the disk was thrashing like mad. Printing fewer results (i.e., keeping the heap burden under 4Mb) made that illusion vanish. Looks like there's no hope for plugging the LazyList leaks automatically short of adding frameobjects and genobjects to gc. OTOH, they're very easy to break by hand, and they're the only *kind* of plausibly realistic leaks I've been able to provoke. Dilemma.
-
Martin v. Löwis yazdı
Implement sys.maxunicode. Explicitly wrap around upper/lower computations for wide Py_UNICODE. When decoding large characters with UTF-8, represent expected test results using the \U notation.
-
- 26 Haz, 2001 24 kayıt (commit)
-
-
Guido van Rossum yazdı
- the correct range for the error message is range(0x110000); - put the 4-byte Unicode-size code inside the same else branch as the 2-byte code, rather generating unreachable code in the 2-byte case. - Don't hide the 'else' behine the '}'. (I would prefer that in 4-byte mode, any value should be accepted, but reasonable people can argue about that, so I'll put that off.)
-
Fredrik Lundh yazdı
-
Martin v. Löwis yazdı
when checking surrogates.
-
Tim Peters yazdı
SIZEOF_SHORT by hand here. Also added dynamic check that SIZEOF_SHORT is correct for the platform (in _testcapimodule).
-
Tim Peters yazdı
not writable -- too dangerous!) from Python code.
-
Martin v. Löwis yazdı
Add configure option --enable-unicode. Add config.h macros Py_USING_UNICODE, PY_UNICODE_TYPE, Py_UNICODE_SIZE, SIZEOF_WCHAR_T. Define Py_UCS2. Encode and decode large UTF-8 characters into single Py_UNICODE values for wide Unicode types; likewise for UTF-16. Remove test whether sizeof Py_UNICODE is two.
-
Jack Jansen yazdı
such as the Core Foundation ones.
-
Jack Jansen yazdı
-
Jack Jansen yazdı
First small step towards bgen-generated CoreFoundation. there is hardly any real functionality yet, but method chains seem to work, and so do Retain/Release semantics.
-
Tim Peters yazdı
Makes it much easier to find references via dumb editor search (former "frame" in particular was near-hopeless).
-
Fredrik Lundh yazdı
sizeof(int)
-
Barry Warsaw yazdı
-
Barry Warsaw yazdı
mapping objects as an argument.
-
Barry Warsaw yazdı
a non-dictionary mapping object. Include tests for several expected failure modes.
-
Barry Warsaw yazdı
"mapping" object, specifically one that supports PyMapping_Keys() and PyObject_GetItem(). This allows you to say e.g. {}.update(UserDict()) We keep the special case for concrete dict objects, although that seems moderately questionable. OTOH, the code exists and works, so why change that? .update()'s docstring already claims that D.update(E) implies calling E.keys() so it's appropriate not to transform AttributeErrors in PyMapping_Keys() to TypeErrors. Patch eyeballed by Tim.
-
Fredrik Lundh yazdı
wrt surrogates. (this extends the valid range from 65535 to 1114111)
-
Fredrik Lundh yazdı
HAVE_USABLE_WCHAR_T
-
Fredrik Lundh yazdı
unicodeobject.h, which forces sizeof(Py_UNICODE) == sizeof(Py_UCS4). (this may be good enough for platforms that doesn't have a 16-bit type. the UTF-16 codecs don't work, though)
-
Fredrik Lundh yazdı
sizeof(Py_UNICODE) >= sizeof(long). also changed surrogate expansion to work if sizeof(Py_UNICODE) > 2.
-
Fredrik Lundh yazdı
HAVE_USABLE_WCHAR_T
-
Jack Jansen yazdı
-
Just van Rossum yazdı
-
Just van Rossum yazdı
package to be loaded from a PYD resource.
-
Tim Peters yazdı
Not anymore <wink>. Pure hack. Doesn't fix any other "if 0:" glitches.
-
- 25 Haz, 2001 7 kayıt (commit)
-
-
Tim Peters yazdı
Iterators list for bringing it up!
-
Just van Rossum yazdı
Return self.trace_dispatch from dispatch_return() to enable stepping through generators. (An alternative would be to create a new "yield" debugger event, but that involves many more changes, and might break Bdb subclasses.)
-
Fred Drake yazdı
-
Jack Jansen yazdı
-
Steven M. Gava yazdı
-
Martin v. Löwis yazdı
-
Martin v. Löwis yazdı
-