| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Cater to that.
+ Major speed boost via not reading more of files than necessary. This
was no slouch before; now it screams.
+ Improve msg when giving up on a goofy future statement.
|
| |
|
|
|
|
| |
David Goodger.
|
|
|
|
|
| |
Otherwise printlist(surprise) will fail with a TypeError, because map
is called with an argument that doesn't support iteration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The descr changes moved the dispatch for calling objects from
call_object() in ceval.c to PyObject_Call() in abstract.c.
call_object() and the many functions it used in ceval.c were no longer
used, but were not removed.
Rename meth_call() as PyCFunction_Call() so that it can be called by
the CALL_FUNCTION opcode in ceval.c.
Also, fix error message that referred to PyEval_EvalCodeEx() by its
old name eval_code2(). (I'll probably refer to it by its old name,
too.)
|
| |
|
| |
|
|
|
|
|
|
| |
- Remove various 'global' directives and move some global definitions
inside the test functions that use them -- we have nested scopes so
the old hacks using globals are no longer needed.
|
|
|
|
|
|
|
| |
XXX There are still some loose ends: repr(), str(), hash() and
comparisons don't inherit a default implementation from object. This
must be resolved similarly to the way it's resolved for classic
instances.
|
|
|
|
| |
into indented lines each of which probably fits on a typical screen line).
|
|
|
|
|
|
|
|
|
|
| |
XXX This is not sufficient: if a dynamic class has no __repr__ method
(for instance), but later one is added, that doesn't add a tp_repr
slot, so repr() doesn't call the __repr__ method. To make this work,
I'll have to add default implementations of several slots to 'object'.
XXX Also, dynamic types currently only inherit slots from their
dominant base.
|
|
|
|
| |
broken). Also fix an invalid reference to C (should be S).
|
| |
|
|
|
|
|
| |
little bit using a dictionary to avoid more code duplication as
more platforms are supported.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Revised version of Fred's patch, including support for ~ operator.
If the unary +, -, or ~ operator is applied to a constant, don't
generate a UNARY_xxx opcode. Just store the approriate value as a
constant. If the value is negative, extend the string containing the
constant and insert a negative in the 0th position.
For ~, compute the inverse of int and longs and use them directly, but
be prepared to generate code for all other possibilities (invalid
numbers, floats, complex).
|
|
|
|
| |
about your platform too.
|
| |
|
|
|
|
|
| |
and even if we have a long time left to wait, try the lock at least 20
times/second.
|
| |
|
|
|
|
| |
before "foo/bar", which is not true on the mac (where they are "foo" and ":foo:bar", respectively; ":foo" would be fine too, but "foo" is the preferred spelling). Fixed by sorting the output.
|
|
|
|
| |
on files, but in stead open the parent directory! We now explicitly test for the argument being a directory and simulate ENOTDIR otherwise.
|
|
|
|
| |
check that it isn't incidentally running already.
|
|
|
|
| |
needed, and without it you can get work done while building the projects:-)
|
|
|
|
|
|
|
|
| |
same module twice, which apparently crashes Python. I could not test the
error condition, but in normal life it seems to have no adverse effects.
Also removed an unsued variable, and corrected 2 glaring errors (missing
'case' in front of a label).
|
|
|
|
|
|
|
| |
because nested scopes are always enabled.
(Accidentally checked in one small change along this path yesterday,
wreaking havoc in the Windows build.)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
canceling an edit operation would not revert the value of the field.
The fix takes care to destroy the Entry object, as suggested in the
patch.
|
|
|
|
|
|
|
|
|
|
| |
IDLE and pydoc into a separate component. That's almost as big as the
rest of Python (excl. docs and test suite) combined.
Pop up a confimation box if they choose to install at least one of
{Tcl/Tk/IDLE/pydoc, Tools, Test suite} but do not choose to install
Python -- doesn't make much sense, so ask whether that's really what they
want.
|
|
|
|
|
|
|
|
| |
in xml.sax.saxutils, since that is the right function to use for quoting
attribute values.
This closes SF bug #444707.
Cleaned up a variety of other minor markup errors.
|
|
|
|
| |
Converted tests to PyUnit.
|
|
|
|
| |
have it yet).
|
|
|
|
| |
Minor grammatical changes, reformattings, and an error fix from Keith Briggs
|
|
|
|
| |
way; see code comments.
|
|
|
|
| |
attributes as well.
|
|
|
|
|
|
|
|
|
|
|
| |
Replace uses of PyCF_xxx with CO_xxx.
Replace individual feature slots in PyFutureFeatures with single
bitmask ff_features.
When flags must be transfered among the three parts of the interpreter
that care about them -- the pythonrun layer, the compiler, and the
future feature parser -- can simply or (|) the definitions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replace individual slots in PyFutureFeatures with a single bitmask
with one field per feature. The flags for this bitmask are the same
as the flags used in the co_flags slot of a code object.
XXX This means we waste several bits, because they are used
for co_flags but have no meaning for future statements. Don't
think this is an issue.
Remove the NESTED_SCOPES_DEFAULT define and others. Not sure what
they were for anyway.
Remove all the PyCF_xxx flags, but define PyCF_MASK in terms of the
CO_xxx flags that are relevant for this release.
Change definition of PyCompilerFlags so that cf_flags matches
co_flags.
|
| |
|
| |
|
|
|
|
| |
attribute changed again.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
problem). inherit_slots() is split in two parts: inherit_special()
which inherits the flags and a few very special members from the
dominant base; inherit_slots() which inherits only regular slots,
and is now called for each base in the MRO in turn. These are now
both void functions since they don't have error returns.
- Added object.__setitem__() back -- for the same reason as
object.__new__(): a subclass of object should be able to call
object.__new__().
- add_wrappers() was moved around to be closer to where it is used (it
was defined together with add_methods() etc., but has nothing to do
with these).
|
|
|
|
| |
Depend AF_PACKET on HAVE_NETPACKET_PACKET_H.
|