summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Fix warning detected by VC++ on assignment of Py_UNICODE to char.Guido van Rossum2000-05-031-1/+1
|
* Vladimir Marangozov's long-awaited malloc restructuring.Guido van Rossum2000-05-0373-390/+641
| | | | | | | | | | For more comments, read the patches@python.org archives. For documentation read the comments in mymalloc.h and objimpl.h. (This is not exactly what Vladimir posted to the patches list; I've made a few changes, and Vladimir sent me a fix in private email for a problem that only occurs in debug mode. I'm also holding back on his change to main.c, which seems unnecessary to me.)
* Remove all references to stdwin.Guido van Rossum2000-05-031-21/+1
|
* >>Boing!<<Guido van Rossum2000-05-031-2664/+0
| | | | Finally, this long-obsolete module bites the dust.
* Vladimir Marangozov:Guido van Rossum2000-05-031-5/+5
| | | | | Change Py_Malloc/Realloc/Free calls to PyMem_Malloc/Realloc/Free + PyErr_Nomemory on error check. Py_Malloc c.s. are obsolete.
* A bit of cleanup:Guido van Rossum2000-05-031-34/+5
| | | | | | | | | - When 'import exceptions' fails, don't suggest to use -v to print the traceback; this doesn't actually work. - Remove comment about fallback to string exceptions. - Remove a PyErr_Occurred() check after all is said and done that can never trigger. - Remove static function newstdexception() which is no longer called.
* Someone found the examples of poor practice on socket addresses!Fred Drake2000-05-031-3/+3
| | | | Spotted by Greg Kochanski <gpk@bell-labs.com>.
* Brian Hooper <brian_takashi@hotmail.com>:Fred Drake2000-05-032-0/+60
| | | | | | | Added 'u' and 'u#' tags for PyArg_ParseTuple - these turn a PyUnicodeObject argument into a Py_UNICODE * buffer, or a Py_UNICODE * buffer plus a length with the '#'. Also added an analog to 'U' for Py_BuildValue.
* Clarify status of connection of a new instance; it *is* connected ifFred Drake2000-05-031-3/+5
| | | | | you pass server information to the constructor. Error noted by Pedro Diaz Jimenez <diazjimenez@ctv.es>.
* Mark Hammond withdraws his fix -- the size includes the trailing 0 soGuido van Rossum2000-05-031-7/+2
| | | | a size of 0 *is* illegal.
* Mark Hammond:Guido van Rossum2000-05-031-2/+7
| | | | Fixes the MBCS codec to work correctly with zero length strings.
* Moved to the Compat folder (in case anyone still wants to try MPW building), ↵Jack Jansen2000-05-031-1/+0
| | | | it hasn't been used for years.
* Removed, the core-python getmtime works fine with GUSI2.Jack Jansen2000-05-031-57/+0
|
* Mark Hammond to the rescue:Guido van Rossum2000-05-031-3/+4
| | | | | | | | | | | | Checkin 2.131 of posixmodule.c changed os.stat on Windows, so that "/bin/" type notation (trailing backslash) would work on Windows to be consistent with Unix. However, the patch broke the simple case of: os.stat("\\") This did work in 1.5.2, and obviously should! This patch addresses this, and restores the correct behaviour.
* patches from Mark HammondJeremy Hylton2000-05-028-28/+116
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Attached is a set of diffs for the .py compiler that adds support for the new extended call syntax. compiler/ast.py: CallFunc node gets 2 new children to support extended call syntax - "star_args" (for "*args") and "dstar_args" (for "**args") compiler/pyassem.py It appear that self.lnotab is supposed to be responsible for tracking line numbers, but self.firstlineno was still hanging around. Removed self.firstlineno completely. NOTE - I didnt actually test that the generated code has the correct line numbers!! Stack depth tracking appeared a little broken - the checks never made it beyond the "self.patterns" check - thus, the custom methods were never called! Fixed this. (XXX Jeremy notes: I think this code is still broken because it doesn't track stack effects across block bounaries.) Added support for the new extended call syntax opcodes for depth calculations. compiler/pycodegen.py Added support for the new extended call syntax opcodes. compiler/transformer.py Added support for the new extended call syntax.
* patches from Mark HammondJeremy Hylton2000-05-021-1/+4
| | | | | | | | | compile.py: On Windows, use 'nul' instead of '/dev/null'. test.py: Use double-quotes for the command-line, as Windows doesnt recognise singles.
generated by cgit v0.12 at 2024-11-17 03:46:29 (GMT)