summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* UseGuido van Rossum2001-03-011-2/+2
| | | | | | | | find $(srcdir)/Lib -name '*.py[co]' -print | xargs rm -f to remove all .py[co] files before testing, rather than just those in the Lib/test directory. "find" is used all over the Makefile so I suppose it's safe; how about xargs?
* Call main routine in pydoc module (pydoc.cli).Ka-Ping Yee2001-03-011-76/+2
|
* Normalize case of paths in sys.path to avoid duplicates on Windows.Ka-Ping Yee2001-03-011-14/+24
| | | | | | Handle <... at 001B6378> like <... at 0x120f80> (%p is platform-dependent). Fix RCS version tag handling. Move __main__ behaviour into a function, pydoc.cli().
* Add test case for global stmt at module level.Jeremy Hylton2001-02-283-0/+10
| | | | | Fix test_grammar so that it ignores warning about global stmt at module level in exec.
* undo introduction of st_global_starJeremy Hylton2001-02-281-3/+0
|
* Document PyErr_WarnExplicit().Guido van Rossum2001-02-281-0/+9
|
* Warn about global statement at the module level.Jeremy Hylton2001-02-281-2/+17
| | | | Do better accounting for global variables.
* Document warn_explicit().Guido van Rossum2001-02-281-0/+10
|
* Disable GetWindowSpareFlag and GetWindowGoAwayBox on carbon.Jack Jansen2001-02-282-0/+14
|
* update output to reflect exception that is now raisedJeremy Hylton2001-02-281-3/+3
|
* Put PPC distributions back in, rearranged packages and use VISE variable ↵Jack Jansen2001-02-281-1/+1
| | | | magic to determine which ConfigurePythonXXX to run.
* add DEF_BOUNDJeremy Hylton2001-02-281-1/+3
|
* Add entry for the inspect module.Fred Drake2001-02-282-0/+2
|
* Clean up some of the markup for consistency, wrap some long lines.Fred Drake2001-02-281-45/+50
|
* Fix some rules broken by typos, others by the flattening of the makefile.Fred Drake2001-02-281-7/+7
|
* Add warning/error handlin for problematic nested scopes cases asJeremy Hylton2001-02-281-26/+119
| | | | | | | | | | | | | | | | | | | | | | | described in PEP 227. symtable_check_unoptimized() warns about import * and exec with "in" when it is used in a function that contains a nested function with free variables. Warnings are issued unless nested scopes are in effect, in which case these are SyntaxErrors. symtable_check_shadow() warns about assignments in a function scope that shadow free variables defined in a nested scope. This will always generate a warning -- and will behave differently with nested scopes than without. Restore full checking for free vars in children, even when nested scopes are not enabled. This is needed to support warnings for shadowing. Change symtable_warn() to return an int-- the return value of PyErr_WarnExplicit. Sundry cleanup: Remove commented out code. Break long lines.
* Fix filter for SyntaxErrorsJeremy Hylton2001-02-281-4/+4
|
* Fix for bug #405007: prefix subdir to scripts in order to build inAndrew M. Kuchling2001-02-281-0/+4
| | | | a subdirectory.
* Add description of PEP235Andrew M. Kuchling2001-02-281-19/+23
| | | | | Remove references to 2.1alpha Update description of PEP229
* Move a comment around to where it belongs (the code had alrady beenGuido van Rossum2001-02-281-1/+1
| | | | moved).
* Cover pydocAndrew M. Kuchling2001-02-281-48/+44
| | | | | | | Update reference Python version to beta1 Rip out PEP 232 section Add placeholders for PEP 236 and 235 Fix erroneous \filename references
* Document the object allocatorAndrew M. Kuchling2001-02-281-2/+12
| | | | Minor sentence change
* Let's have some sanity. Introduce a helper to issue a symbol tableGuido van Rossum2001-02-281-16/+17
| | | | warning.
* added description of NL tokenSkip Montanaro2001-02-281-1/+4
|
* Use the new PyErr_WarnExplicit() API to issue better warnings forGuido van Rossum2001-02-281-12/+21
| | | | | | | | | global after assign / use. Note: I'm not updating the PyErr_Warn() call for import * / exec combined with a function, because I can't trigger it with an example. Jeremy, just follow the example of the call to PyErr_WarnExplicit() that I *did* include.
* SyntaxError__init__(): Be a little more robust when picking apart theFred Drake2001-02-281-16/+22
| | | | | location information for the SyntaxError -- do not do more than we need to, stopping as soon as an exception has been raised.
* Move some constant initialization from FTP.__init__() and FTP.connect()Fred Drake2001-02-281-16/+16
| | | | | | | | to the class namespace. Allow FTP.close() to be called more than once without tossing cookies. (This seems to be a fairly common idiom for .close() methods, so let's try to be consistent.)
* Add PyErr_WarnExplicit(), which calls warnings.warn_explicit(), withGuido van Rossum2001-02-281-0/+42
| | | | explicit filename, lineno etc. arguments.
* Add declaration for PyErr_WarnExplicit().Guido van Rossum2001-02-281-0/+2
|
* Add a new API:Guido van Rossum2001-02-281-0/+10
| | | | | | | | | warn_explicit(message, category, filename, lineno, module, registry) The regular warn() call calculates a bunch of values and calls warn_explicit() with these. This will be used to issue better syntax warnings.
* Mention pydocAndrew M. Kuchling2001-02-281-0/+7
|
* Leave #! lines featuring /usr/bin/env aloneAndrew M. Kuchling2001-02-281-2/+4
|
* Now that Jeremy is asking about this code, it looks really bogus to me,Fred Drake2001-02-281-18/+0
| | | | | so let's rip it out. The constructor for SyntaxError does the right thing, so we do not need to do it again.
* Install the pydoc scriptAndrew M. Kuchling2001-02-281-1/+4
|
* Add script form of pydoc so that it's present in beta1. CurrentlyAndrew M. Kuchling2001-02-281-0/+78
| | | | | | this just copies the __name__=='__main__' logic from pydoc.py. ?!ng can decide whether he wants to create a main() in pydoc, or rip it out of pydoc.py completely.
* Fix for bug #404875: fix typo in setup.pyAndrew M. Kuchling2001-02-281-1/+1
|
* Placate tabnannyAndrew M. Kuchling2001-02-281-1/+1
|
* Define lots of constants for indexes into the structures for the fileFred Drake2001-02-281-7/+51
| | | | | | | | | | | | | header and central directory structures, and use them as appropriate. The point being to make it easier to tell what is getting pulled out where; magic numbers are evil! Change the computation of the ZipInfo.file_offset field to use the length of the relevant "extra" field -- there are two different ones, and the wrong one had been used. ;-( This closes SF tracker patch #403276, but more verbosely than the proposed patch.
* Add regression test for future statements. This adds eight files, butJeremy Hylton2001-02-2810-0/+132
| | | | | seven are not tests in their own right; these files are mentioned in regrtest.
* Improve SyntaxErrors for bad future statements. Set file and locationJeremy Hylton2001-02-284-94/+113
| | | | | | | for errors raised in future.c. Move some helper functions from compile.c to errors.c and make them API functions: PyErr_SyntaxLocation() and PyErr_ProgramText().
* SF patch 404928: Support for next Cygwin gcc (2.95.2-8)Tim Peters2001-02-283-13/+4
|
* Reset the resource file chain before calling PyMac_OpenPrefFile. I'm not ↵Jack Jansen2001-02-281-0/+1
| | | | sure why this wasn't a problem before...
* Oops, need to import Res.Jack Jansen2001-02-281-1/+4
|
* If we can't find our splash dialog (i.e. we're probably running from source) ↵Jack Jansen2001-02-281-4/+25
| | | | go into interactive mode: print what we're doing and ask about carbon/classic configure.
* Whitespace normalization.Tim Peters2001-02-286-12/+11
|
* Removed now-unreferenced CHECK_IMPORT_CASE from Windows config.h.Tim Peters2001-02-281-7/+0
| | | | NOTE: someone who understands Unix config should remove it from acconfig.h too.
* Print the offending line of code in the traceback for SyntaxErrorsJeremy Hylton2001-02-282-67/+144
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | raised by the compiler. XXX For now, text entered into the interactive intepreter is not printed in the traceback. Inspired by a patch from Roman Sulzhyk compile.c: Add helper fetch_program_text() that opens a file and reads until it finds the specified line number. The code is a near duplicate of similar code in traceback.c. Modify com_error() to pass two arguments to SyntaxError constructor, where the second argument contains the offending text when possible. Modify set_error_location(), now used only by the symtable pass, to set the text attribute on existing exceptions. pythonrun.c: Change parse_syntax_error() to continue of the offset attribute of a SyntaxError is None. In this case, it sets offset to -1. Move code from PyErr_PrintEx() into helper function print_error_text(). In the helper, only print the caret for a SyntaxError if offset > 0.
* Ack -- my eyes are getting bleary. Typos in the comment typo repairs.Tim Peters2001-02-281-1/+1
|
* Comment typos.Tim Peters2001-02-281-2/+2
|
* Implement PEP 235: Import on Case-Insensitive Platforms.Tim Peters2001-02-281-138/+87
| | | | | | | | | | | | | | | | | | | | | | | | | http://python.sourceforge.net/peps/pep-0235.html Renamed check_case to case_ok. Substantial code rearrangement to get this stuff in one place in the file. Innermost loop of find_module() now much simpler and #ifdef-free, and I want to keep it that way (it's bad enough that the innermost loop is itself still in an #ifdef!). Windows semantics tested and are fine. Jason, Cygwin *should* be fine if and only if what you did before "worked" for case_ok. Jack, the semantics on your flavor of Mac have definitely changed (see the PEP), and need to be tested. The intent is that your flavor of Mac now work the same as everything else in the "lower left" box, including respecting PYTHONCASEOK. Steven, sorry, you did the most work here so far but you got screwed the worst. Happy to work with you on repairing it, but I don't understand anything about all your Mac variants. We need to add another branch (or two, three, ...?) inside case_ok. But we should not need to change anything else.
generated by cgit v0.12 at 2024-11-22 23:10:51 (GMT)