[Patches] [ python-Patches-449043 ] supporting __future__ in simulated shells

noreply@sourceforge.net noreply@sourceforge.net
Thu, 09 Aug 2001 22:01:42 -0700


Patches item #449043, was opened at 2001-08-08 02:05
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=305470&aid=449043&group_id=5470

Category: library
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Hudson (mwh)
>Assigned to: Tim Peters (tim_one)
Summary: supporting __future__ in simulated shells

Initial Comment:
This implements the short PEP I posted to python-dev last week.

It doesn't do docs, and it uses the disputed bitfield interface to compile(), so it should be considered a first cut.


----------------------------------------------------------------------

>Comment By: Tim Peters (tim_one)
Date: 2001-08-09 22:01

Message:
Logged In: YES 
user_id=31435

Assigned to me.  WIll look more closely later.  Things that 
struck the eye at once:

+ _Feature.matches needs a docstring.

+ "<>" is deprecated; use "!=".

+ I think we need a way not to "or" in the caller's flags 
too; but you also think that, so this shouldn't be hard for 
us to reach agreement on <wink>.


----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2001-08-09 15:26

Message:
Logged In: YES 
user_id=6656

New version.

This one attaches knowledge of code flag and compile time bits to the
_Feature objects in Lib/__future__.py.

It also rewrites the docstrings in codeop.py; still pending: latex docs, 
updates to my PEP and possibly 236 (the __future__ one), sanity checking
the arguments to __builtin__.compile().


----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-08-08 07:26

Message:
Logged In: YES 
user_id=6380

Nice! Two questions:

1. Why the refactoring of codeop.py?

2. Shouldn't the built-in compile() do a sanity check on the
flags it accepts?

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=305470&aid=449043&group_id=5470