| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
callable objects than regular Pythonm functions as their im_func.
|
| |
|
|
|
|
| |
after a return).
|
|
|
|
| |
after a return or goto).
|
|
|
|
| |
after a return).
|
|
|
|
|
| |
(unreachable break after a return) but one was a real bug:
ReadFrames() was getting a bogus framecount because of a missing '&'.
|
| |
|
|
|
|
|
| |
This is because they are huge and the stack is limited on Windows.
Other platforms keep declaring it on the stack.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
a doc string.
|
| |
|
|
|
|
|
|
|
| |
PythonCmd_Error() but failed to return. The error wasn't very likely
(only when we run out of memory) but since the check is there we might
as well return the error. (I think that Barry introduced this buglet
when he added error checks everywhere.)
|
|
|
|
|
|
|
|
|
| |
# from my PC at home, but it can't send email :-(
Add a clarifying comment about the new ENTER_OVERLAP and
LEAVE_OVERLAP_TCL macros; get rid of all the bogus tests for deleted
interpreters (Tcl already tests for this; they were left over from an
earlier misguided attempt to fix the threading).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There were some serious problem with the thread-safety code.
The basic problem was that often the result was gotten out of
the Tcl interpreter object after releasing the Tcl lock.
Of course, another thread might have changed the return value
already, and this was indeed happening. (Amazing what trying
it on a different thread implementation does!)
The solution is to grab the Python lock without releasing the
Tcl lock, so it's safe to create a string object or set the
exceptions from the Tcl interpreter. Once that's done, the
Tcl lock is released.
Note that it's now legal to acquire the Python lock while the
the Tcl lock is held; but the reverse is not true: the Python
lock must be released before the Tcl lock is acquired. This
in order to avoid deadlines. Fortunately, there don't seem to
be any problems with this.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(The "sort of" is because it uses kbhit() to detect that the user
starts typing, and then no events are processed until they hit
return.)
Also fixed a nasty locking bug: EventHook() is called without the Tcl
lock set, so it can't use the ENTER_PYTHON and LEAVE_PYTHON macros,
which manipulate both the Python and the Tcl lock. I now only acquire
and release the Python lock.
(Haven't tested this on Unix yet...)
|
|
|
|
|
| |
of Windows file handles. Now it is at least compatible with itself on
Unix!
|
|
|
|
|
| |
tcgetattr(). This seems to be the only correct way to cope with
platform-specific structure members...
|
| |
|
|
|
|
| |
else the damn thing won't compile on Windows :-(
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Tkinter. This adds a separate lock -- read the comments. (This was
also needed for Mark Hammond's attempts to make PythonWin
Tkinter-friendly.)
The changes have affected the EventHook slightly, too; and I've done
some more cleanup of the code that deals with the different versions
of Tcl_CreateFileHandler().
|
|
|
|
|
|
| |
so that our #ifdef test has the wrong effect. Substitute hardcoded
values for some important symbols (but not for the whole range -- some
are pretty obscure so it's not worth it).
|
| |
|
| |
|
|
|
|
| |
places.
|
|
|
|
|
|
|
|
|
|
| |
registers an input file handler for stdin with Tcl and handles Tcl
events until something is available on stdin; it then deletes the
handler and returns from EventHook().
This works with or without GNU readline, and doesn't busy-wait.
It still doesn't work for Mac or Windows :-(
|
|
|
|
|
|
|
|
| |
Rationalized the doc strings.
Also simplify the module initialization -- we don't need a __version__
which is set to "$Rev" :-) and we don't need a fatal error when the
initialization fails.
|
|
|
|
|
| |
argument was initialized to Py_None, but later checked for NULL.
Consistently use Py_None.
|
| |
|
|
|
|
|
| |
tp_as_sequence or tp_as_mapping structure is made without checking it
for NULL first.
|
|
|
|
| |
get_line_buffer() does not take an optional argument.
|
|
|
|
| |
we have no .c source.
|
| |
|
|
|
|
| |
of error when sys.modules isn't there.
|
| |
|
| |
|
|
|
|
| |
they should have a Repr() function.
|
|
|
|
| |
warning (at least under Linux).
|
|
|
|
|
|
|
| |
- When facility not specified to syslog() method, use default from openlog()
(This is how it was claimed to work in the documentation)
- Potential resource leak of o_ident, now cleaned up in closelog()
- Minor comment accuracy fix.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
symlink to a symlink can work.
(Jack)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
most common interface to Tcl, the call() method, by maybe 20-25%.
The speedup code avoids the construction of a Tcl command string from
the argument list -- the Tcl argument list is immediately parsed back
by Tcl_Eval() into a list that is *guaranteed* (by Tcl_Merge()) to be
exactly the same list, so instead we look up the command info and call
the command function directly. If the lookup fails, we fall back to
the old method (Tcl_Merge() + Tcl_Eval()) so we don't need to worry
about special cases like undefined commands or the occasional command
("after") that sets the info.proc pointer to NULL -- let TclEval()
deal with these.
|
|
|
|
|
|
|
|
| |
the address of the Tcl interpreter object, as an integer. Not very
useful for the Python programmer, but this can be called by another C
extension that needs to make calls into the Tcl/Tk C API and needs to
get the address of the Tcl interpreter object. A simple cast of the
return value to (Tcl_Interp *) will do the trick now.
|
|
|
|
| |
Fixed a memory leak in an error handler.
|