summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Added docstrings by Neal Norwitz. This closes SF bug #450980.Fred Drake2001-09-045-3/+89
|
* Move call_trace(..., PyTrace_CALL, ...) call to top of eval_frame. ThatNeil Schemenauer2001-09-041-35/+35
| | | | | way it's called each time a generator is resumed. The tracing of normal functions should be unaffected by this change.
* Added docstring by Neal Norwitz. This closes SF bug #450981.Fred Drake2001-09-041-35/+86
|
* Added docstring by Neal Norwitz. This closes SF bug #450979.Fred Drake2001-09-041-4/+10
|
* Add more detail to the descriptions of the shutil functions.Fred Drake2001-09-041-4/+9
| | | | This closes SF bug #458223.
* Added documentation for sys.maxunicode and sys.warnoptions.Fred Drake2001-09-041-1/+14
| | | | | Fixed a markup error which caused an em dash to be presented as a minus sign. This closes SF bug #458350.
* HTMLParser is allowed to be more strict than sgmllib, so let's notFred Drake2001-09-042-37/+17
| | | | | change their basic behavior: When parsing something that cannot possibly be valid in either HTML or XHTML, raise an exception.
* - Reverse the meaning of the -m option: warnings about multiple /Guido van Rossum2001-09-041-35/+85
| | | | | | | | | | | | | | operators per line or statement are now on by default, and -m turns these warnings off. - Change the way multiple / operators are reported; a regular recommendation is always emitted after the warning. - Report ambiguous warnings (both int|long and float|complex used for the same operator). - Update the doc string again to clarify all this and describe the possible messages more precisely.
* Suppressing all DeprecationWarning messages was a bit of a problem forGuido van Rossum2001-09-041-3/+3
| | | | | the -Qwarnall option, so I've changed this to only filter out the one warning that's a problem in practice.
* Suppress the warning about regex here.Guido van Rossum2001-09-041-0/+4
|
* Enhanced the test for DOCTYPE declarations, added a test for dealing withFred Drake2001-09-041-14/+23
| | | | broken declaration-like things.
* Added reasonable parsing of the DOCTYPE declaration, fixed edge casesFred Drake2001-09-041-12/+260
| | | | regarding bare ampersands in content.
* On the mac some library paths returned were outdated, some were outright funny.Jack Jansen2001-09-041-5/+3
| | | | Fixed.
* Disabled _curses modules on MacOSX. The curses version is a 1994 BSDJack Jansen2001-09-041-1/+2
| | | | curses, far too old for _cursesmodule.c.
* Whitespace normalization.Tim Peters2001-09-045-8/+7
|
* Fixed a typo and added more tests.Tim Peters2001-09-041-1/+12
|
* Change long/long true division to return as many good bits as it can;Tim Peters2001-09-043-2/+78
| | | | e.g., (1L << 40000)/(1L << 40001) returns 0.5, not Inf or NaN or whatever.
* Move int_true_divide next to the other division routines.Tim Peters2001-09-041-6/+6
|
* Move long_true_divide next to the other division routines (for clarity!).Tim Peters2001-09-041-6/+6
|
* Raise OverflowError when appropriate on long->float conversion. Most ofTim Peters2001-09-045-23/+76
| | | | | | | 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.
* PEP 238 documented -Qwarn as warning only for classic int or longGuido van Rossum2001-09-044-7/+11
| | | | | division, and this makes sense. Add -Qwarnall to warn for all classic divisions, as required by the fixdiv.py tool.
* Rename the -D option to -Q, to avoid a Jython option name conflict.Guido van Rossum2001-09-043-13/+13
|
* Introduce new private API function _PyLong_AsScaledDouble. Not used yet,Tim Peters2001-09-042-0/+61
| | | | | | | | | | but will be the foundation for Good Things: + Speed PyLong_AsDouble. + Give PyLong_AsDouble the ability to detect overflow. + Make true division of long/long nearly as accurate as possible (no spurious infinities or NaNs). + Return non-insane results from math.log and math.log10 when passing a long that can't be approximated by a double better than HUGE_VAL.
* builtin_dir(): Treat classic classes like types. Use PyDict_Keys insteadTim Peters2001-09-043-28/+52
| | | | | | | | | | | | | | 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.).
* Don't use dir() to find instance attribute names.Neil Schemenauer2001-09-031-3/+7
|
* Fix the names of _PyObject_GC_TRACK and _PyObject_GC_UNTRACK when the GC isNeil Schemenauer2001-09-031-2/+2
| | | | disabled. Obviously everyone enables the GC. :-)
* Restore a line deleted by mistake.Tim Peters2001-09-031-0/+2
|
* New restriction on pow(x, y, z): If z is not None, x and y must be ofTim Peters2001-09-039-49/+79
| | | | | 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
* Make dir() wordier (see the new docstring). The new behavior is a mixedTim Peters2001-09-035-64/+206
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Made a doctest out of the examples in Guido's type/class tutorial.Tim Peters2001-09-031-0/+498
|
* Clarify the Borland situation, based on email from Stephen.Tim Peters2001-09-021-3/+5
|
* Repair typo in comment.Tim Peters2001-09-021-1/+1
|
* Added the last few missing files, and put everything in the right packages.Jack Jansen2001-09-021-0/+0
| | | | Tested, too:-)
* Implement what the docstring said: multiple slashes per line areGuido van Rossum2001-09-021-15/+26
| | | | | treated the same as single ones by default. Added -m option to issue a warning for this case instead.
* Add news about dictionary() constructor.Guido van Rossum2001-09-021-0/+4
|
* Make dictionary() a real constructor. Accepts at most one argument, "aTim Peters2001-09-022-3/+80
| | | | | | | | | | | | 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).
* Rewrite the tuple() docstring to parallel the list() docstring.Tim Peters2001-09-021-4/+4
|
* Repair apparent cut'n'pasteo in tuple() docstring.Tim Peters2001-09-021-1/+1
|
* Move the long minidom example to a separate file; \verbatiminput does theFred Drake2001-09-022-67/+66
| | | | | | 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.
* An anonymous contributor reveals his name...Guido van Rossum2001-09-021-0/+1
|
* Added more text to the docstring, updated the way the exit status isGuido van Rossum2001-09-021-31/+113
| | | | | | | 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).
* A grep-like tool that looks for division operators.Guido van Rossum2001-09-021-0/+89
|
* Whitespace normalization (tabs -> 4 spaces) in the Mac expectations.Guido van Rossum2001-09-021-35/+35
|
* Start items w/ "-" instead of "+" (consistency w/ earlier versions).Tim Peters2001-09-021-18/+17
| | | | | | 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.
* Silly typos.Jack Jansen2001-09-021-2/+2
|
* Don't call PyMac_HandleEvent in unix-PythonJack Jansen2001-09-021-0/+2
|
* Regenerated, mainly for new GC routines.Jack Jansen2001-09-012-8/+38
|
* xx.prj has been replaced by xx.mcp.Jack Jansen2001-09-011-74/+183
|
* Added glue routine for PyMac_BuildFSSpec, PyMac_GetFSRef and PyMac_BuildFSRef.Jack Jansen2001-09-014-8/+18
| | | | Moved the declarations to pymactoolbox.h.
* Don't call PyMac_HandleEvent if we're in unix-Python.Jack Jansen2001-09-012-0/+4
|
generated by cgit v0.12 at 2024-11-23 03:47:44 (GMT)