Message 65095 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	belopolsky
Recipients	belopolsky, georg.brandl, gvanrossum, twouters
Date	2008年04月07日.19:00:14
SpamBayes Score	0.4605531
Marked as misclassified	No
Message-id	<1207594815.42.0.17940161805.issue2292@psf.upfronthosting.co.za>

Content
Thomas, Could you add BUILD__UNPACK opcodes documentation to Doc/library/dis.rst? It would also help if you modify CALL_FUNCTION_ opcodes' documentation to explain how they will interact with unpacking opcodes. Do I understand correctly that non-starred arguments are packed into intermediate tuples/sets in the presence of starred arguments so that {a,b,c,d,e} is equivalent to {{a,b},c,{d,e}}? This should not be a problem for tuples, but with sets, it means that {a,b,c} may behave subtly differently from {a,*(b,c)}.

Content

Thomas,
Could you add BUILD_*_UNPACK opcodes documentation to
Doc/library/dis.rst? It would also help if you modify CALL_FUNCTION_*
opcodes' documentation to explain how they will interact with unpacking
opcodes.
Do I understand correctly that non-starred arguments are packed into
intermediate tuples/sets in the presence of starred arguments so that
{a,b,*c,d,e} is equivalent to {*{a,b},*c,*{d,e}}? This should not be a
problem for tuples, but with sets, it means that {a,b,c} may behave
subtly differently from {a,*(b,c)}.

History
Date	User	Action	Args
2008年04月07日 19:00:15	belopolsky	set	spambayes_score: 0.460553 -> 0.4605531 recipients: + belopolsky, gvanrossum, twouters, georg.brandl
2008年04月07日 19:00:15	belopolsky	set	spambayes_score: 0.460553 -> 0.460553 messageid: <1207594815.42.0.17940161805.issue2292@psf.upfronthosting.co.za>
2008年04月07日 19:00:14	belopolsky	link	issue2292 messages
2008年04月07日 19:00:14	belopolsky	create

homepage