summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Enums we cannot find are set to None, and enumsubst understands this (no ↵Jack Jansen2000-08-202-6/+10
| | | | substitution done). This is need for what I think are bugs in the Finder aete resources (some events use unknown enums).
* Fixed event inheritance code (which didn't work at all).Jack Jansen2000-08-201-117/+239
| | | | Do two passes over the suites so we can figure out dependencies for enums and such. The manual method was getting too cumbersome for Finder suites.
* Finder suite.Jack Jansen2000-08-2012-0/+3801
|
* Regenerated with fixes to gensuitemodule.Jack Jansen2000-08-206-44/+44
|
* Fix the bug Sjoerd Mullender discovered, where find_from_args() wasn'tThomas Wouters2000-08-201-1/+3
| | | | | | | | | | trying hard enough to find out what the arguments to an import were. There is no test-case for this bug, yet, but this is what it looked like: from encodings import cp1006, cp1026 ImportError: cannot import name cp1026 '__import__' was called with only the first name in the 'arguments' list.
* Changed the popen2.py _test function to use the "more" cmd whenTim Peters2000-08-201-5/+10
| | | | | | | | os.name == "nt". This makes test_popen2 pass under Win98SE. HOWEVER, the Win98 "more" invents a leading newline out of thin air, and I'm not sure that the other Windows flavors of "more" also do that. So, somebody please try under other Windows flavors!
* David Goodger's new getopt test module (thanks, David!).Tim Peters2000-08-202-0/+108
| | | | | https://sourceforge.net/patch/?func=detailpatch&patch_id=101110&group_id=5470 Accepted as-is, except for purging an "import *".
* Disallow "import mod.submod as m", because the result is ambiguous. Does itThomas Wouters2000-08-192-2/+8
| | | | | | | | | | load mod.submod as m, or mod as m ? Both can be achieved differently, and unambiguously. Also attempt to document this restriction (editor appreciated!) Note that this is an artificial check during compile, because incorporating this in the grammar is hard, and then adjusting the compiler to do the right thing with the right nodes is harder.
* Add entry for Cookie module.Fred Drake2000-08-192-0/+2
|
* Make it format.Fred Drake2000-08-191-166/+177
| | | | | | Adjust markup for hyperlinking to the relevant RFCs. Give it a little organization. Minor nits.
* Adding tests of the "attrs" optional argument, and of the js_outputMoshe Zadka2000-08-192-0/+20
| | | | functionality.
* Use METH_VARARGS constant in example module.Andrew M. Kuchling2000-08-191-6/+6
| | | | Fix comment typo
* Test case for Cookie.pyAndrew M. Kuchling2000-08-192-0/+33
|
* Initial revision. Markup unchecked.Moshe Zadka2000-08-191-0/+232
|
* Added Tim O'Malley's Cookie.py module (master version atAndrew M. Kuchling2000-08-191-0/+718
| | | | | http://www.timo-tasi.org/python/Cookie.py) This is revision 2.26 according to Tim's RCS history.
* com_error(): Quiet gcc -Wall warning.Barry Warsaw2000-08-181-1/+0
|
* Remove a couple of warnings turned up by "gcc -Wall".Fred Drake2000-08-182-3/+4
|
* PyUnicode_AsUTF8String(): /F picks up what I missed: the local varBarry Warsaw2000-08-181-2/+0
| | | | `str' is no longer necessary. Gotta turn on -Wall!
* Do not set a MemoryError exception over another MemoryError exception,Vladimir Marangozov2000-08-181-0/+4
| | | | thus preserving the first one that has been raised.
* Better conformance to the Python Style Guide: use spaces around operators.Fred Drake2000-08-181-32/+33
|
* When a KeyboardInterrupt is caught, just use the "raise" syntax toFred Drake2000-08-181-2/+2
| | | | re-raise it instead of re-raising it "manually" the ugly way.
* Revise to use atexit instead of monkeying with sys.exitfunc directly.Fred Drake2000-08-181-9/+2
|
* Convert some old-style string exceptions to class exceptions.Fred Drake2000-08-188-10/+20
|
* Convert some old-style string exceptions to class exceptions.Fred Drake2000-08-182-2/+4
|
* Removed references to Py_FPROTO.Sjoerd Mullender2000-08-181-2/+2
|
* PyUnicode_AsUTF8String(): Don't need to explicitly incref str sinceBarry Warsaw2000-08-181-7/+3
| | | | | PyUnicode_EncodeUTF8() already returns the created object with the proper reference count. This fixes an Insure reported memory leak.
* ANSI-fy function headers. Not much more can be done since I don'tBarry Warsaw2000-08-181-249/+82
| | | | have access to Purify anymore.
* lad_dealloc(): if xp->x_fd == -1, it means the descriptor's alreadyBarry Warsaw2000-08-181-1/+3
| | | | been closed. Don't try to reclose it. Found by Insure.
* pattern_findall(): Plug small memory leak discovered by Insure.Barry Warsaw2000-08-181-3/+3
| | | | | PyList_Append() always incref's the inserted item. Be sure to decref it regardless of whether the append succeeds or fails.
* init_locale(): This file defines the _locale module, so theBarry Warsaw2000-08-181-1/+1
| | | | Py_FatalError() should reflect that.
* SyntaxError__classinit__(): Slight reorg for simplicity.Barry Warsaw2000-08-181-4/+4
|
* PyParser_ParseString(): When the err_ret structure is initialized, theBarry Warsaw2000-08-181-0/+2
| | | | | | fields token and expected must also be initialized, otherwise the tests in parsetok() can generate uninitialized memory read errors. This quiets an Insure warning.
* comples_from_string(): Move s_buffer[] up to the top-level functionBarry Warsaw2000-08-181-2/+1
| | | | | | scope. Previously, s_buffer[] was defined inside the PyUnicode_Check() scope, but referred to in the outer scope via assignment to s. This quiets an Insure portability warning.
* make_pair(): When comparing the pointers, they must be cast to integerBarry Warsaw2000-08-181-2/+6
| | | | | | types (i.e. Py_uintptr_t, our spelling of C9X's uintptr_t). ANSI specifies that pointer compares other than == and != to non-related structures are undefined. This quiets an Insure portability warning.
* PyFloat_FromString(): Move s_buffer[] up to the top-level functionBarry Warsaw2000-08-181-2/+1
| | | | | | scope. Previously, s_buffer[] was defined inside the PyUnicode_Check() scope, but referred to in the outer scope via assignment to s. This quiets an Insure portability warning.
* PyInstance_DoBinOp(): When comparing the pointers, they must be castBarry Warsaw2000-08-181-1/+4
| | | | | | | to integer types (i.e. Py_uintptr_t, our spelling of C9X's uintptr_t). ANSI specifies that pointer compares other than == and != to non-related structures are undefined. This quiets an Insure portability warning.
* Added test for uintptr_t, the C9X acceptable way to spell "type toBarry Warsaw2000-08-183-212/+291
| | | | | | | which I can cast void* to and back again without losing information". In pyport.h, we typedef Py_uintptr_t to mean this thing, which if the platform supports, will be uintptr_t (otherwise, other accomodations are made).
* Added #undef HAVE_UINTPTR_T for autoconf's delight.Barry Warsaw2000-08-181-0/+3
|
* Moved LONG_LONG #define from here to pyport.h.Barry Warsaw2000-08-181-3/+0
|
* Moved LONG_LONG #define from longobject.h to here, since it's neededBarry Warsaw2000-08-181-0/+43
| | | | | | | | | | by the following. typedef in a portable way the Python name for the C9X uintptr_t type. This latter is the most portable way to spell an integral type to which a void* can be cast to and back again without losing information. Parallel checkin hacks configure to check if the platform/compiler supports the C9X name.
* As pointed out by Denis S. Otkidach <den@analyt.chem.msu.ru>, xrange()Fred Drake2000-08-181-14/+15
| | | | | | | | returns an xrange object, not a range object, despite the name of the source file they're implemented in. In the list of comparison operators, list != before <>, since <> is described as obsolescent.
* Adjust the way __getslice__() is marked as deprecated; this will alsoFred Drake2000-08-181-2/+4
| | | | stand out more.
* Fix a markup error that caused formatting to fail.Fred Drake2000-08-181-16/+17
| | | | Lots of minor markup adjustments as well.
* Mention the new 'import X as Y' syntaxAndrew M. Kuchling2000-08-171-0/+4
|
* Document the returns_unicode attributeAndrew M. Kuchling2000-08-171-4/+11
|
* Update to reflect the recent Grammar changes.Fred Drake2000-08-171-40/+42
|
* Apply SF patch #101135, adding 'import module as m' and 'from module importThomas Wouters2000-08-1712-743/+895
| | | | | | | | name as n'. By doing some twists and turns, "as" is not a reserved word. There is a slight change in semantics for 'from module import name' (it will now honour the 'global' keyword) but only in cases that are explicitly undocumented.
* Apply SF patch #101029: call __getitem__ with a proper slice object if thereThomas Wouters2000-08-175-18/+435
| | | | | | | | is no __getslice__ available. Also does the same for C extension types. Includes rudimentary documentation (it could use a cross reference to the section on slice objects, I couldn't figure out how to do that) and a test suite for all Python __hooks__ I could think of, including the new behaviour.
* Remove an item that's been done.Fred Drake2000-08-171-2/+0
|
* A little more text, and some really minor cleanups.Fred Drake2000-08-171-3/+10
|
generated by cgit v0.12 at 2025-01-15 14:47:48 (GMT)