| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the past, an object's tp_compare could return any value. In 2.2
the docs were tightened to require it to return -1, 0 or 1; and -1 for
an error.
We now issue a warning if the value is not in this range. When an
exception is raised, we allow -1 or -2 as return value, since -2 will
the recommended return value for errors in the future. (Eventually
tp_compare will also be allowed to return +2, to indicate
NotImplemented; but that can only be implemented once we know all
extensions return a value in [-2...1]. Or perhaps it will require the
type to set a flag bit.)
I haven't decided yet whether to backport this to 2.2.x. The patch
applies fine. But is it fair to start warning in 2.2.2 about code
that worked flawlessly in 2.2.1?
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
mode).
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
In the error message, say del for del and assign for everything else.
|
| | |
|
| | |
|
| |
|
|
| |
in the mode (it's forbidden).
|
| |
|
|
|
|
|
|
|
| |
get_file() must convert 'U' to "r" PY_STDIOTEXTMODE before calling
fopen().
imp_load_module() must accept 'r' or 'U' or something with '+'.
Also reflow some long lines.
|
| | |
|
| | |
|
| |
|
|
| |
Now we just need to make sure people know about it...
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
readline in all python versions is configured
to append a 'space' character for a successful
completion. But for almost all python expressions
'space' is not wanted (see coding conventions PEP 8).
For example if you have a function 'longfunction'
and you type 'longf<TAB>' you get 'longfunction '
as a completion. note the unwanted space at the
end.
The patch fixes this behaviour by setting readline's
append_character to '\0' which means don't append
anything. This doesn't work with readline < 2.1
(AFAIK nowadays readline2.2 is in good use).
An alternative approach would be to make the
append_character
accessable from python so that modules like
the rlcompleter.py can set it to '\0'.
[Ed.: I think expecting readline >= 2.2 is fine. If a completer wants
another character they can append that to the keyword in the list.]
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- Add comment explaining the structure of the stack.
- Minor optimization: make stack tuple directly usable as part of return
value for enter/exit events.
|
| | |
|
| |
|
|
|
| |
and got confused by certain log files. Remove logreader_refill and the
associated logic and replace with fgetc.
|
| | |
|
| | |
|
| |
|
|
| |
not updated after 2.2).
|
| |
|
|
|
| |
that are in the process of deprecation (PendingDeprecationWarning).
Docs could be improved.
|
| |
|
|
| |
UINT4.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
[ 558914 ] Build md5.c fails on Cray T3E
I've also deleted a comment that I didn't understand. Feel free to
put it back if it makes/made sense to you.
|
| | |
|
| |
|
|
|
| |
Using Unicode-aware methods may still die with a NameError on unicode.
Maybe there's a more elegant solution but I doubt anybody cares.)
|
| |
|
|
|
| |
literals must not contain \u, \U or \N escapes. (XXX Should they also
not contain non-ASCII characters?)
|
| |
|
|
|
|
|
| |
in there, and convert it to "rb" (or "r" for non-universal-newline builds)
before passing it to fopen().
Fixes #561326.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(or how do I "mark" something to be a candidate?)
fixed an old buglet that caused bdb to be unable to
continue in the botframe, after a breakpoint was set.
the key idea is not to set botframe to the bottom level frame,
but its f_back, which actually might be None.
Additional changes: migrated old exception trick to use
sys._getframe(), which exists both in 2.1 and 2.2 .
Note: I believe Mark Hammond needs to look over his code now.
F5 correctly starts up in the debugger, but later on doesn't stop at a given
breakpoint any longer.
kind regards - chris
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
[ 559250 ] more POSIX signal stuff
Adds support (and docs and tests and autoconfery) for posix signal
mask handling -- sigpending, sigprocmask and sigsuspend.
|
| | |
|
| |
|
|
| |
allow subclassing.
|
| | |
|
| |
|
|
| |
target.
|
| |
|
|
|
|
| |
whose tp_mro hasn't been initialized, it would dump core. Fix this by
checking for NULL and calling PyType_Ready(). Will fix this in 2.2.1
too.
|
| |
|
|
| |
Other minor rewrites
|
| |
|
|
|
|
|
| |
for 'str' and 'unicode', and can be used instead of
types.StringTypes, e.g. to test whether something is "a string":
isinstance(x, string) is True for Unicode and 8-bit strings. This
is an abstract base class and cannot be instantiated directly.
|
| |
|
|
| |
different free or alloc slot.
|
| | |
|
