- 02 Şub, 2009 1 kayıt (commit)
-
-
Raymond Hettinger yazdı
-
- 26 Agu, 2008 1 kayıt (commit)
-
-
Antoine Pitrou yazdı
match Python 2.5 speed despite the __instancecheck__ / __subclasscheck__ mechanism. In the process, fix a bug where isinstance() and issubclass(), when given a tuple of classes as second argument, were looking up __instancecheck__ / __subclasscheck__ on the tuple rather than on each type object. Reviewed by Benjamin Peterson and Raymond Hettinger.
-
- 12 Agu, 2008 1 kayıt (commit)
-
-
Martin v. Löwis yazdı
by denying s# to parse objects that have a releasebuffer procedure, and introducing s*. More module might need to get converted to use s*.
-
- 18 Mar, 2008 1 kayıt (commit)
-
-
Travis E. Oliphant yazdı
Finish backporting new buffer API to Python 2.6. Left to do: memoryview object and structmodule. But, these need to be finished in Python 3.0 first. No objects support the new buffer API in Python 2.6 as of yet, and except for the memoryview object, I don't think they will.
-
- 17 Mar, 2008 1 kayıt (commit)
-
-
Travis E. Oliphant yazdı
-
- 17 Şub, 2008 1 kayıt (commit)
-
-
Eric Smith yazdı
Highlights: - Adding PyObject_Format. - Adding string.Format class. - Adding __format__ for str, unicode, int, long, float, datetime. - Adding builtin format. - Adding ''.format and u''.format. - str/unicode fixups for formatters. The files in Objects/stringlib that implement PEP 3101 (stringdefs.h, unicodedefs.h, formatter.h, string_format.h) are identical in trunk and py3k. Any changes from here on should be made to trunk, and changes will propogate to py3k).
-
- 10 Şub, 2008 1 kayıt (commit)
-
-
Eric Smith yazdı
-
- 04 Şub, 2008 1 kayıt (commit)
-
-
Jeffrey Yasskin yazdı
-
- 19 Ara, 2007 1 kayıt (commit)
-
-
Christian Heimes yazdı
#1629: Renamed Py_Size, Py_Type and Py_Refcnt to Py_SIZE, Py_TYPE and Py_REFCNT. Macros for b/w compatibility are available.
-
- 06 Ara, 2007 1 kayıt (commit)
-
-
Raymond Hettinger yazdı
Factor-out common calling code by simplifying the length_hint API. Speed-up the function by caching the PyObject_String for the attribute lookup.
-
- 21 Tem, 2007 1 kayıt (commit)
-
-
Martin v. Löwis yazdı
backwards compatibility. Add Py_Refcnt, Py_Type, Py_Size, and PyVarObject_HEAD_INIT.
-
- 22 Eki, 2006 1 kayıt (commit)
-
-
Martin v. Löwis yazdı
Will backport to 2.5.
-
- 12 Agu, 2006 1 kayıt (commit)
-
-
Neal Norwitz yazdı
I modified this patch some by fixing style, some error checking, and adding XXX comments. This patch requires review and some changes are to be expected. I'm checking in now to get the greatest possible review and establish a baseline for moving forward. I don't want this to hold up release if possible.
-
- 18 Nis, 2006 1 kayıt (commit)
-
-
Skip Montanaro yazdı
_PyObject_Call(Function|Method)_SizeT into Include/abstract.h. This gets them under the umbrella of the extern "C" { ... } block in that file.
-
- 14 Nis, 2006 1 kayıt (commit)
-
-
Martin v. Löwis yazdı
PyObject_CallMethod aware of PY_SSIZE_T_CLEAN.
-
- 07 Mar, 2006 1 kayıt (commit)
-
-
Guido van Rossum yazdı
This was mostly written by Travis Oliphant. I've inspected it all; Neal Norwitz and MvL have also looked at it (in an earlier incarnation).
-
- 04 Mar, 2006 1 kayıt (commit)
-
-
Neal Norwitz yazdı
-
- 15 Şub, 2006 1 kayıt (commit)
-
-
Martin v. Löwis yazdı
-
- 11 Şub, 2006 1 kayıt (commit)
-
- 24 Eyl, 2005 1 kayıt (commit)
-
-
Raymond Hettinger yazdı
-
- 12 Mar, 2004 2 kayıt (commit)
-
-
Raymond Hettinger yazdı
-
Raymond Hettinger yazdı
three recent optimizations. Aside from reducing code volume, it increases readability.
-
- 20 Eki, 2003 1 kayıt (commit)
-
-
Walter Dörwald yazdı
(From SF patch #810751)
-
- 12 May, 2003 1 kayıt (commit)
-
-
Fred Drake yazdı
-
- 28 Şub, 2003 1 kayıt (commit)
-
-
Raymond Hettinger yazdı
-
- 25 Kas, 2002 1 kayıt (commit)
-
-
Michael W. Hudson yazdı
-
- 12 Agu, 2002 1 kayıt (commit)
-
-
Mark Hammond yazdı
Thanks to Skip Montanaro and Kalle Svensson for the patches.
-
- 08 May, 2002 1 kayıt (commit)
-
-
Martin v. Löwis yazdı
Avoid checks for negative indices and duplicate checks for support of the sequence protocol.
-
- 05 Ock, 2002 1 kayıt (commit)
-
-
Martin v. Löwis yazdı
-
- 28 Kas, 2001 1 kayıt (commit)
-
-
Jeremy Hylton yazdı
Change macros as requested by Guido
-
- 09 Kas, 2001 1 kayıt (commit)
-
-
Jeremy Hylton yazdı
supports the single-segment readable buffer interface. Add documentation for this and other PyObject_XXXBuffer() calls.
-
- 28 Eki, 2001 1 kayıt (commit)
-
-
Fred Drake yazdı
PyObject_CallMethodObArgs() ---> PyObject_CallMethodObjArgs()
-
- 26 Eki, 2001 2 kayıt (commit)
-
-
Fred Drake yazdı
PyObject_CallFunctionObArgs() and PyObject_CallMethodObArgs() have the advantage that no format strings need to be parsed. The CallMethod variant also avoids creating a new string object in order to retrieve a method from an object as well.
-
Tim Peters yazdı
outer level, the iterator protocol is used for memory-efficiency (the outer sequence may be very large if fully materialized); at the inner level, PySequence_Fast() is used for time-efficiency (these should always be sequences of length 2). dictobject.c, new functions PyDict_{Merge,Update}FromSeq2. These are wholly analogous to PyDict_{Merge,Update}, but process a sequence-of-2- sequences argument instead of a mapping object. For now, I left these functions file static, so no corresponding doc changes. It's tempting to change dict.update() to allow a sequence-of-2-seqs argument too. Also changed the name of dictionary's keyword argument from "mapping" to "x". Got a better name? "mapping_or_sequence_of_pairs" isn't attractive, although more so than "mosop" <wink>. abstract.h, abstract.tex: Added new PySequence_Fast_GET_SIZE function, much faster than going thru the all-purpose PySequence_Size. libfuncs.tex: - Document dictionary(). - Fiddle tuple() and list() to admit that their argument is optional. - The long-winded repetitions of "a sequence, a container that supports iteration, or an iterator object" is getting to be a PITA. Many months ago I suggested factoring this out into "iterable object", where the definition of that could include being explicit about generators too (as is, I'm not sure a reader outside of PythonLabs could guess that "an iterator object" includes a generator call). - Please check my curly braces -- I'm going blind <0.9 wink>. abstract.c, PySequence_Tuple(): When PyObject_GetIter() fails, leave its error msg alone now (the msg it produces has improved since PySequence_Tuple was generalized to accept iterable objects, and PySequence_Tuple was also stomping on the msg in cases it shouldn't have even before PyObject_GetIter grew a better msg).
-
- 08 Eyl, 2001 1 kayıt (commit)
-
-
Tim Peters yazdı
iterable object. I'm not sure how that got overlooked before! Got rid of the internal _PySequence_IterContains, introduced a new internal _PySequence_IterSearch, and rewrote all the iteration-based "count of", "index of", and "is the object in it or not?" routines to just call the new function. I suppose it's slower this way, but the code duplication was getting depressing.
-
- 08 Agu, 2001 1 kayıt (commit)
-
-
Guido van Rossum yazdı
This introduces: - A new operator // that means floor division (the kind of division where 1/2 is 0). - The "future division" statement ("from __future__ import division) which changes the meaning of the / operator to implement "true division" (where 1/2 is 0.5). - New overloadable operators __truediv__ and __floordiv__. - New slots in the PyNumberMethods struct for true and floor division, new abstract APIs for them, new opcodes, and so on. I emphasize that without the future division statement, the semantics of / will remain unchanged until Python 3.0. Not yet implemented are warnings (default off) when / is used with int or long arguments. This has been on display since 7/31 as SF patch #443474. Flames to /dev/null.
-
- 02 Agu, 2001 1 kayıt (commit)
-
-
Tim Peters yazdı
-
- 05 May, 2001 3 kayıt (commit)
-
-
Tim Peters yazdı
safely together and don't duplicate logic (the common logic was factored out into new private API function _PySequence_IterContains()). Visible change: some_complex_number in some_instance no longer blows up if some_instance has __getitem__ but neither __contains__ nor __iter__. test_iter changed to ensure that remains true.
-
Tim Peters yazdı
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.
-
Tim Peters yazdı
internals) so clients can be a lot dumber (wrt their knowledge).
-