summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* USE_GUSI2 should be defined, not USE_GUSI1.Jack Jansen2000-05-091-2/+2
|
* Selecting the macfsn option didn't work, fixed.Jack Jansen2000-05-095-7/+6
| | | | | Fixed the help strings. Swapped the macfsn and help button numbers.
* Import this to replace open() by an extended version that usesJack Jansen2000-05-091-0/+66
| | | | | Internet Config to set creator/type based on the extension. Donated by Oliver Steele.
* Added comment about the MSVC-specific kludge.Greg Ward2000-05-091-0/+10
|
* Deleted some modules that are no longer supported.Guido van Rossum2000-05-083-451/+0
|
* The usual...Guido van Rossum2000-05-0856-667/+5051
|
* Deleted the stdwin-based test() function.Guido van Rossum2000-05-081-66/+0
|
* Deleting all stdwin library modules.Guido van Rossum2000-05-0834-3829/+0
|
* if the GzipFile constructor fails, the __del__ method is stillJeremy Hylton2000-05-081-3/+7
| | | | called. catch the resulting AttributeError and exit cleanly.
* Trent Mick:Guido van Rossum2000-05-081-4/+4
| | | | | | | | | | | | | Fix overflow bug in ldexp(x, exp). The 'exp' argument maps to a C int for the math library call [double ldexp(double, int)], however the 'd' PyArg_ParseTuple formatter was used to yield a double, which was subsequently cast to an int. This could overflow. [GvR: mysteriously, on Solaris 2.7, ldexp(1, 2147483647) returns Inf while ldexp(1, 2147483646) raises OverflowError; this seems a bug in the math library (it also takes a real long time to compute the Inf outcome). Does this point to a bug in the CHECK() macro? It should have discovered that the result was outside the HUGE_VAL range.]
* Trent Mick:Guido van Rossum2000-05-081-3/+17
| | | | | | The following modules are specifically excluded in the Win64 build: audioop, binascii, imageop, rgbimg. They are advertised as heavily 32-bit dependent. [They should probably be fixed! --GvR]
* Trent Mick:Guido van Rossum2000-05-081-23/+57
| | | | | | | | | | | | | | | | | | | | Changes to PC\config.[hc] for Win64. MSVC defines _WINxx to differentiate the various windows platforms. Python's MS_WINxx are keyed off of these. Note that _WIN32 (and hence MS_WIN32 in Python) are defined on Win32 *and* on Win64. This is for compatibility reasons. The idea is that the common case is that code specific to Win32 will also work on Win64 rather than being specific to Win32 (i.e. there is more the same than different in WIn32 and Win64). The following modules are specifically excluded in the Win64 build: audioop, binascii, imageop, rgbimg. They are advertised as heavily 32-bit dependent. [They should probably be fixed! --GvR] The patch to config.h looks big but it really is not. These are the effective changes: - MS_WINxx are keyed off _WINxx - SIZEOF_VOID_P is set to 8 for Win64 - COMPILER string is changed appropriately for Win64
* Trent Mick:Guido van Rossum2000-05-081-5/+9
| | | | | | | | | | | | | | | | Fix the string methods that implement slice-like semantics with optional args (count, find, endswith, etc.) to properly handle indeces outside [INT_MIN, INT_MAX]. Previously the "i" formatter for PyArg_ParseTuple was used to get the indices. These could overflow. This patch changes the string methods to use the "O&" formatter with the slice_index() function from ceval.c which is used to do the same job for Python code slices (e.g. 'abcabcabc'[0:1000000000L]). slice_index() is renamed _PyEval_SliceIndex() and is now exported. As well, the return values for success/fail were changed to make slice_index directly usable as required by the "O&" formatter. [GvR: shouldn't a similar patch be applied to unicodeobject.c?]
* Trent Mick:Guido van Rossum2000-05-081-11/+14
| | | | | Change static slice_index() to extern _PyEval_SliceIndex() (with different return value interpretation: 0 for failure, 1 for success).
* Trent Mick:Guido van Rossum2000-05-081-0/+3
| | | | Add declaration of PyEval_SliceIndex().
* Trent Mick:Guido van Rossum2000-05-081-14/+44
| | | | | | | | | | Changes the 'b', 'h', and 'i' formatters in PyArg_ParseTuple to raise an Overflow exception if they overflow (previously they just silently overflowed). Changes by Guido: always accept values [0..255] (in addition to [CHAR_MIN..CHAR_MAX]) for 'b' format; changed some spaces into tabs in other code.
* Andy Dustman: add GNU pth user-space thread support.Guido van Rossum2000-05-087-155/+551
|
* Updated for the 1.6a2 distribution: added a note about the special Tcl/Tk ↵Jack Jansen2000-05-071-18/+23
| | | | distribution, about Quicktime Exschange and a few minor updates.
* Changed for the new preference resource version.Jack Jansen2000-05-071-4/+6
|
* The applets need more memory nowadays, it seems (because of navservices, ↵Jack Jansen2000-05-073-0/+0
| | | | maybe?). Give them 4M, that should be okay for a while.
* Installer for 1.6a2. This is not the optimal location for the VCT file, it ↵Jack Jansen2000-05-071-0/+0
| | | | should be one level higher, but I can't be bothered fixing that this time around.
* 1.6a2 directive files.Jack Jansen2000-05-072-110/+173
|
* These were never used, removed.Jack Jansen2000-05-072-104/+0
|
* Moved and renamedJack Jansen2000-05-071-0/+0
|
* Don't use 'set_option()' or 'get_option()' method -- direct attribute access,Greg Ward2000-05-072-2/+2
| | | | or getattr/setattr, is all that's needed.
* Got rid of several little-used and not-very-useful methods: 'get_option()',Greg Ward2000-05-071-47/+2
| | | | 'get_options()', 'get_command_option()', 'get_command_options()'.
* Got rid of some little-used and not-very-useful methods: 'get_option()' andGreg Ward2000-05-071-44/+3
| | | | 'get_options()'.
* Tentative MkDistr scripts for 1.6a2.Jack Jansen2000-05-064-25/+151
|
* Updated for 1.6a2.Jack Jansen2000-05-062-201/+70
|
* Put the install folders in (vise), not vise, so the include files aren't ↵Jack Jansen2000-05-061-1/+1
| | | | accidentally picked up by the normal build process.
* We should define both USE_GUSI and USE_GUSI2.Jack Jansen2000-05-062-2/+5
|
* Added the ability to sneak extra flags onto the C compiler command lineGreg Ward2000-05-061-1/+3
| | | | via an 'extra_compile_args' option in the 'build_info' dictionary.
* Toby Dickenson:Guido van Rossum2000-05-061-4/+1
| | | | | | | Fix for problem with freeze when both "-m" and "-s service" options are used. (Blessed by MarkH)
* Adding projects to the repository again, this time in MacBinary form. If you ↵Jack Jansen2000-05-0532-3/+9
| | | | | | | | | | have added the MMPr filetype as "plain binary" in the MacCVS preferences you should revert this before doing this update. Got rid of last references to GUSI1. Upped for current python CVS status. Various minor tweaks, I guess:-)
* Removed string-exception preference, added tabcheck and NavService ↵Jack Jansen2000-05-0510-13/+52
| | | | preference, upped version number.
* Auto-install on import, if NavServices is available. Unless a "no ↵Jack Jansen2000-05-051-0/+1
| | | | navservices" flag is set Python automagically imports this module so code that uses macfs.xxxGetFile will get NavServices dialogs.
* Got rid of PyMem_XDEL.Jack Jansen2000-05-051-7/+7
|
* Got rid of w/MSL in the version string.Jack Jansen2000-05-051-9/+3
|
* Automatically dump distribution folders where I want them, next to the vise ↵Jack Jansen2000-05-052-15/+8
| | | | scripts.
* The methods islower(), isupper(), isspace(), isdigit() and istitle()Guido van Rossum2000-05-051-11/+11
| | | | | | gave bogus results for chars in the range 128-255, because their implementation was using signed characters. Fixed this by using unsigned character pointers (as opposed to using Py_CHARMASK()).
* Add two scenarios by Vladimir Marangozov that show how to use your ownGuido van Rossum2000-05-051-1/+43
| | | | allocator.
* Quick fix by Mark Hammond -- Yakov changed a dprintf call but it wasGuido van Rossum2000-05-051-1/+1
| | | | referencing an undefined variable, so we better change it back.
* Alas, Vladimir's patch was too aggressive, and started causing reallyGuido van Rossum2000-05-051-1/+1
| | | | | | | | weird errors. (E.g. see thread "weird bug in test_winreg" in python-dev.) Since it's actually useful to be able to re-run an individual test after running test.autotest, we keep the unloading code, but only for modules whose full name starts with "test.".
* Fast NonRecursiveMutex support by Yakov Markovitch, markovitch@iso.ru,Guido van Rossum2000-05-041-25/+113
| | | | | | | | | | | | | | | | | | who wrote: Here's the new version of thread_nt.h. More particular, there is a new version of thread lock that uses kernel object (e.g. semaphore) only in case of contention; in other case it simply uses interlocked functions, which are faster by the order of magnitude. It doesn't make much difference without threads present, but as soon as thread machinery initialised and (mostly) the interpreter global lock is on, difference becomes tremendous. I've included a small script, which initialises threads and launches pystone. With original thread_nt.h, Pystone results with initialised threads are twofold worse then w/o threads. With the new version, only 10% worse. I have used this patch for about 6 months (with threaded and non-threaded applications). It works remarkably well (though I'd desperately prefer Python was free-threaded; I hope, it will soon).
* When the UTF-8 conversion to Unicode fails, return an 8-bit stringGuido van Rossum2000-05-041-1/+5
| | | | | | | | | | instead. This seems more robust than returning an Unicode string with some unconverted charcters in it. This still doesn't support getting truly binary data out of Tcl, since we look for the trailing null byte; but the old (pre-Unicode) code did this too, so apparently there's no need. (Plus, I really don't feel like finding out how Tcl deals with this in each version.)
* Mark Hammond should get his act into gear (his words :-). Zero lengthGuido van Rossum2000-05-041-2/+7
| | | | strings _are_ valid!
* Added accessor for kControlListBoxDoubleClickPartJack Jansen2000-05-041-0/+4
|
* Two changes to improve (I hope) Unicode support.Guido van Rossum2000-05-041-2/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. In Tcl 8.2 and later, use Tcl_NewUnicodeObj() when passing a Python Unicode object rather than going through UTF-8. (This function doesn't exist in Tcl 8.1, so there the original UTF-8 code is still used; in Tcl 8.0 there is no support for Unicode.) This assumes that Tcl_UniChar is the same thing as Py_UNICODE; a run-time error is issued if this is not the case. 2. In Tcl 8.1 and later (i.e., whenever Tcl supports Unicode), when a string returned from Tcl contains bytes with the top bit set, we assume it is encoded in UTF-8, and decode it into a Unicode string object. Notes: - Passing Unicode strings to Tcl 8.0 does not do the right thing; this isn't worth fixing. - When passing an 8-bit string to Tcl 8.1 or later that has bytes with the top bit set, Tcl tries to interpret it as UTF-8; it seems to fall back on Latin-1 for non-UTF-8 bytes. I'm not sure what to do about this besides telling the user to disambiguate such strings by converting them to Unicode (forcing the user to be explicit about the encoding). - Obviously it won't be possible to get binary data out of Tk this way. Do we need that ability? How to do it?
* Add useless 'return 1' to prtrace() to shut up VC++.Guido van Rossum2000-05-041-0/+1
|
* Raise ImportError when os.fork does not exist.Guido van Rossum2000-05-041-0/+5
|
generated by cgit v0.12 at 2024-12-02 05:51:26 (GMT)