1. 09 May, 2010 1 kayıt (commit)
  2. 30 Eki, 2008 1 kayıt (commit)
  3. 09 Haz, 2008 1 kayıt (commit)
  4. 26 May, 2008 1 kayıt (commit)
  5. 26 Mar, 2008 1 kayıt (commit)
  6. 18 Mar, 2008 1 kayıt (commit)
    • Eric Smith's avatar
      Backport of the print function, using a __future__ import. · 7c47894a
      Eric Smith yazdı
      This work is substantially Anthony Baxter's, from issue
      1633807.  I just freshened it, made a few minor tweaks,
      and added the test cases.  I also created issue 2412,
      which is to check for 2to3's behavior with the print
      function.  I also added myself to ACKS.
      7c47894a
  7. 07 Ock, 2008 1 kayıt (commit)
  8. 23 Tem, 2006 1 kayıt (commit)
  9. 11 Nis, 2006 1 kayıt (commit)
  10. 10 Nis, 2006 1 kayıt (commit)
  11. 03 Nis, 2006 1 kayıt (commit)
  12. 28 Şub, 2006 2 kayıt (commit)
    • Thomas Wouters's avatar
    • Thomas Wouters's avatar
      SF patch #1438387, PEP 328: relative and absolute imports. · f7f438ba
      Thomas Wouters yazdı
       - IMPORT_NAME takes an extra argument from the stack: the relativeness of
         the import. Only passed to __import__ when it's not -1.
      
       - __import__() takes an optional 5th argument for the same thing; it
         __defaults to -1 (old semantics: try relative, then absolute)
      
       - 'from . import name' imports name (be it module or regular attribute)
         from the current module's *package*. Likewise, 'from .module import name'
         will import name from a sibling to the current module.
      
       - Importing from outside a package is not allowed; 'from . import sys' in a
         toplevel module will not work, nor will 'from .. import sys' in a
         (single-level) package.
      
       - 'from __future__ import absolute_import' will turn on the new semantics
         for import and from-import: imports will be absolute, except for
         from-import with dots.
      
      Includes tests for regular imports and importhooks, parser changes and a
      NEWS item, but no compiler-package changes or documentation changes.
      f7f438ba
  13. 06 Ara, 2005 2 kayıt (commit)
  14. 13 Kas, 2005 1 kayıt (commit)
  15. 20 Eki, 2005 1 kayıt (commit)
    • Jeremy Hylton's avatar
      Merge ast-branch to head · 3e0055f8
      Jeremy Hylton yazdı
      This change implements a new bytecode compiler, based on a
      transformation of the parse tree to an abstract syntax defined in
      Parser/Python.asdl.
      
      The compiler implementation is not complete, but it is in stable
      enough shape to run the entire test suite excepting two disabled
      tests.
      3e0055f8
  16. 04 Şub, 2005 1 kayıt (commit)
  17. 31 Agu, 2004 1 kayıt (commit)
  18. 11 Ara, 2002 1 kayıt (commit)
  19. 12 Nis, 2002 1 kayıt (commit)
  20. 20 Agu, 2001 1 kayıt (commit)
  21. 10 Agu, 2001 1 kayıt (commit)
    • Jeremy Hylton's avatar
      Refactor future feature handling · b857ba26
      Jeremy Hylton yazdı
      Replace uses of PyCF_xxx with CO_xxx.
      
      Replace individual feature slots in PyFutureFeatures with single
      bitmask ff_features.
      
      When flags must be transfered among the three parts of the interpreter
      that care about them -- the pythonrun layer, the compiler, and the
      future feature parser -- can simply or (|) the definitions.
      b857ba26
  22. 08 Agu, 2001 1 kayıt (commit)
    • Guido van Rossum's avatar
      Implement PEP 238 in its (almost) full glory. · 4668b000
      Guido van Rossum yazdı
      This introduces:
      
      - A new operator // that means floor division (the kind of division
        where 1/2 is 0).
      
      - The "future division" statement ("from __future__ import division)
        which changes the meaning of the / operator to implement "true
        division" (where 1/2 is 0.5).
      
      - New overloadable operators __truediv__ and __floordiv__.
      
      - New slots in the PyNumberMethods struct for true and floor division,
        new abstract APIs for them, new opcodes, and so on.
      
      I emphasize that without the future division statement, the semantics
      of / will remain unchanged until Python 3.0.
      
      Not yet implemented are warnings (default off) when / is used with int
      or long arguments.
      
      This has been on display since 7/31 as SF patch #443474.
      
      Flames to /dev/null.
      4668b000
  23. 16 Tem, 2001 2 kayıt (commit)
    • Tim Peters's avatar
      future.c: insert a cosmetic space. · 51d76f1f
      Tim Peters yazdı
      pythonrun.c, run_pyc_file():  repair semantic error wrt CO_GENERATOR vs
      CO_GENERATOR_ALLOWED.
      51d76f1f
    • Tim Peters's avatar
      Part way to allowing "from __future__ import generators" to communicate · 5ba58662
      Tim Peters yazdı
      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.
      5ba58662
  24. 15 Tem, 2001 1 kayıt (commit)
  25. 10 Mar, 2001 1 kayıt (commit)
  26. 28 Şub, 2001 3 kayıt (commit)
    • Jeremy Hylton's avatar
      Improve SyntaxErrors for bad future statements. Set file and location · ad3d3f2f
      Jeremy Hylton yazdı
      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().
      ad3d3f2f
    • Jeremy Hylton's avatar
      Need to support single_input explicitly so from __future__ imports · 280c81a9
      Jeremy Hylton yazdı
      are legal at the interactive interpreter prompt.  They don't do
      anything yet...
      280c81a9
    • Jeremy Hylton's avatar
      Presumed correct compiler pass for future statements · 39e2f3f8
      Jeremy Hylton yazdı
      XXX still need to integrate into symtable API
      
      compile.h: Remove ff_n_simple_stmt; obsolete.
      
                 Add ff_found_docstring used internally to skip one and only
                 one string at the beginning of a module.
      
      compile.c: Add check for from __future__ imports to far into the file.
      
       	   In symtable_global() check for -1 returned from
      	   symtable_lookup(), which signifies name not defined.
      
      	   Add missing DECERF in symtable_add_def.
      
                 Free c->c_future.
      
      future.c:  Add special handling for multiple statements joined on a
      	   single line using one or more semicolons; this form can
                 include an illegal future statement that would otherwise be
                 hard to detect.
      
      	   Add support for detecting and skipping doc strings.
      39e2f3f8
  27. 27 Şub, 2001 1 kayıt (commit)
    • Jeremy Hylton's avatar
      Improved __future__ parser; still more to do · 4db62b1e
      Jeremy Hylton yazdı
      Makefile.pre.in: add target future.o
      
      Include/compile.h: define PyFutureFeaters and PyNode_Future()
                         add c_future slot to struct compiling
      
      Include/symtable.h: add st_future slot to struct symtable
      
      Python/future.c: implementation of PyNode_Future()
      
      Python/compile.c: use PyNode_Future() for nested_scopes support
      
      Python/symtable.c: include compile.h to pick up PyFutureFeatures decl
      4db62b1e