Michael Hudson wrote: > >... > I propose adding a fourth, optional, "flags" argument to the > builtin "compile" function. If this argument is omitted, there > will be no change in behaviour from that of Python 2.1. > > If it is present it is expected to be an integer, representing > various possible compile time options as a bitfield. Nit: What is the virtue to using a C-style bitfield? The efficiency isn't much of an issue. I'd prefer either keyword arguments or a list of strings. -- Take a recipe. Leave a recipe. Python Cookbook! http://www.ActiveState.com/pythoncookbook
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4