| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
disabled. Obviously everyone enables the GC. :-)
|
| |
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
Tested, too:-)
|
|
|
|
|
| |
treated the same as single ones by default. Added -m option to issue
a warning for this case instead.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
| |
|
|
|
|
|
|
| |
right thing with page breaks in long examples, while the verbatim
environment does not. This causes the example to wrap to the next page
instead of overwriting the page footer and bottom margin.
|
| |
|
|
|
|
|
|
|
| |
percolated out, and some general cleanup. The output is still the
same, except it now prints "Index: <file>" instead of "Processing:
<file>", so that the output can be used as input for patch (but only
the diff-style parts of it).
|
| |
|
| |
|
|
|
|
|
|
| |
Stephen Hansen reported via email that he didn't finish the port to
Borland C, so remove the old item saying it worked and add a new item
saying what I know; I've asked Stephen for more details.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Moved the declarations to pymactoolbox.h.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
and accepting unix-style newlines on input.
Also (finally) added a startup option to get -vv behaviour.
Moved __convert_to_newlines to main.c because that's easier with the newline option.
|
|
|
|
| |
and accepting unix-style newlines on input.
|
|
|
|
|
| |
to be change to //. The code is pretty gross so far, and I promise
I'll work on this more, but I have to go eat now! :-)
|
|
|
|
| |
doesn't have it.) This is from SF bug #457487 by anonymous.
|
|
|
|
| |
This closes SF bug #457100.
|
|
|
|
| |
Michael Hudson's.
|
| |
|
|
|
|
|
| |
substitute "<string>" for the module name in that case. This actually
occurred when running test_descr.py with -Dwarn.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
PEP 238. Changes:
- add a new flag variable Py_DivisionWarningFlag, declared in
pydebug.h, defined in object.c, set in main.c, and used in
{int,long,float,complex}object.c. When this flag is set, the
classic division operator issues a DeprecationWarning message.
- add a new API PyRun_SimpleStringFlags() to match
PyRun_SimpleString(). The main() function calls this so that
commands run with -c can also benefit from -Dnew.
- While I was at it, I changed the usage message in main() somewhat:
alphabetized the options, split it in *four* parts to fit in under
512 bytes (not that I still believe this is necessary -- doc strings
elsewhere are much longer), and perhaps most visibly, don't display
the full list of options on each command line error. Instead, the
full list is only displayed when -h is used, and otherwise a brief
reminder of -h is displayed. When -h is used, write to stdout so
that you can do `python -h | more'.
Notes:
- I don't want to use the -W option to control whether the classic
division warning is issued or not, because the machinery to decide
whether to display the warning or not is very expensive (it involves
calling into the warnings.py module). You can use -Werror to turn
the warnings into exceptions though.
- The -Dnew option doesn't select future division for all of the
program -- only for the __main__ module. I don't know if I'll ever
change this -- it would require changes to the .pyc file magic
number to do it right, and a more global notion of compiler flags.
- You can usefully combine -Dwarn and -Dnew: this gives the __main__
module new division, and warns about classic division everywhere
else.
|
|
|
|
| |
xxx_subtype_new() functions are OK, but I goofed up in this one. :-( )
|
| |
|
|
|
|
|
| |
type and obj properties. The "bogus super object" message is gone --
this will now just raise an AttributeError.
|
|
|
|
| |
untested).
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
looooong time. Reported by Chris Smith.
|
|
|
|
| |
itself, when we're looking for the resource file.
|
|
|
|
| |
scratchpad -- the merge is long behind us.
|
|
|
|
|
|
| |
using cooperative multiple inheritance.
inherits(): add a test for subclassing the unicode type.
|
|
|
|
| |
Consequences for Jython still unknown (but raised on Jython-Dev).
|
|
|
|
| |
object at %p>".
|