summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Added new BoundedSemaphore class. Closes bug 452836.Skip Montanaro2001-08-201-0/+15
|
* Silence warnings during test_osJeremy Hylton2001-08-201-0/+5
|
* Split "Extending & Embedding" into separate files, one per chapter.Fred Drake2001-08-207-3158/+3160
|
* It will always be a string, because it is created just before this call.Jeremy Hylton2001-08-201-1/+1
|
* Added documentation for BoundedSemaphore(), contributed by Skip Montanaro.Fred Drake2001-08-201-2/+40
| | | | This closes SF patch #452836.
* Document PyTuple_GET_SIZE(), removing confusing sentence from PyDict_Copy()Fred Drake2001-08-201-2/+7
| | | | | | description. This fixes SF bug #453111.
* Oops, these compatibility modules were missing. Which went unnoticed because ↵Jack Jansen2001-08-208-0/+8
| | | | their companions had been put in the wrong place.
* Various toolbox modules were generated in lib-dynload accidentallyJack Jansen2001-08-201-3/+3
| | | | in stead of in Carbon. Fixed.
* Clean up some argument profiles, enrich the docstring.Eric S. Raymond2001-08-202-32/+41
|
* Oops, this file shouldn't have been removed.Jack Jansen2001-08-201-0/+1
|
* The destination folder is now :Lib:lib-dynloadJack Jansen2001-08-191-0/+0
|
* PATCHLEVEL is outdated, use PY_VERSION.Jack Jansen2001-08-191-1/+1
|
* Step 1 in packaging the toolbox modules and making MacPython moreJack Jansen2001-08-191-1/+0
| | | | | | | like normal Python. toolbox modules are now in the Carbon package in :Mac:Lib, with a workaround flat namespace in :Mac:Lib:lib-compat. Other dynamic modules are in :Lib:lib-dynload. :Mac:Lib:lib-toolbox and :Mac:Plugins are gone.
* Dynamic modules are now put in :Lib:lib-dynload by default. For the toolbox ↵Jack Jansen2001-08-191-37/+41
| | | | modules this is overridden to put them in :Mac:Lib:Carbon.
* Compatibility modules. lib-compat is on the default sys.path for MacPython ↵Jack Jansen2001-08-1937-0/+37
| | | | 2.2, and each of these modules imports * from its namesake in the Carbon package.
* Moved to either :Mac:Lib (WASTEconst and files that weren't generated) or to ↵Jack Jansen2001-08-1927-6475/+0
| | | | the Carbon package.
* The modules with toolbox constants.Jack Jansen2001-08-1922-0/+4998
|
* Carbon is now a package encapsulating all the toolbox modules. Carbon is notJack Jansen2001-08-191-0/+0
| | | | | | the best of names right now (because QuickTime, for instance, is part of its own framekwork in OSX terminology, and because all these modules also work on pre-Carbon MacOS) but in a year or so it will be:-).
* Moved here form lib-toolbox, for lack of a better place to go.Jack Jansen2001-08-191-0/+95
|
* Moved here from lib-toolbox, where they should never have been in the first ↵Jack Jansen2001-08-194-0/+1382
| | | | place (all the other stuff there wa generated with bgen).
* Step 1 in packaging the toolbox modules and making MacPython moreJack Jansen2001-08-191-2/+2
| | | | | | | like normal Python. toolbox modules are now in the Carbon package in :Mac:Lib, with a workaround flat namespace in :Mac:Lib:lib-compat. Other dynamic modules are in :Lib:lib-dynload. :Mac:Lib:lib-toolbox and :Mac:Plugins are gone.
* Temporarily disabled the import hook. It breaks with the package-basedJack Jansen2001-08-191-1/+2
| | | | Carbon and its workaround.
* Removed NEXT-NOTES, the NeXT is no longer supported.Jack Jansen2001-08-192-82/+0
|
* Removed NeXT notes (replacing them with a line saying NeXT is noJack Jansen2001-08-191-17/+23
| | | | longer supported) and updated MacOSX notes.
* Got rid of all the plugin xml files: they are generated, andJack Jansen2001-08-19135-63926/+0
| | | | | | | | | they were only in the repository for people building MacPython from CVS (the .cmp project files are in a MacPython source distribution). The process to regenerate them is now easier (and documented!) so these shouldn't be needed anymore. And eventually they should all be built by setup.py anyway.
* of course I muffed it separating the notes code from the initial_valueSkip Montanaro2001-08-191-4/+4
| | | | code. grrr...
* Avoid total dependency on the new module. This addresses the problemGuido van Rossum2001-08-191-1/+7
| | | | reported by Greg Ball on python-dev.
* add debug calls to self._note for the Semaphore class. This closes bugSkip Montanaro2001-08-191-0/+9
| | | | | 443614. I will submit a new feature request and patch to threading.py and libthreading.tex to address the bounded semaphore issue.
* Improve Windows time.clock() blurb; was missing return type and unit.Tim Peters2001-08-191-4/+4
|
* Windows fiddling for 2.2a2: bump build number; update copyright andTim Peters2001-08-194-8/+10
| | | | | company info in resource files; change installer strings to match. This belongs in the release branch too, of course.
* SF patch #452239 by Gordon McMillan, to fix SF bug #451547.Guido van Rossum2001-08-181-1/+25
| | | | | | | | | | This patch attempts to do to cPickle what Guido did for pickle.py v 1.50. That is: save_global tries importing the module, and fetching the name from the module. If that fails, or the returned object is not the same one we started with, it raises a PicklingError. (All this so pickling a lambda will fail at save time, rather than load time).
* Add dependencies for Python/thread.c on all of the header files thatGuido van Rossum2001-08-181-0/+4
| | | | | | | | it may depend on. It's really annoying that thread.o doesn't get rebuilt when the .h file is changed! :-) The dependency is on *all* the Python/thread_*.h files -- that should be sufficient and rarely cause unneeded recompilations.
* Inspired by Greg Stein's proposed simplification of the _closesocketGuido van Rossum2001-08-181-5/+1
| | | | | class, I came up with an even simpler solution: raise the error in __getattr__().
* Expose the CO_xxx flags via the "new" module (re-solving a problem "theTim Peters2001-08-183-13/+48
| | | | | | | | | | right way"). Fiddle __future__.py to use them. Jeremy's pyassem.py may also want to use them (by-hand duplication of magic numbers is brittle), but leaving that to his judgment. Beef up __future__'s test to verify the exported feature names appear correct.
* added warnings about security risk of using tmpnam and tempnamSkip Montanaro2001-08-181-0/+10
|
* Fix SF bug #443600:Guido van Rossum2001-08-181-15/+46
| | | | | | | | Change to get/set/del slice operations so that if the object doesn't support slicing, *or* if either of the slice arguments is not an int or long, we construct a slice object and call the get/set/del item operation instead. This makes it possible to design classes that support slice arguments of non-integral types.
* Framework code for compilerlike scripts.Eric S. Raymond2001-08-182-0/+241
|
* Resolve patch #449367.Greg Stein2001-08-181-15/+26
| | | | | | | | | | | For the HTTPS class (when available), ensure that the x509 certificate data gets passed through to the HTTPSConnection class. Create a new HTTPS.__init__ to do this, and refactor the HTTP.__init__ into a new _setup method for both init's to call. Note: this is solved differently from the patch, which advocated a new **x509 parameter on the base HTTPConnection class. But that would open HTTPConnection to arbitrary (ignored) parameters, so was not as desirable.
* Add some fairly important file extensions: bmp css doc mid midi mp2 mp3 xls.Ka-Ping Yee2001-08-181-0/+8
| | | | Entries taken from the standard Debian mime.types file.
* Initial check-in of cgitb.Ka-Ping Yee2001-08-181-0/+182
| | | | A few enhancements are pending, but this should work reliably.
* When the socket is closed, don't just assign 0 to self._sock.Guido van Rossum2001-08-181-8/+18
| | | | | This breaks software that excepts a socket.error but not an AttributeError.
* Add a little introductory text.Jeremy Hylton2001-08-181-15/+93
| | | | | | | | | Change several sections to subsections (part of the manual -> howto transformation). Flesh out discussion of assignment nodes (and delete statements). Add an example of manipulating AST objects at a >>> prompt
* Generate correct reprs for Mul, Add, etc.Jeremy Hylton2001-08-184-40/+20
|
* Track removal of doc string from Module().nodes[0]Jeremy Hylton2001-08-182-14/+4
|
* Add Yield() nodeJeremy Hylton2001-08-182-0/+24
|
* Remove the horrid generators hack from doctest.py. This relies on aTim Peters2001-08-181-75/+37
| | | | | | | | | | | | | | | | | somewhat less horrid hack <wink>: if a module does from __future__ import X then the module dict D is left in a state such that (viewing X as a string) D[X] is getattr(__future__, X) So by examining D for all the names of future features, and making that test for each, we can make a darned good guess as to which future-features were imported by the module. The appropriate flags are then sucked out of the __future__ module, and passed on to compile()'s new optional arguments (PEP 264). Also gave doctest a meaningful __all__, removed the history of changes (CVS serves that purpose now), and removed the __version__ vrbl (similarly; before CVS, it was a reasonable clue, but not anymore).
* Add Yield() statement handlerJeremy Hylton2001-08-182-2/+22
| | | | Fix Module() handler to avoid including the doc string in the AST
* Fix for bug [#452230] future division isn't propagated.Tim Peters2001-08-172-1/+9
| | | | | | | builtin_eval wasn't merging in the compiler flags from the current frame; I suppose we never noticed this before because future division is the first future-feature that can affect expressions (nested_scopes and generators had only statement-level effects).
* The OSX framework Headers symlink pointed the wrong way. Fixed.Jack Jansen2001-08-171-1/+1
| | | | Bill Fancher found this one.
* A fiddled version of the rest of Michael Hudson's SF patchTim Peters2001-08-174-47/+157
| | | | | #449043 supporting __future__ in simulated shells which implements PEP 264.
generated by cgit v0.12 at 2025-03-06 20:51:28 (GMT)