summaryrefslogtreecommitdiffstats
path: root/Lib
Commit message (Collapse)AuthorAgeFilesLines
* Detabified.Guido van Rossum2003-04-091-20/+5
| | | | Removed dead code.
* - New function sys.call_tracing() allows pdb to debug codeGuido van Rossum2003-04-091-0/+33
| | | | | | recursively. - pdb has a new command, "debug", which lets you step through arbitrary code from the debugger's (pdb) prompt.
* Patch #709178: remove -static option from cygwinccompilerJason Tishler2003-04-091-8/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Currently, the cygwinccompiler.py compiler handling in distutils is invoking the cygwin and mingw compilers with the -static option. Logically, this means that the linker should choose to link to static libraries instead of shared/dynamically linked libraries. Current win32 binutils expect import libraries to have a .dll.a suffix and static libraries to have .a suffix. If -static is passed, it will skip the .dll.a libraries. This is pain if one has a tree with both static and dynamic libraries using this naming convention, and wish to use the dynamic libraries. The -static option being passed in distutils is to get around a bug in old versions of binutils where it would get confused when it found the DLLs themselves. The decision to use static or shared libraries is site or package specific, and should be left to the setup script or to command line options.
* Detabbed.Jack Jansen2003-04-0923-7956/+7970
|
* Remove the --verify option in favor of the standard -n/--dry-run optionAndrew M. Kuchling2003-04-091-4/+1
|
* add a #! line for unix weeniesSkip Montanaro2003-04-081-0/+2
|
* New tests identical to boom and boom2, except using new-style classes.Tim Peters2003-04-081-0/+44
| | | | | | | These never failed in 2.3, and the tests confirm it. They still blow up in the 2.2 branch, despite that all the gc-vs-__del__ fixes from 2.3 have been backported (and this is expected -- 2.2 needs more work than 2.3 needed).
* correct a couple docstring nitsSkip Montanaro2003-04-081-3/+3
|
* s/referrents/referents/g. Gotta love that referrers remains rife with rs.Tim Peters2003-04-081-11/+11
|
* Finished implementing gc.get_referrents(): dealt with error and endTim Peters2003-04-081-1/+25
| | | | cases, wrote docs, added a test.
* Reworked has_finalizer() to use the new _PyObject_Lookup() insteadTim Peters2003-04-071-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | of PyObject_HasAttr(); the former promises never to execute arbitrary Python code. Undid many of the changes recently made to worm around the worst consequences of that PyObject_HasAttr() could execute arbitrary Python code. Compatibility is hard to discuss, because the dangerous cases are so perverse, and much of this appears to rely on implementation accidents. To start with, using hasattr() to check for __del__ wasn't only dangerous, in some cases it was wrong: if an instance of an old- style class didn't have "__del__" in its instance dict or in any base class dict, but a getattr hook said __del__ existed, then hasattr() said "yes, this object has a __del__". But instance_dealloc() ignores the possibility of getattr hooks when looking for a __del__, so while object.__del__ succeeds, no __del__ method is called when the object is deleted. gc was therefore incorrect in believing that the object had a finalizer. The new method doesn't suffer that problem (like instance_dealloc(), _PyObject_Lookup() doesn't believe __del__ exists in that case), but does suffer a somewhat opposite-- and even more obscure --oddity: if an instance of an old-style class doesn't have "__del__" in its instance dict, and a base class does have "__del__" in its dict, and the first base class with a "__del__" associates it with a descriptor (an object with a __get__ method), *and* if that descriptor raises an exception when __get__ is called, then (a) the current method believes the instance does have a __del__, but (b) hasattr() does not believe the instance has a __del__. While these disagree, I believe the new method is "more correct": because the descriptor *will* be called when the object is destructed, it can execute arbitrary Python code at the time the object is destructed, and that's really what gc means by "has a finalizer": not specifically a __del__ method, but more generally the possibility of executing arbitrary Python code at object destruction time. Code in a descriptor's __get__() executed at destruction time can be just as problematic as code in a __del__() executed then. So I believe the new method is better on all counts. Bugfix candidate, but it's unclear to me how all this differs in the 2.2 branch (e.g., new-style and old-style classes already took different gc paths in 2.3 before this last round of patches, but don't in the 2.2 branch).
* SF bug #699934: Obscure error messageRaymond Hettinger2003-04-061-3/+2
| | | | | mwh pointed out that the error message did not make sense if obtained by rearranging the bases.
* SF patch #701494: more apply removalsRaymond Hettinger2003-04-0622-2471/+2456
|
* Reworked move_finalizer_reachable() to create two distinct lists:Tim Peters2003-04-061-4/+32
| | | | | | | | | externally unreachable objects with finalizers, and externally unreachable objects without finalizers reachable from such objects. This allows us to call has_finalizer() at most once per object, and so limit the pain of nasty getattr hooks. This fixes the failing "boom 2" example Jeremy posted (a non-printing variant of which is now part of test_gc), via never triggering the nasty part of its __getattr__ method.
* test_boom: More comments. Also check that len(gc.garbage) doesn'tTim Peters2003-04-051-4/+9
| | | | | change (it would be another kind of bug if the trash cycle weren't reclaimed).
* SF bug #715145: unittest.py still uses != in failUnlessEqualRaymond Hettinger2003-04-041-2/+2
|
* Add Tim's gc boom test to the test suite.Jeremy Hylton2003-04-041-0/+19
|
* Revert Patch #670715: iconv support.Martin v. Löwis2003-04-034-142/+0
|
* Change formatchar(), so that u"%c" % 0xffffffff now raisesWalter Dörwald2003-04-021-1/+1
| | | | | an OverflowError instead of a TypeError to be consistent with "%c" % 256. See SF patch #710127.
* Fix a commentBarry Warsaw2003-04-021-1/+1
|
* Sigh... The get() and set() commands are not declared in the aete forJack Jansen2003-04-011-9/+18
| | | | | | the Standard_Suite, but various other suites do expect it (the Finder implements get() without declaring it itself). It is probably another case of OSA magic. Adding them to the global base class.
* Regenerated with property names with _Prop_ prepended.Jack Jansen2003-04-0153-2860/+1697
|
* Properties (like enums) are not in the global namespace but only validJack Jansen2003-04-011-23/+23
| | | | | | | | | within a certain context. Give them an _Prop_ prefix, so they don't accidentally obscure an element from another suite (as happened with the Finder). Comparisons I'm not sure about, so I left them as global names. Also got rid of the lists if declarations, they serve no useful purpose.
* Turned the suite compiler into an object.Jack Jansen2003-04-011-254/+258
|
* - All messages are now dependent on the --verbose option.Jack Jansen2003-04-011-47/+85
| | | | | - Added a --dump option that doesn't generate the module but dumps the pretty-printed aete resource(s) on stdout.
* Remove duplicate test.Walter Dörwald2003-03-311-2/+2
|
* Fix PyString_Format() so that '%c' % u'a' returns u'a'Walter Dörwald2003-03-313-0/+8
| | | | | | | | instead of raising a TypeError. (From SF patch #710127) Add tests to verify this is fixed. Add various tests for '%c' % int.
* Subclasses of ObjectSpecifier can now be packed and unpacked. This allowsJack Jansen2003-03-311-3/+20
| | | | | | you to say something like "talker.count(want=Address_Book.people)" in stead of having to manually create the aetypes.Type(Address_Book.people.want) OSA type.
* In TalkTo.send(), check that we have access to the window manager,Jack Jansen2003-03-311-1/+13
| | | | | and initialize the event loop (if not done previously) to work around a bug (IMHO) in MacOSX 10.2.
* Regenerated again, now clases are sorted by code, and with synonyms afterJack Jansen2003-03-3029-2046/+8742
| | | | the primary name.
* Classes have to be sorted by code, not name, and synonyms have toJack Jansen2003-03-301-2/+19
| | | | | | | be sorted after the main name, otherwise filling of properties and elements messes up. Sorting is always more difficult than expected:-)
* Bump to version 2.5.1Barry Warsaw2003-03-301-1/+1
|
* test_whitespace_eater_unicode_2(): Test case for SF bug #710498.Barry Warsaw2003-03-301-0/+9
|
* __unicode__(): Fix the logic for calculating whether to add aBarry Warsaw2003-03-301-3/+3
| | | | | separating space or not between encoded chunks. Closes SF bug #710498.
* SF patch #706338, Fix a few broken links in pydoc by Greg ChapmanNeal Norwitz2003-03-301-4/+4
|
* Patch #712124: Remove obsolete comment.Martin v. Löwis2003-03-301-1/+0
|
* Support '' as the argument for the setlocale emulation. Fixes #678259.Martin v. Löwis2003-03-301-1/+1
|
* Patch #545300: Support marked sections.Martin v. Löwis2003-03-303-16/+104
|
* The socket module now always uses the _socketobject wrapper class, even onSkip Montanaro2003-03-302-5/+33
| | | | | | | | | platforms which have dup(2). The makefile() method is built directly on top of the socket without duplicating the file descriptor, allowing timeouts to work properly. Includes a new test case (urllibnet) which requires the network resource. Closes bug 707074.
* Moved gensuitemodule from Mac/scripts to Lib/plat-mac. DocumentationJack Jansen2003-03-291-0/+1132
| | | | remains to be done.
* Move Mac/Windows specific expected skips from each platform listNeal Norwitz2003-03-291-49/+8
| | | | | to the ExpectedSkips class. Add test_scriptpackages to Mac only list. Add test_unicode_file to Windows only list.
* Patch #707701: Expect '??' in event fields. Fixes #698517.Martin v. Löwis2003-03-291-16/+32
| | | | Will backport to 2.2.
* Regenerated with the new way to get terminology (through AppleEvents),Jack Jansen2003-03-2927-2692/+1571
| | | | | which sometimes seems to result in different terminology. It does seem to be mostly compatible, though.
* On OSX the finder will return from an open() event before the applicationJack Jansen2003-03-281-0/+12
| | | | | has actually entered its event loop. As a stopgap, allow for a 10 second grace period.
* Sigh: didn't catch all lists that needed to be sorted. Regenerated again.Jack Jansen2003-03-2829-2508/+2508
|
* make nt altsep forward slash - closes bug 709428Skip Montanaro2003-03-281-1/+1
| | | | backport candidate
* Regenerated (from resource files) with sorting version of gensuitemodule.Jack Jansen2003-03-2829-3052/+3048
| | | | | | This is a first step towards regenerating the modules with newer, MacOSX, versions of these programs, and using the programmatic interface to get at the terminology in stead of poking in resource files.
* Minimal test suite of the generated packages in plat-mac/lib-scriptpackages.Jack Jansen2003-03-281-0/+49
| | | | | At the moment does little more than testing that the modules import correctly and some classes can be instantiated.
* Hide private names beginning with _ (but don't hide __special__ names).Ka-Ping Yee2003-03-281-54/+77
| | | | | | Clean up section headings; make the bars on the left less fat. Adjust the display of properties slightly. Don't show stuff inherited from the base 'object' type.
* Make module lookup a little more robust (certain kinds of fiddling toKa-Ping Yee2003-03-281-2/+2
| | | | sys.modules previously produced an exception).