summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* There is no PyArg_ConvertTuple(); call it by the right name.Fred Drake2002-04-011-1/+1
| | | | This closes SF bug #537511.
* Fix up the documentation of the type codes to give both the C and PythonFred Drake2002-04-011-17/+24
| | | | | | | | | types for each code, and give the actual C types. Clarified the support for slice operations and note when some TypeError exceptions are raised. This closes SF bugs 518767 and 536469.
* Change reference to execframes to naming.Jeremy Hylton2002-04-011-1/+1
|
* Restore a minimal definition of execution frame, since other parts ofJeremy Hylton2002-04-011-0/+6
| | | | | | | | the manual refer to it. XXX Not sure that it belongs in this section, or that the concept is particularly important for writing documentation. Perhaps references to the frame should be removed entirely.
* Update programmer's note on nested functions.Jeremy Hylton2002-04-011-5/+5
|
* Reword explanation of global statement since an undeclared global is aJeremy Hylton2002-04-011-3/+3
| | | | free variable and is subject to those rules.
* Note the sole case in which the ban on "from ... import *" within aJeremy Hylton2002-04-011-1/+5
| | | | function is enforced.
* Remove the following restriction:Jeremy Hylton2002-04-011-4/+0
| | | | | | | Names bound by import statements may not occur in global statements in the same scope. Why not?
* Note that it is illegal to delete a cell variable.Jeremy Hylton2002-04-011-2/+6
| | | | Note that deleteing an unbound local will raise a NameError.
* Given lambda its own section, instead of burying it in boolean operators.Jeremy Hylton2002-04-011-30/+7
|
* Update / simplify Identifiers section for nested scopes.Jeremy Hylton2002-04-011-18/+2
| | | | How do I create a cross reference to section 4.1?
* Update docs for nested scopes.Jeremy Hylton2002-04-012-257/+134
| | | | | | | | | | | | | Replace section 4.1 with section A.3. The new section 4.1 is titled "Naming and binding." It includes the text of section A.3 augmented with some of the detailed text from the old section 4.1. The \dfn, \index stuff is probably wrong, but I tried. Also update other parts of appendix A to mention that nested scopes and generators are standard features.
* Update to push the docs to python.org instead of python.sf.net.Fred Drake2002-04-012-9/+12
|
* Fixed errors in two comments.Tim Peters2002-04-011-3/+4
|
* Copy section on generators from the 2.2 document with a bit of rewritingAndrew M. Kuchling2002-04-011-1/+153
| | | | Add an item
* Restructured my pool-management overview in terms of the threeTim Peters2002-04-011-21/+61
| | | | | | | | | | | | | possible pool states. I think it's much clearer now. Added a new long overdue block-management overview comment block. I believe the comments are in good shape now. Added two comments about possible small optimizations (one getting rid of runtime multiplications at the cost of a new pool_header member; the other getting rid of runtime divisions and the pool_header capacity member, at the cost of a static const vector of 32 uints).
* Mention 2.2.1 in intro and in bug/patch countsAndrew M. Kuchling2002-04-011-8/+11
| | | | Fix two typos spotted by Joonas Paalasmaa
* Format strings (tuples,) appropriatelyNeal Norwitz2002-04-012-3/+3
|
* Use attributes appropriatelyNeal Norwitz2002-04-012-2/+2
|
* There is no TestError, use TestFailed appropriatelyNeal Norwitz2002-04-013-10/+10
|
* Update documentation of code objects.Jeremy Hylton2002-04-011-10/+15
| | | | | | | | Split the description of co_flags into two paragraphs. The first describes the flags that are used for non-future purposes, where CO_GENERATOR was added. The second describes __future__'s use of co_flags and mentions the only one currently meaningful, CO_FUTURE_DIVISION.
* Minor adjustments.Fred Drake2002-04-011-1/+2
|
* Small fixes for description of function attributes.Jeremy Hylton2002-04-011-5/+3
| | | | | | func_closure is a readonly attribute. Add \ttindex{} for func_closure. Remove discussion of func_closure specific to 2.1.
* Reindent. Break long lines. Move comments before the statements.Martin v. Löwis2002-04-011-3482/+3641
|
* Use the PyModule_Add*() APIs instead of manipulating the module dictFred Drake2002-04-015-283/+280
| | | | directly.
* Remove all but one use of the module dict.Fred Drake2002-04-011-44/+38
|
* Remove unused variable and call to PyModule_GetDict().Fred Drake2002-04-011-2/+1
|
* Switch to using METH_NOARGS where possible.Fred Drake2002-04-011-38/+18
| | | | Convert to use PyModule_*() instead of manipulating the module dict directly.
* Remove UNLESS.Martin v. Löwis2002-04-011-152/+152
|
* New PYMALLOC_DEBUG function void _PyMalloc_DebugDumpStats(void).Tim Peters2002-04-012-1/+98
| | | | | | | | | | | | | This displays stats about the # of arenas, pools, blocks and bytes, to stderr, both used and reserved but unused. CAUTION: Because PYMALLOC_DEBUG is on, the debug malloc routine adds 16 bytes to each request. This makes each block appear two size classes higher than it would be if PYMALLOC_DEBUG weren't on. So far, playing with this confirms the obvious: there's a lot of activity in the "small dict" size class, but nothing in the core makes any use of the 8-byte or 16-byte classes.
* We expect to skip the new test_mpz on Windows.Tim Peters2002-04-011-1/+5
|
* Use the PyModule_*() API instead of manipulating the module dictionaryFred Drake2002-04-012-11/+11
| | | | directly.
* Get rid of another use of PyArg_Parse()Neal Norwitz2002-04-011-2/+2
|
* Get rid of all METH_OLDARGS & PyArg_Parse.Neal Norwitz2002-04-012-43/+125
| | | | | Fix floating point exception if mpz.powm(10, 1, 0) (modulus == 0). Add a test.
* Remove some now-obsolete generator future statements.Tim Peters2002-04-016-19/+5
| | | | | I left the email pkg alone; I'm not sure how Barry would like to handle that.
* Convert file.readinto() to stop using METH_OLDARGS & PyArg_Parse.Neal Norwitz2002-04-012-2/+17
| | | | Add test for file.readinto().
* Hopeful fix for SF bug 503031: urllib.py: open_http() host problem.Guido van Rossum2002-03-311-1/+5
| | | | | | | I really can't test this, but from reading the discussion in that bug report, it's likely that this works. It may also close a whole bunch of other bug reports related to urllib and proxies on Windows, but who knows.
* mpz_float() only takes one parameter nowNeal Norwitz2002-03-311-5/+0
|
* Added a "run with commandline Python" flag. Works in MachoPython, should workJack Jansen2002-03-311-12/+54
| | | | | in OSX MacPython (untested), and should be disabled/removed in OS9 (but that doesn't happen yet).
* Get rid of warnings due to changing to METH_NOARGSNeal Norwitz2002-03-311-5/+5
|
* Use METH_VARARGS rather than METH_OLDARGS implicitly (args are ignored)Neal Norwitz2002-03-311-1/+1
|
* Convert METH_OLDARGS -> METH_NOARGS: remove args parameterNeal Norwitz2002-03-311-243/+247
| | | | Use METH_OLDARGS explicitly rather than implicitly.
* Revert use of METH_OLDARGS (use 0) to support 1.5.2Neal Norwitz2002-03-311-2/+4
|
* Convert METH_OLDARGS -> METH_VARARGS: also PyArg_Parse -> PyArg_ParseTupleNeal Norwitz2002-03-313-47/+34
| | | | Please review for correctness.
* Remove METH_OLDARGS:Neal Norwitz2002-03-3111-164/+85
| | | | | | | Convert METH_OLDARGS -> METH_VARARGS: also PyArg_Parse -> PyArg_ParseTuple Convert METH_OLDARGS -> METH_NOARGS: remove args parameter Please review. All tests pass, but some modules don't have tests. I spot checked various functions to try to make sure nothing broke.
* Convert from using METH_OLDARGS to METH_NOARGS.Neal Norwitz2002-03-313-85/+44
| | | | These should be safe.
* Fix whitespaceNeal Norwitz2002-03-311-2/+1
|
* Use symbolic METH_VARARGS/METH_OLDARGS instead of 1/0 for ml_flagsNeal Norwitz2002-03-313-17/+17
|
* Use symbolic METH_VARARGS instead of 1 for ml_flagsNeal Norwitz2002-03-315-51/+51
|
* Use docstrings for exception classesNeal Norwitz2002-03-312-2/+4
|
generated by cgit v0.12 at 2025-03-04 01:23:33 (GMT)