1. 16 Jul, 2001 7 commits
    • Kurt B. Kaiser's avatar
      Add a script "idles" which opens a Python Shell window. · e222a292
      Kurt B. Kaiser authored
      The default behaviour of idlefork idle is to open an editor window instead
      of a shell. Complex expressions may be run in a fresh environment by
      selecting "run".  There are times, however, when a shell is desired.
      Though one can be started by "idle -t 'foo'", this script is more
      convenient.  In addition, a shell and an editor window can be started
      in parallel by "idles -e foo.py".
      e222a292
    • Tim Peters's avatar
      Ugly. A pile of new xxxFlags() functions, to communicate to the parser · 54a685c6
      Tim Peters authored
      that 'yield' is a keyword.  This doesn't help test_generators at all!  I
      don't know why not.  These things do work now (and didn't before this
      patch):
      
      1. "from __future__ import generators" now works in a native shell.
      
      2. Similarly "python -i xxx.py" now has generators enabled in the
         shell if xxx.py had them enabled.
      
      3. This program (which was my doctest proxy) works fine:
      
      from __future__ import generators
      
      source = """\
      def f():
          yield 1
      """
      
      exec compile(source, "", "single") in globals()
      print type(f())
      54a685c6
    • Kurt B. Kaiser's avatar
      Call out IDLE Fork in startup message. · 1074cabd
      Kurt B. Kaiser authored
      1074cabd
    • Kurt B. Kaiser's avatar
      Add a script "idles" which opens a Python Shell window. · 91475b72
      Kurt B. Kaiser authored
      The default behaviour of idlefork idle is to open an editor window instead
      of a shell. Complex expressions may be run in a fresh environment by
      selecting "run".  There are times, however, when a shell is desired.
      Though one can be started by "idle -t 'foo'", this script is more
      convenient.  In addition, a shell and an editor window can be started
      in parallel by "idles -e foo.py".
      91475b72
    • Tim Peters's avatar
      future.c: insert a cosmetic space. · b4638518
      Tim Peters authored
      pythonrun.c, run_pyc_file():  repair semantic error wrt CO_GENERATOR vs
      CO_GENERATOR_ALLOWED.
      b4638518
    • Tim Peters's avatar
      Part way to allowing "from __future__ import generators" to communicate · 0bfd3b1b
      Tim Peters authored
      that info to code dynamically compiled *by* code compiled with generators
      enabled.  Doesn't yet work because there's still no way to tell the parser
      that "yield" is OK (unlike nested_scopes, the parser has its fingers in
      this too).
      Replaced PyEval_GetNestedScopes by a more-general
      PyEval_MergeCompilerFlags.  Perhaps I should not have?  I doubted it was
      *intended* to be part of the public API, so just did.
      0bfd3b1b
    • Andrew M. Kuchling's avatar
      Began actually writing: · 58b7b5b9
      Andrew M. Kuchling authored
      * iterators
      * generators
      * copied the nested scopes section from the 2.1 article
      * standard library changes
      58b7b5b9
  2. 15 Jul, 2001 5 commits
  3. 14 Jul, 2001 28 commits