Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #87962 > unrolled thread

Re: Function Defaults - avoiding unneccerary combinations of arguments at input

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Function Defaults - avoiding unneccerary combinations of arguments at input Terry Reedy <tjreedy@udel.edu> - 2015-03-25 14:43 -0400

#87962 — Re: Function Defaults - avoiding unneccerary combinations of arguments at input

On 3/25/2015 1:43 PM, Ivan Evstegneev wrote:
> Hello all ,
>
>
> Just a little question about function's default arguments.
>
> Let's say I have this function:
>
> def  my_fun(history=False, built=False, current=False, topo=None,
> full=False, file=None):
> 	if currnet and full:
> 		do something_1
> 	elif current and file:
> 		do something_2
> 	elif history and full and file:
> 		do something_3
> 	
>
> 	...... some code here..............
>
> and so on...
>
> I won't cover all the possibilities here (actually I don't use all of them
> ^_^).
>
> The question is about avoiding the response for unnecessary combinations?
>
> For instance, if user will call function this way:
>
>
>>>> my_fun(current=True, full=True, topo='some str', file="some_file")
>
> That will lead to function's misbehavior. As a particular case it will
> choose "current and full" condition.
>
>
> What is the common accepted way to deal with such unwanted situations?

Raise a value error for illegal combinations.  There are a few instances 
in the stdlib where 2 of several options are mutually incompatible.


-- 
Terry Jan Reedy

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web