kwdargs for compile/__import__

[Yhg1s]

BPO	1444529
Nosy	@loewis, @Yhg1s, @birkenfeld
Files	kwds.diff

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/birkenfeld'
closed_at = <Date 2007-03-13.20:47:10.000>
created_at = <Date 2006-03-07.00:55:30.000>
labels = ['interpreter-core']
title = 'kwdargs for compile/__import__'
updated_at = <Date 2007-03-13.20:47:10.000>
user = 'https://github.com/Yhg1s'

bugs.python.org fields:

activity = <Date 2007-03-13.20:47:10.000>
actor = 'georg.brandl'
assignee = 'georg.brandl'
closed = True
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2006-03-07.00:55:30.000>
creator = 'twouters'
dependencies = []
files = ['7056']
hgrepos = []
issue_num = 1444529
keywords = ['patch']
message_count = 4.0
messages = ['49681', '49682', '49683', '49684']
nosy_count = 4.0
nosy_names = ['loewis', 'twouters', 'nnorwitz', 'georg.brandl']
pr_nums = []
priority = 'normal'
resolution = 'accepted'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1444529'
versions = ['Python 2.5']

[Yhg1s]

Keyword arguments for compile() and __import__(), as
discussed at PyCon. There is a slight speed difference
on my development system: __import__ is ~1% slower,
compile() is ~1.5% faster. I blame both on caches,
alignment and what not, so I bet they're totally
different for everyone. I'd say the advantage of
managing the growing set of arguments outweighs the
speed impact (if any.)

[nnorwitz]

Logged In: YES
user_id=33168

These look good to me. Thanks Thomas. I had started a patch
for import. BTW I think the new __import__ needs to be
documented in libfuncs.txt or somewhere like that. If you
don't get to it, I'll find my change and update the docs.

[loewis]

Is anybody still working on this?

[birkenfeld]

__import__ already accepted kwargs, committed the compile() part in rev. 54358.