| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Slightly modified version of patch from Jon Nelson (jnelson).
|
|
|
|
|
| |
INSTALLED_FILES output. Modified version of a patch from
Jon Nelson (jnelson)
|
|
|
|
|
|
| |
"/" and "//", and doesn't really care what they *mean*, just that both
are tried (and that, whatever they mean, they act similarly for int and
long arguments).
|
|
|
|
| |
This closes SF patch #451538.
|
| |
|
|
|
|
|
| |
mostly changes of / operators into //. Once or twice I did more or
less than recommended.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
change their basic behavior: When parsing something that cannot possibly
be valid in either HTML or XHTML, raise an exception.
|
|
|
|
|
| |
the -Qwarnall option, so I've changed this to only filter out the one
warning that's a problem in practice.
|
| |
|
|
|
|
| |
broken declaration-like things.
|
|
|
|
| |
regarding bare ampersands in content.
|
|
|
|
| |
Fixed.
|
| |
|
| |
|
|
|
|
| |
e.g., (1L << 40000)/(1L << 40001) returns 0.5, not Inf or NaN or whatever.
|
|
|
|
|
|
|
| |
the fiddling is simply due to that no caller of PyLong_AsDouble ever
checked for failure (so that's fixing old bugs). PyLong_AsDouble is much
faster for big inputs now too, but that's more of a happy consequence
than a design goal.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of PyMapping_Keys because we know we have a real dict. Tolerate that
objects may have an attr named "__dict__" that's not a dict (Py_None
popped up during testing).
test_descr.py, test_dir(): Test the new classic-class behavior; beef up
the new-style class test similarly.
test_pyclbr.py, checkModule(): dir(C) is no longer a synonym for
C.__dict__.keys() when C is a classic class (looks like the same thing
that burned distutils! -- should it be *made* a synoym again? Then it
would be inconsistent with new-style class behavior.).
|
| |
|
| |
|
|
|
|
|
| |
integer types, and y must be >= 0. See discussion at
http://sf.net/tracker/index.php?func=detail&aid=457066&group_id=5470&atid=105470
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bag. It's clearly wrong for classic classes, at heart because a classic
class doesn't have a __class__ attribute, and I'm unclear on whether
that's feature or bug. I'll repair this once I find out (in the
meantime, dir() applied to classic classes won't find the base classes,
while dir() applied to a classic-class instance *will* find the base
classes but not *their* base classes).
Please give the new dir() a try and see whether you love it or hate it.
The new dir([]) behavior is something I could come to love. Here's
something to hate:
>>> class C:
... pass
...
>>> c = C()
>>> dir(c)
['__doc__', '__module__']
>>>
The idea that an instance has a __doc__ attribute is jarring (of course
it's really c.__class__.__doc__ == C.__doc__; likewise for __module__).
OTOH, the code already has too many special cases, and dir(x) doesn't
have a compelling or clear purpose when x isn't a module.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
mapping object", in the same sense dict.update(x) requires of x (that x
has a keys() method and a getitem).
Questionable: The other type constructors accept a keyword argument, so I
did that here too (e.g., dictionary(mapping={1:2}) works). But type_call
doesn't pass the keyword args to the tp_new slot (it passes NULL), it only
passes them to the tp_init slot, so getting at them required adding a
tp_init slot to dicts. Looks like that makes the normal case (i.e., no
args at all) a little slower (the time it takes to call dict.tp_init and
have it figure out there's nothing to do).
|
| |
|
|
|
|
| |
doesn't have it.) This is from SF bug #457487 by anonymous.
|
|
|
|
|
| |
substitute "<string>" for the module name in that case. This actually
occurred when running test_descr.py with -Dwarn.
|
| |
|
|
|
|
|
|
| |
I actually rewrote normpath quite a bit: it had no test cases, and as
soon as I starting writing some I found several cases that didn't make
sense.
|
|
|
|
|
|
| |
using cooperative multiple inheritance.
inherits(): add a test for subclassing the unicode type.
|
|
|
|
| |
Consequences for Jython still unknown (but raised on Jython-Dev).
|
|
|
|
|
|
|
|
|
| |
Fix list comp code generation -- emit GET_ITER instead of Const(0)
after the list.
Add CO_GENERATOR flag to generators.
Get CO_xxx flags from the new module
|
|
|
|
| |
tuples).
|
|
|
|
|
| |
based on a suggestion from Tim Peters; also make sure that we're really
doing exponentiation and not multiplication.
|
|
|
|
| |
bug from compile.c. (SF bug #456756.)
|
| |
|
|
|
|
|
|
|
| |
default_getpass(). This should prevent hanging when it is called in
IDLE.
Fixes SF bug #455648.
|
|
|
|
| |
when that test is doomed to deadlock.
|
|
|
|
| |
the setup script is running from inside Vim.
|
|
|
|
|
|
|
|
| |
try/except or try/finally.
Previous versions had only track SETUP_LOOP blocks and ignored the
exception part. This meant that it allowed continue inside a
try/except but generated buggy code. Now it does the right thing.
|
|
|
|
| |
Add CONTINUE_LOOP to the list of unconditional transfers
|
| |
|
|
|
|
|
|
|
| |
starts a new line.
Also fix undetected typo in visitDict() -- uncovered by recent change
to add lineno attrs to atoms.
|
| |
|
|
|
|
|
| |
XXX The code is still widely inaccurate, but most (all?) of the time
it's an overestimate.
|
|
|
|
|
| |
in which case it will hang because the import lock is already held
by the main thread.
|
|
|
|
|
|
|
|
|
|
| |
As the doc string for _lookupName() explains:
This routine uses a list instead of a dictionary, because a
dictionary can't store two different keys if the keys have the
same value but different types, e.g. 2 and 2L. The compiler
must treat these two separately, so it does an explicit type
comparison before comparing the values.
|
| |
|