summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Include Carbon/Carbon.h if we're on OSX.Jack Jansen2001-09-012-2/+2
|
* Updated the Popt resources for the applets to the newest version.Jack Jansen2001-09-017-0/+0
|
* Added preferences/startup options for division warningJack Jansen2001-09-012-23/+37
| | | | | | | | 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.
* Added preferences/startup options for division warningJack Jansen2001-09-016-13/+28
| | | | and accepting unix-style newlines on input.
* The beginnings of a script to help finding / operators that may needGuido van Rossum2001-09-011-0/+237
| | | | | 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! :-)
* Add Listbox.itemconfig[ure] call. (A "recent" addition to Tk -- 8.0Guido van Rossum2001-09-011-5/+26
| | | | doesn't have it.) This is from SF bug #457487 by anonymous.
* Added the "Host" header to the "GET" example.Fred Drake2001-09-011-0/+1
| | | | This closes SF bug #457100.
* Add various and sundry news items -- most mine, one Barry's, oneGuido van Rossum2001-08-311-0/+44
| | | | Michael Hudson's.
* Oops. The -W option takes args, not -X.Guido van Rossum2001-08-311-1/+1
|
* Allow for the possibility that globals['__name__'] does not exist;Guido van Rossum2001-08-311-1/+4
| | | | | substitute "<string>" for the module name in that case. This actually occurred when running test_descr.py with -Dwarn.
* Add warning mode for classic division, almost exactly as specified inGuido van Rossum2001-08-319-25/+146
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Fix a memory leak in str_subtype_new(). (All the otherGuido van Rossum2001-08-311-3/+3
| | | | xxx_subtype_new() functions are OK, but I goofed up in this one. :-( )
* Correct name mangling algorithm, and add a comment.Guido van Rossum2001-08-311-2/+1
|
* Give 'super' a decent repr(), and readonly attributes to access theGuido van Rossum2001-08-301-11/+36
| | | | | type and obj properties. The "bogus super object" message is gone -- this will now just raise an AttributeError.
* Added all the new files in the right packages and file groups (I think, ↵Jack Jansen2001-08-301-0/+0
| | | | untested).
* SF bug #456621: normpath on Win32 not collapsing c:\\..Tim Peters2001-08-302-8/+35
| | | | | | 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.
* Add Jack Jansen's explanation of the MacOS X changesAndrew M. Kuchling2001-08-301-7/+43
|
* Superseded by the (generated) xx.mcp.Jack Jansen2001-08-301-0/+0
|
* Case mismatch in "import Types". Apparently nobody has looked at this for a ↵Jack Jansen2001-08-301-2/+2
| | | | looooong time. Reported by Chris Smith.
* We should look in the directory containing the module, not in the module ↵Jack Jansen2001-08-301-1/+1
| | | | itself, when we're looking for the resource file.
* Group some projects into "Done" and "To do". Get rid of Tim's mergeGuido van Rossum2001-08-301-213/+46
| | | | scratchpad -- the merge is long behind us.
* metaclass(): add some more examples of metaclasses, including oneGuido van Rossum2001-08-301-0/+104
| | | | | | using cooperative multiple inheritance. inherits(): add a test for subclassing the unicode type.
* SF patch #455966: Allow leading 0 in float/imag literals.Tim Peters2001-08-305-15/+84
| | | | Consequences for Jython still unknown (but raised on Jython-Dev).
* PyObject_Repr(): add missing ">" back at end of format string: "<%sGuido van Rossum2001-08-301-1/+1
| | | | object at %p>".