summaryrefslogtreecommitdiffstats
path: root/Lib
Commit message (Collapse)AuthorAgeFilesLines
* Allow switching of install dir after creation of preferences.Jack Jansen2003-04-161-7/+10
| | | | Changed some message to be clearer when presented by Package Manager.
* Add two dictionaries to htmlentitydefs: name2codepoint mapsWalter Dörwald2003-04-161-254/+270
| | | | | HTML entity names to Unicode codepoints (as integers). codepoint2name is the reverse mapping. From SF patch #722017.
* Test SystemEvents too.Jack Jansen2003-04-151-1/+4
|
* Ouch, it's Carlo Verre, not Verre Carlo.Guido van Rossum2003-04-151-5/+5
|
* Add a few errors tests for range().Walter Dörwald2003-04-151-0/+6
|
* Fix copy & paste error in comment.Walter Dörwald2003-04-151-1/+1
|
* Fix the test so that it works even when /etc/group has two entriesWalter Dörwald2003-04-151-1/+12
| | | | for the same gid.
* Fix the test so that it works even when /etc/passwd has two entriesWalter Dörwald2003-04-151-1/+12
| | | | for the same uid.
* - Use the tarfile module to unpack tarfiles.Jack Jansen2003-04-151-62/+187
| | | | | | | | | - Allow setting the destination install directory. If this is set then it is used for the modules, other items (header files, etc) are not installed, and warnings are printed if the package would have liked to. Unfortunaltey binary installs seem broken due to a tarfile bug (#721871) or my misunderstanding of how tarfile works.
* test_range(): The C code changed to raise TypeError in one of theseTim Peters2003-04-151-1/+1
| | | | cases, but the test still expected ValueError. Repaired that.
* Port test_pwd.py to PyUnit. Check that getpwall() andWalter Dörwald2003-04-154-239/+319
| | | | | | | | | | | | getpwnam()/getpwuid() return consistent data. Change test_grp to check that getgrall() and getgrnam()/getgrgid() return consistent data. Add error checks similar to test_pwd.py. Port test___all__.py to PyUnit. From SF patch #662807.
* The date class is now properly subclassable. (SF bug #720908)Guido van Rossum2003-04-141-0/+6
| | | | | (This is only the tip of the iceberg; the time and datetime classes need the same treatment.)
* Close off the "Verre Carlo hack" as discussed on python-dev.Guido van Rossum2003-04-141-0/+17
|
* - list.insert(i, x) now interprets negative i as it would beGuido van Rossum2003-04-141-0/+5
| | | | | | interpreted by slicing, so negative values count from the end of the list. This was the only place where such an interpretation was not placed on a list index.
* SF patch #720991 by Gary Herron:Guido van Rossum2003-04-144-4/+24
| | | | | | | A small fix for bug #545855 and Greg Chapman's addition of op code SRE_OP_MIN_REPEAT_ONE for eliminating recursion on simple uses of pattern '*?' on a long string.
* Patch #709178: remove -static option from cygwinccompilerJason Tishler2003-04-141-5/+30
| | | | | | | | | | | | | | After some more reflection (and no negative feedback), I am reverting the original patch and applying my version, cygwinccompiler.py-shared.diff, instead. My reasons are the following: 1. support for older toolchains is retained 2. support for new toolchains (i.e., ld -shared) is added The goal of my approach is to avoid breaking older toolchains while adding better support for newer ones.
* Get test working if gzip support is not availableNeal Norwitz2003-04-141-1/+2
|
* Oops, _propdeclarations and friends are needed: gensuitemodule uses themJack Jansen2003-04-1256-12422/+13583
| | | | | | | | | to lookup properties declared in base classes. Looking at it I'm not sure what the official scope if the property codes is, maybe it is only the (OSA) class in which they are used. But giving them global scope hasn't been a problem so far. Regenerated the standard suites, which are now also space-indented.
* NullTranslations.__init__(): Back out of setting the default charsetBarry Warsaw2003-04-111-16/+16
| | | | | | | | | | | | to iso-8859-1. GNUTranslations._parse(): Back out the addition of a test for Project-ID-Version in the metadata. This was deliberately removed in response to SF patch #700839. Also, re-organize the code in _parse() so we parse the metadata header containing the charset parameter before we try to decode any strings using charset.
* Patch by Chad Netzer (with significant change):Guido van Rossum2003-04-111-0/+35
| | | | | | | - range() now works even if the arguments are longs with magnitude larger than sys.maxint, as long as the total length of the sequence fits. E.g., range(2**100, 2**101, 2**100) is the following list: [1267650600228229401496703205376L]. (SF patch #707427.)
* From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.htmlBarry Warsaw2003-04-112-138/+210
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
* SF patch #706707, time.tzset standards compliance update by Stuart BishopNeal Norwitz2003-04-111-58/+41
| | | | Update configure and test to use proper timezone specifications
* Avoid creating one of the TestSuite objects.Fred Drake2003-04-111-2/+1
|
* Fix test_tarfile failure when gzip is not availableNeal Norwitz2003-04-111-1/+2
| | | | | The module would exist, but be empty if already imported. This change ensures we have gzip available.
* Attempt to make all the various string *strip methods the same.Neal Norwitz2003-04-103-40/+40
| | | | | | | | | | | * Doc - add doc for when functions were added * UserString * string object methods * string module functions 'chars' is used for the last parameter everywhere. These changes will be backported, since part of the changes have already been made, but they were inconsistent.
* hoist contents of csv submodule up to the package levelSkip Montanaro2003-04-102-1/+2
|
* Patch #718551: cygwinccompiler.get_versions() patchJason Tishler2003-04-091-3/+3
| | | | | | | | | | The cygwinccompiler.get_versions() function only handles versions numbers of the form "x.y.z". The attached patch enhances get_versions() to handle "x.y" too (i.e., the ".z" is optional). This change causes the unnecessary "--entry _DllMain@12" link option to be suppressed for recent Cygwin and Mingw toolchains. Additionally, it directs recent Mingw toolchains to use gcc instead of dllwrap during linking.
* Add test for MessageBeep()Guido van Rossum2003-04-091-1/+13
|
* 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
|
generated by cgit v0.12 at 2024-12-04 03:25:30 (GMT)