summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Use raw-unicode-escape for the tests that require it.Martin v. Löwis2001-08-172-3/+3
|
* Address SF bug #442813. The sequence getitem wrappers should doGuido van Rossum2001-08-171-8/+50
| | | | | | interpretation of negative indices, since neither the sq_*item slots nor the slot_ wrappers do this. (Slices are a different story, there the size wrapping is done too early.)
* Add test for weak references.Guido van Rossum2001-08-171-3/+33
|
* Add note on type/class unification.Guido van Rossum2001-08-171-0/+6
|
* ceval, PyEval_MergeCompilerFlags: wasn't merging in theTim Peters2001-08-172-6/+5
| | | | | | | | | | | | | | CO_FUTURE_DIVISION flag. Redid this to use Jeremy's PyCF_MASK #define instead, so we dont have to remember to fiddle individual feature names here again. pythonrun.h: Also #define a PyCF_MASK_OBSOLETE mask. This isn't used yet, but will be as part of the PEP 264 implementation (compile() mustn't raise an error just because old code uses a flag name that's become obsolete; a warning may be appropriate, but not an error; so compile() has to know about obsolete flags too, but nobody is going to remember to update compile() with individual obsolete flag names across releases either -- i.e., this is the flip side of PyEval_MergeCompilerFlags's oversight).
* Weak reference support, closing SF bug #451773.Guido van Rossum2001-08-171-21/+51
| | | | | | | | | | | Classes that don't use __slots__ have a __weakref__ member added in the same way as __dict__ is added (i.e. only if the base didn't already have one). Classes using __slots__ can enable weak referenceability by adding '__weakref__' to the __slots__ list. Renamed the __weaklistoffset__ class member to __weakrefoffset__ -- it's not always a list, it seems. (Is tp_weaklistoffset a historical misnomer, or do I misunderstand this?)
* Document that uu.decode() will always raise a uu.Error if out_fileBarry Warsaw2001-08-171-9/+18
| | | | | isn't given, and the file in the uu header already exists. Also add a description of the uu.Error exception class.
* Test that uu.py will not override an existing file if out_file isn'tBarry Warsaw2001-08-171-0/+34
| | | | given and the path is gleaned from the uu header.
* decode(): Raise a uu.Error if no out_file is given but the fileBarry Warsaw2001-08-171-9/+13
| | | | | | | | | specified in the uu header already exists. No additional workaround is provided since out_file=pathname is a deprecated interface, so it is better to simply pass a file-like object into out_file anyway. This closes SF bug #438083. Use isinstance() tests instead of type comparisons.
* A self-contained piece of Michael Hudson's patchTim Peters2001-08-172-8/+46
| | | | | | | | | | | | | | #449043 supporting __future__ in simulated shells in support of PEP 264. Much has changed from the patch version: + Repaired bad hex constant for nested_scopes. + Defined symbolic CO_xxx names so global search will find these uses. + Made the exported list of feature names explicit, instead of abusing __all__ for this purpose (and redefined __all__ accordingly). + Added gross .compiler_flag verification to test___future__.py, and reworked it a little to make use of the newly exported explicit list of feature names.
* Address SF #451547. The approach is a bit draconian: any object thatGuido van Rossum2001-08-171-0/+14
| | | | | | | | | | is pickled as a global must now exist by the name under which it is pickled, otherwise the pickling fails. Previously, such things would fail on unpickling, or unpickle as the wrong global object. I'm hoping that this won't break existing code that is playing tricks with this. I need a volunteer to do this for cPickle too.
* Patch #445762: Support --disable-unicodeMartin v. Löwis2001-08-1742-185/+465
| | | | | | | | - Do not compile unicodeobject, unicodectype, and unicodedata if Unicode is disabled - check for Py_USING_UNICODE in all places that use Unicode functions - disables unicode literals, and the builtin functions - add the types.StringTypes list - remove Unicode literals from most tests.
* Another contributor's patch got accepted.Guido van Rossum2001-08-171-0/+1
|
* Change the 227 response parser to use a more liberal regularGuido van Rossum2001-08-171-7/+9
| | | | | | | | expression. This is needed for certain servers that (in violation of the standard) don't return the parentheses in the response. This fixes SF bug #441712 by Henrik Weber (not exactly using his patch).
* Make sure that ampersand escaping is still performed on the contents ofFred Drake2001-08-171-0/+2
| | | | | | | | | local module tables (the lists of modules documented within a chapter, inserted at the beginning of the chapter). If this is not done here, the text is not part of the resulting documents when latex2html does the processing normally. This fixes a little bit more of SF bug #451556.
* type_new(): look for __dynamic__ at the module level (after looking inGuido van Rossum2001-08-171-14/+54
| | | | | | | | | | | | | the class dict). Anything but a nonnegative int in either place is *ignored* (before, a non-Boolean was an error). The default is still static -- in a comparative test, Jeremy's Tools/compiler package ran twice as slow (compiling itself) using dynamic as the default. (The static version, which requires a few tweaks to avoid modifying class variables, runs at about the same speed as the classic version.) slot_tp_descr_get(): this also needed fallback behavior. slot_tp_getattro(): remove a debug fprintf() call.
* Strip trailing whitespace, including two lines containing only one orGuido van Rossum2001-08-171-11/+11
| | | | more tabs that XEmacs Makefile mode found suspicious.
* - Get rid of obsolete #define PATCHLEVEL.Guido van Rossum2001-08-171-4/+1
| | | | - Change PY_VERSION (but not the numeric versions) to "2.2a1+".
* Fix core dump in repr() of instancemethod whose class==NULL.Guido van Rossum2001-08-171-7/+11
|
* classic(),metods(): add tests to verify that a bound method without aGuido van Rossum2001-08-171-0/+2
| | | | class has a correct repr().
generated by cgit v0.12 at 2024-11-11 08:32:46 (GMT)