summaryrefslogtreecommitdiffstats
path: root/Lib/__future__.py
Commit message (Collapse)AuthorAgeFilesLines
* Repair repr of future-features (wasn't updated to include the newTim Peters2001-08-241-2/+3
| | | | compiler-flag argument).
* Back out trying to use the C values for CO_xxx.Tim Peters2001-08-241-10/+10
| | | | | __future__.py reverted to 1.9. newmodule.c reverted to 2.32.
* Avoid total dependency on the new module. This addresses the problemGuido van Rossum2001-08-191-1/+7
| | | | reported by Greg Ball on python-dev.
* Expose the CO_xxx flags via the "new" module (re-solving a problem "theTim Peters2001-08-181-11/+4
| | | | | | | | | | 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.
* A self-contained piece of Michael Hudson's patchTim Peters2001-08-171-7/+40
| | | | | | | | | | | | | | #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.
* Implement PEP 238 in its (almost) full glory.Guido van Rossum2001-08-081-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Preliminary support for "from __future__ import generators" to enableGuido van Rossum2001-07-151-0/+1
| | | | | | | | the yield statement. I figure we have to have this in before I can release 2.2a1 on Wednesday. Note: test_generators is currently broken, I'm counting on Tim to fix this.
* Remove now-unnecessary "from __future__ import nested_scopes" stmts.Tim Peters2001-07-121-1/+1
|
* Remove redundant "__future__:" from module docstring.Ka-Ping Yee2001-03-151-1/+1
|
* Typo repair.Tim Peters2001-03-021-1/+1
|
* Make names in __future__.py bind to class instances instead of 2-tuples.Tim Peters2001-03-021-7/+32
| | | | Suggested on c.l.py by William Tanksley, and I like it.
* Whitespace normalization.Tim Peters2001-02-281-4/+4
|
* Add __future__.py to std library, + dull test to verify that assignmentsTim Peters2001-02-261-0/+44
therein are of the proper form.
generated by cgit v0.12 at 2024-10-01 00:26:27 (GMT)