Method for adding error messages to a dictionary given a key The 2019 Stack Overflow Developer Survey Results Are In“Multi-key” dictionaryOutputting all possible words which fit a string of lettersCheck value from two different dictionary with matched keyDictionary of key signatures for various major and minor scalesResolving MySQL 1215 errors in a declarative MySQL migration systemSmall Chatbot challengeSimple Python script seems to stop when N >> 1Make a given number by adding given numbersAdding values from DictReader to empty dictionaryDefine the scope of negation with the Dependency Parser of spaCy

Button changing its text & action. Good or terrible?

Why doesn't UInt have a toDouble()?

For what reasons would an animal species NOT cross a *horizontal* land bridge?

How much of the clove should I use when using big garlic heads?

What to do when moving next to a bird sanctuary with a loosely-domesticated cat?

What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?

Will it cause any balance problems to have PCs level up and gain the benefits of a long rest mid-fight?

How to notate time signature switching consistently every measure

Is it a good practice to use a static variable in a Test Class and use that in the actual class instead of Test.isRunningTest()?

What is the most efficient way to store a numeric range?

Why does the nucleus not repel itself?

How can I add encounters in the Lost Mine of Phandelver campaign without giving PCs too much XP?

Worn-tile Scrabble

Cooking pasta in a water boiler

Why doesn't shell automatically fix "useless use of cat"?

How can I define good in a religion that claims no moral authority?

Is Cinnamon a desktop environment or a window manager? (Or both?)

The phrase "to the numbers born"?

Unitary representations of finite groups over finite fields

Ubuntu Server install with full GUI

Dropping list elements from nested list after evaluation

Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?

Can I have a signal generator on while it's not connected?

Why couldn't they take pictures of a closer black hole?



Method for adding error messages to a dictionary given a key



The 2019 Stack Overflow Developer Survey Results Are In“Multi-key” dictionaryOutputting all possible words which fit a string of lettersCheck value from two different dictionary with matched keyDictionary of key signatures for various major and minor scalesResolving MySQL 1215 errors in a declarative MySQL migration systemSmall Chatbot challengeSimple Python script seems to stop when N >> 1Make a given number by adding given numbersAdding values from DictReader to empty dictionaryDefine the scope of negation with the Dependency Parser of spaCy



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








8












$begingroup$


I want this method to be completely understandable just from looking at the code and comments only.



def add_error(error_dict, key, err):
"""Given an error message, or a list of error messages, this method
adds it/them to a dictionary of errors.

Doctests:
>>> add_error(, 'key1', 'error1')
'key1': ['error1']
>>> add_error('key1': ['error1'], 'key1', 'error2')
'key1': ['error1', 'error2']
>>> add_error('key1': ['error1', 'error2'], 'key2', 'error1')
'key1': ['error1', 'error2'], 'key2': ['error1']
>>> add_error(, 'key1', ['error1', 'error2'])
'key1': ['error1', 'error2']
>>> add_error(, 'key1', [])

>>> add_error('key1': ['error1'], 'key2', ['error1', 'error2'])
'key1': ['error1'], 'key2': ['error1', 'error2']
>>> add_error(, 'key1', 23) # doctest: +IGNORE_EXCEPTION_DETAIL
Traceback (most recent call last):
...
TypeError: The error(s) must be a string, or a list of strings.
>>> add_error(, 'key1', [23]) # doctest: +IGNORE_EXCEPTION_DETAIL
Traceback (most recent call last):
...
TypeError: The error(s) must be a string, or a list of strings.
>>> add_error(, 'key1', ['error1', 23]) # doctest:
+IGNORE_EXCEPTION_DETAIL
Traceback (most recent call last):
...
TypeError: The error(s) must be a string, or a list of strings.
"""
if not isinstance(err, list):
err = [err]

if not key in error_dict and len(err) > 0:
error_dict[key] = []

for e in err:
if not isinstance(e, string_types):
raise TypeError(
'The error(s) must be a string, or a list of strings.'
)
error_dict[key].append(e)
return error_dict


Hopefully, the code along with the comment does the job well, but I would still appreciate review(s) of this method. One thing I always keep on wondering is whether this is too many doc-tests for such a simple method. Thanks.










share|improve this question









$endgroup$


















    8












    $begingroup$


    I want this method to be completely understandable just from looking at the code and comments only.



    def add_error(error_dict, key, err):
    """Given an error message, or a list of error messages, this method
    adds it/them to a dictionary of errors.

    Doctests:
    >>> add_error(, 'key1', 'error1')
    'key1': ['error1']
    >>> add_error('key1': ['error1'], 'key1', 'error2')
    'key1': ['error1', 'error2']
    >>> add_error('key1': ['error1', 'error2'], 'key2', 'error1')
    'key1': ['error1', 'error2'], 'key2': ['error1']
    >>> add_error(, 'key1', ['error1', 'error2'])
    'key1': ['error1', 'error2']
    >>> add_error(, 'key1', [])

    >>> add_error('key1': ['error1'], 'key2', ['error1', 'error2'])
    'key1': ['error1'], 'key2': ['error1', 'error2']
    >>> add_error(, 'key1', 23) # doctest: +IGNORE_EXCEPTION_DETAIL
    Traceback (most recent call last):
    ...
    TypeError: The error(s) must be a string, or a list of strings.
    >>> add_error(, 'key1', [23]) # doctest: +IGNORE_EXCEPTION_DETAIL
    Traceback (most recent call last):
    ...
    TypeError: The error(s) must be a string, or a list of strings.
    >>> add_error(, 'key1', ['error1', 23]) # doctest:
    +IGNORE_EXCEPTION_DETAIL
    Traceback (most recent call last):
    ...
    TypeError: The error(s) must be a string, or a list of strings.
    """
    if not isinstance(err, list):
    err = [err]

    if not key in error_dict and len(err) > 0:
    error_dict[key] = []

    for e in err:
    if not isinstance(e, string_types):
    raise TypeError(
    'The error(s) must be a string, or a list of strings.'
    )
    error_dict[key].append(e)
    return error_dict


    Hopefully, the code along with the comment does the job well, but I would still appreciate review(s) of this method. One thing I always keep on wondering is whether this is too many doc-tests for such a simple method. Thanks.










    share|improve this question









    $endgroup$














      8












      8








      8





      $begingroup$


      I want this method to be completely understandable just from looking at the code and comments only.



      def add_error(error_dict, key, err):
      """Given an error message, or a list of error messages, this method
      adds it/them to a dictionary of errors.

      Doctests:
      >>> add_error(, 'key1', 'error1')
      'key1': ['error1']
      >>> add_error('key1': ['error1'], 'key1', 'error2')
      'key1': ['error1', 'error2']
      >>> add_error('key1': ['error1', 'error2'], 'key2', 'error1')
      'key1': ['error1', 'error2'], 'key2': ['error1']
      >>> add_error(, 'key1', ['error1', 'error2'])
      'key1': ['error1', 'error2']
      >>> add_error(, 'key1', [])

      >>> add_error('key1': ['error1'], 'key2', ['error1', 'error2'])
      'key1': ['error1'], 'key2': ['error1', 'error2']
      >>> add_error(, 'key1', 23) # doctest: +IGNORE_EXCEPTION_DETAIL
      Traceback (most recent call last):
      ...
      TypeError: The error(s) must be a string, or a list of strings.
      >>> add_error(, 'key1', [23]) # doctest: +IGNORE_EXCEPTION_DETAIL
      Traceback (most recent call last):
      ...
      TypeError: The error(s) must be a string, or a list of strings.
      >>> add_error(, 'key1', ['error1', 23]) # doctest:
      +IGNORE_EXCEPTION_DETAIL
      Traceback (most recent call last):
      ...
      TypeError: The error(s) must be a string, or a list of strings.
      """
      if not isinstance(err, list):
      err = [err]

      if not key in error_dict and len(err) > 0:
      error_dict[key] = []

      for e in err:
      if not isinstance(e, string_types):
      raise TypeError(
      'The error(s) must be a string, or a list of strings.'
      )
      error_dict[key].append(e)
      return error_dict


      Hopefully, the code along with the comment does the job well, but I would still appreciate review(s) of this method. One thing I always keep on wondering is whether this is too many doc-tests for such a simple method. Thanks.










      share|improve this question









      $endgroup$




      I want this method to be completely understandable just from looking at the code and comments only.



      def add_error(error_dict, key, err):
      """Given an error message, or a list of error messages, this method
      adds it/them to a dictionary of errors.

      Doctests:
      >>> add_error(, 'key1', 'error1')
      'key1': ['error1']
      >>> add_error('key1': ['error1'], 'key1', 'error2')
      'key1': ['error1', 'error2']
      >>> add_error('key1': ['error1', 'error2'], 'key2', 'error1')
      'key1': ['error1', 'error2'], 'key2': ['error1']
      >>> add_error(, 'key1', ['error1', 'error2'])
      'key1': ['error1', 'error2']
      >>> add_error(, 'key1', [])

      >>> add_error('key1': ['error1'], 'key2', ['error1', 'error2'])
      'key1': ['error1'], 'key2': ['error1', 'error2']
      >>> add_error(, 'key1', 23) # doctest: +IGNORE_EXCEPTION_DETAIL
      Traceback (most recent call last):
      ...
      TypeError: The error(s) must be a string, or a list of strings.
      >>> add_error(, 'key1', [23]) # doctest: +IGNORE_EXCEPTION_DETAIL
      Traceback (most recent call last):
      ...
      TypeError: The error(s) must be a string, or a list of strings.
      >>> add_error(, 'key1', ['error1', 23]) # doctest:
      +IGNORE_EXCEPTION_DETAIL
      Traceback (most recent call last):
      ...
      TypeError: The error(s) must be a string, or a list of strings.
      """
      if not isinstance(err, list):
      err = [err]

      if not key in error_dict and len(err) > 0:
      error_dict[key] = []

      for e in err:
      if not isinstance(e, string_types):
      raise TypeError(
      'The error(s) must be a string, or a list of strings.'
      )
      error_dict[key].append(e)
      return error_dict


      Hopefully, the code along with the comment does the job well, but I would still appreciate review(s) of this method. One thing I always keep on wondering is whether this is too many doc-tests for such a simple method. Thanks.







      python python-3.x






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 30 at 18:49









      darkhorsedarkhorse

      1804




      1804




















          3 Answers
          3






          active

          oldest

          votes


















          8












          $begingroup$

          Consider narrowing accepted types



          This might not be possible based on the context of your code, but if it is: arguments sharing one of many different types hinders and complicates testability and maintainability. There are many different solutions to this that will help this situation; one is accepting variadic arguments - i.e.



          def add_error(error_dict, key, *errs):


          This is still easily invocable without needing to wrap a single error in a list.



          Use x not in instead of not x in



          i.e.



          if key not in error_dict


          Lose your loop



          and also lose your empty-list assignment, instead doing



          error_dict.setdefault(key, []).extend(err)


          If you use the variadic suggestion above, your entire function becomes that one line.



          Immutable or not?



          Currently you do two things - alter a dictionary and return it - when you should only pick one. Either make a copy of the dict and return an altered version, or modify the dict and don't return anything.






          share|improve this answer









          $endgroup$




















            5












            $begingroup$

            congratulations on writing a fairly clear, readable function! (And welcome!)



            What types do you take?



            You explicitly check for an instance of type list. I think you should invert your check, and look for a string type instead. The reason is that it would enable you to accept iterables other than list as your errors.



            For example, you would be able to do something like:



            add_error(edict, 'key', (str(e) for e in ...))


            That last parameter is not a list, but it is something you might want to do. Also, *args is not a list but a tuple - you might want to splat a tuple rather than converting it to a list first.



            What types do you take?



            Your key parameter is always tested as a string. But dicts can have other key-types than string, and you neither test those, nor do you appear to have coded any kind of rejection on that basis. I suggest you add some tests that demonstrate your intent: is it okay to use non-strings as keys, or not?



            What constraints exist on the errors?



            I don't see any indication of what happens when duplicate errors are added. Is this intended to be allowed, or not?



            What constraints exist on the keys?



            Is it okay to use None as a key? How about '' (empty string)? Tests, please.






            share|improve this answer









            $endgroup$




















              0












              $begingroup$

              Type Hints



              Based on your doctests, you must be using Python 3.6 or later (due to reliance on dictionary key order).



              Since Python 3.5+ includes support for type hints, you could declare you function as:



              def add_error(error_dict: dict, key: str, err: list) -> dict:


              Or



              from typing import List, Dict

              def add_error(error_dict: Dict[str, List[str]], key: str,
              err: List[str]) -> Dict[str]:


              Of course, modify the type hints if you take the argument changes suggested in other answers. In particular, as is, the type of err is actually a variant type. I’d prefer a variable list of strings, *err: str.



              Detect Errors before Modifying



              If an error is not a string, you will raise an exception. But first, if the key does not exist in the dictionary, you add an empty list for that key.



              If the error list contains strings before a non-string, you add those strings to the key’s list, then raise an exception part way through.



              Consider moving the checks up to the start of the function, before any changes have been made.



              if any(not isinstance(e, string_types) for e in err):
              raise TypeError("The error(s) must be a string, or list of strings")


              Duck Typing



              Why must the errors be a string? Any object can be converted to a string...






              share|improve this answer











              $endgroup$













                Your Answer





                StackExchange.ifUsing("editor", function ()
                return StackExchange.using("mathjaxEditing", function ()
                StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix)
                StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
                );
                );
                , "mathjax-editing");

                StackExchange.ifUsing("editor", function ()
                StackExchange.using("externalEditor", function ()
                StackExchange.using("snippets", function ()
                StackExchange.snippets.init();
                );
                );
                , "code-snippets");

                StackExchange.ready(function()
                var channelOptions =
                tags: "".split(" "),
                id: "196"
                ;
                initTagRenderer("".split(" "), "".split(" "), channelOptions);

                StackExchange.using("externalEditor", function()
                // Have to fire editor after snippets, if snippets enabled
                if (StackExchange.settings.snippets.snippetsEnabled)
                StackExchange.using("snippets", function()
                createEditor();
                );

                else
                createEditor();

                );

                function createEditor()
                StackExchange.prepareEditor(
                heartbeatType: 'answer',
                autoActivateHeartbeat: false,
                convertImagesToLinks: false,
                noModals: true,
                showLowRepImageUploadWarning: true,
                reputationToPostImages: null,
                bindNavPrevention: true,
                postfix: "",
                imageUploader:
                brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
                contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
                allowUrls: true
                ,
                onDemand: true,
                discardSelector: ".discard-answer"
                ,immediatelyShowMarkdownHelp:true
                );



                );













                draft saved

                draft discarded


















                StackExchange.ready(
                function ()
                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f216535%2fmethod-for-adding-error-messages-to-a-dictionary-given-a-key%23new-answer', 'question_page');

                );

                Post as a guest















                Required, but never shown

























                3 Answers
                3






                active

                oldest

                votes








                3 Answers
                3






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                8












                $begingroup$

                Consider narrowing accepted types



                This might not be possible based on the context of your code, but if it is: arguments sharing one of many different types hinders and complicates testability and maintainability. There are many different solutions to this that will help this situation; one is accepting variadic arguments - i.e.



                def add_error(error_dict, key, *errs):


                This is still easily invocable without needing to wrap a single error in a list.



                Use x not in instead of not x in



                i.e.



                if key not in error_dict


                Lose your loop



                and also lose your empty-list assignment, instead doing



                error_dict.setdefault(key, []).extend(err)


                If you use the variadic suggestion above, your entire function becomes that one line.



                Immutable or not?



                Currently you do two things - alter a dictionary and return it - when you should only pick one. Either make a copy of the dict and return an altered version, or modify the dict and don't return anything.






                share|improve this answer









                $endgroup$

















                  8












                  $begingroup$

                  Consider narrowing accepted types



                  This might not be possible based on the context of your code, but if it is: arguments sharing one of many different types hinders and complicates testability and maintainability. There are many different solutions to this that will help this situation; one is accepting variadic arguments - i.e.



                  def add_error(error_dict, key, *errs):


                  This is still easily invocable without needing to wrap a single error in a list.



                  Use x not in instead of not x in



                  i.e.



                  if key not in error_dict


                  Lose your loop



                  and also lose your empty-list assignment, instead doing



                  error_dict.setdefault(key, []).extend(err)


                  If you use the variadic suggestion above, your entire function becomes that one line.



                  Immutable or not?



                  Currently you do two things - alter a dictionary and return it - when you should only pick one. Either make a copy of the dict and return an altered version, or modify the dict and don't return anything.






                  share|improve this answer









                  $endgroup$















                    8












                    8








                    8





                    $begingroup$

                    Consider narrowing accepted types



                    This might not be possible based on the context of your code, but if it is: arguments sharing one of many different types hinders and complicates testability and maintainability. There are many different solutions to this that will help this situation; one is accepting variadic arguments - i.e.



                    def add_error(error_dict, key, *errs):


                    This is still easily invocable without needing to wrap a single error in a list.



                    Use x not in instead of not x in



                    i.e.



                    if key not in error_dict


                    Lose your loop



                    and also lose your empty-list assignment, instead doing



                    error_dict.setdefault(key, []).extend(err)


                    If you use the variadic suggestion above, your entire function becomes that one line.



                    Immutable or not?



                    Currently you do two things - alter a dictionary and return it - when you should only pick one. Either make a copy of the dict and return an altered version, or modify the dict and don't return anything.






                    share|improve this answer









                    $endgroup$



                    Consider narrowing accepted types



                    This might not be possible based on the context of your code, but if it is: arguments sharing one of many different types hinders and complicates testability and maintainability. There are many different solutions to this that will help this situation; one is accepting variadic arguments - i.e.



                    def add_error(error_dict, key, *errs):


                    This is still easily invocable without needing to wrap a single error in a list.



                    Use x not in instead of not x in



                    i.e.



                    if key not in error_dict


                    Lose your loop



                    and also lose your empty-list assignment, instead doing



                    error_dict.setdefault(key, []).extend(err)


                    If you use the variadic suggestion above, your entire function becomes that one line.



                    Immutable or not?



                    Currently you do two things - alter a dictionary and return it - when you should only pick one. Either make a copy of the dict and return an altered version, or modify the dict and don't return anything.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Mar 30 at 20:36









                    ReinderienReinderien

                    5,445927




                    5,445927























                        5












                        $begingroup$

                        congratulations on writing a fairly clear, readable function! (And welcome!)



                        What types do you take?



                        You explicitly check for an instance of type list. I think you should invert your check, and look for a string type instead. The reason is that it would enable you to accept iterables other than list as your errors.



                        For example, you would be able to do something like:



                        add_error(edict, 'key', (str(e) for e in ...))


                        That last parameter is not a list, but it is something you might want to do. Also, *args is not a list but a tuple - you might want to splat a tuple rather than converting it to a list first.



                        What types do you take?



                        Your key parameter is always tested as a string. But dicts can have other key-types than string, and you neither test those, nor do you appear to have coded any kind of rejection on that basis. I suggest you add some tests that demonstrate your intent: is it okay to use non-strings as keys, or not?



                        What constraints exist on the errors?



                        I don't see any indication of what happens when duplicate errors are added. Is this intended to be allowed, or not?



                        What constraints exist on the keys?



                        Is it okay to use None as a key? How about '' (empty string)? Tests, please.






                        share|improve this answer









                        $endgroup$

















                          5












                          $begingroup$

                          congratulations on writing a fairly clear, readable function! (And welcome!)



                          What types do you take?



                          You explicitly check for an instance of type list. I think you should invert your check, and look for a string type instead. The reason is that it would enable you to accept iterables other than list as your errors.



                          For example, you would be able to do something like:



                          add_error(edict, 'key', (str(e) for e in ...))


                          That last parameter is not a list, but it is something you might want to do. Also, *args is not a list but a tuple - you might want to splat a tuple rather than converting it to a list first.



                          What types do you take?



                          Your key parameter is always tested as a string. But dicts can have other key-types than string, and you neither test those, nor do you appear to have coded any kind of rejection on that basis. I suggest you add some tests that demonstrate your intent: is it okay to use non-strings as keys, or not?



                          What constraints exist on the errors?



                          I don't see any indication of what happens when duplicate errors are added. Is this intended to be allowed, or not?



                          What constraints exist on the keys?



                          Is it okay to use None as a key? How about '' (empty string)? Tests, please.






                          share|improve this answer









                          $endgroup$















                            5












                            5








                            5





                            $begingroup$

                            congratulations on writing a fairly clear, readable function! (And welcome!)



                            What types do you take?



                            You explicitly check for an instance of type list. I think you should invert your check, and look for a string type instead. The reason is that it would enable you to accept iterables other than list as your errors.



                            For example, you would be able to do something like:



                            add_error(edict, 'key', (str(e) for e in ...))


                            That last parameter is not a list, but it is something you might want to do. Also, *args is not a list but a tuple - you might want to splat a tuple rather than converting it to a list first.



                            What types do you take?



                            Your key parameter is always tested as a string. But dicts can have other key-types than string, and you neither test those, nor do you appear to have coded any kind of rejection on that basis. I suggest you add some tests that demonstrate your intent: is it okay to use non-strings as keys, or not?



                            What constraints exist on the errors?



                            I don't see any indication of what happens when duplicate errors are added. Is this intended to be allowed, or not?



                            What constraints exist on the keys?



                            Is it okay to use None as a key? How about '' (empty string)? Tests, please.






                            share|improve this answer









                            $endgroup$



                            congratulations on writing a fairly clear, readable function! (And welcome!)



                            What types do you take?



                            You explicitly check for an instance of type list. I think you should invert your check, and look for a string type instead. The reason is that it would enable you to accept iterables other than list as your errors.



                            For example, you would be able to do something like:



                            add_error(edict, 'key', (str(e) for e in ...))


                            That last parameter is not a list, but it is something you might want to do. Also, *args is not a list but a tuple - you might want to splat a tuple rather than converting it to a list first.



                            What types do you take?



                            Your key parameter is always tested as a string. But dicts can have other key-types than string, and you neither test those, nor do you appear to have coded any kind of rejection on that basis. I suggest you add some tests that demonstrate your intent: is it okay to use non-strings as keys, or not?



                            What constraints exist on the errors?



                            I don't see any indication of what happens when duplicate errors are added. Is this intended to be allowed, or not?



                            What constraints exist on the keys?



                            Is it okay to use None as a key? How about '' (empty string)? Tests, please.







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Mar 30 at 22:07









                            Austin HastingsAustin Hastings

                            7,7371236




                            7,7371236





















                                0












                                $begingroup$

                                Type Hints



                                Based on your doctests, you must be using Python 3.6 or later (due to reliance on dictionary key order).



                                Since Python 3.5+ includes support for type hints, you could declare you function as:



                                def add_error(error_dict: dict, key: str, err: list) -> dict:


                                Or



                                from typing import List, Dict

                                def add_error(error_dict: Dict[str, List[str]], key: str,
                                err: List[str]) -> Dict[str]:


                                Of course, modify the type hints if you take the argument changes suggested in other answers. In particular, as is, the type of err is actually a variant type. I’d prefer a variable list of strings, *err: str.



                                Detect Errors before Modifying



                                If an error is not a string, you will raise an exception. But first, if the key does not exist in the dictionary, you add an empty list for that key.



                                If the error list contains strings before a non-string, you add those strings to the key’s list, then raise an exception part way through.



                                Consider moving the checks up to the start of the function, before any changes have been made.



                                if any(not isinstance(e, string_types) for e in err):
                                raise TypeError("The error(s) must be a string, or list of strings")


                                Duck Typing



                                Why must the errors be a string? Any object can be converted to a string...






                                share|improve this answer











                                $endgroup$

















                                  0












                                  $begingroup$

                                  Type Hints



                                  Based on your doctests, you must be using Python 3.6 or later (due to reliance on dictionary key order).



                                  Since Python 3.5+ includes support for type hints, you could declare you function as:



                                  def add_error(error_dict: dict, key: str, err: list) -> dict:


                                  Or



                                  from typing import List, Dict

                                  def add_error(error_dict: Dict[str, List[str]], key: str,
                                  err: List[str]) -> Dict[str]:


                                  Of course, modify the type hints if you take the argument changes suggested in other answers. In particular, as is, the type of err is actually a variant type. I’d prefer a variable list of strings, *err: str.



                                  Detect Errors before Modifying



                                  If an error is not a string, you will raise an exception. But first, if the key does not exist in the dictionary, you add an empty list for that key.



                                  If the error list contains strings before a non-string, you add those strings to the key’s list, then raise an exception part way through.



                                  Consider moving the checks up to the start of the function, before any changes have been made.



                                  if any(not isinstance(e, string_types) for e in err):
                                  raise TypeError("The error(s) must be a string, or list of strings")


                                  Duck Typing



                                  Why must the errors be a string? Any object can be converted to a string...






                                  share|improve this answer











                                  $endgroup$















                                    0












                                    0








                                    0





                                    $begingroup$

                                    Type Hints



                                    Based on your doctests, you must be using Python 3.6 or later (due to reliance on dictionary key order).



                                    Since Python 3.5+ includes support for type hints, you could declare you function as:



                                    def add_error(error_dict: dict, key: str, err: list) -> dict:


                                    Or



                                    from typing import List, Dict

                                    def add_error(error_dict: Dict[str, List[str]], key: str,
                                    err: List[str]) -> Dict[str]:


                                    Of course, modify the type hints if you take the argument changes suggested in other answers. In particular, as is, the type of err is actually a variant type. I’d prefer a variable list of strings, *err: str.



                                    Detect Errors before Modifying



                                    If an error is not a string, you will raise an exception. But first, if the key does not exist in the dictionary, you add an empty list for that key.



                                    If the error list contains strings before a non-string, you add those strings to the key’s list, then raise an exception part way through.



                                    Consider moving the checks up to the start of the function, before any changes have been made.



                                    if any(not isinstance(e, string_types) for e in err):
                                    raise TypeError("The error(s) must be a string, or list of strings")


                                    Duck Typing



                                    Why must the errors be a string? Any object can be converted to a string...






                                    share|improve this answer











                                    $endgroup$



                                    Type Hints



                                    Based on your doctests, you must be using Python 3.6 or later (due to reliance on dictionary key order).



                                    Since Python 3.5+ includes support for type hints, you could declare you function as:



                                    def add_error(error_dict: dict, key: str, err: list) -> dict:


                                    Or



                                    from typing import List, Dict

                                    def add_error(error_dict: Dict[str, List[str]], key: str,
                                    err: List[str]) -> Dict[str]:


                                    Of course, modify the type hints if you take the argument changes suggested in other answers. In particular, as is, the type of err is actually a variant type. I’d prefer a variable list of strings, *err: str.



                                    Detect Errors before Modifying



                                    If an error is not a string, you will raise an exception. But first, if the key does not exist in the dictionary, you add an empty list for that key.



                                    If the error list contains strings before a non-string, you add those strings to the key’s list, then raise an exception part way through.



                                    Consider moving the checks up to the start of the function, before any changes have been made.



                                    if any(not isinstance(e, string_types) for e in err):
                                    raise TypeError("The error(s) must be a string, or list of strings")


                                    Duck Typing



                                    Why must the errors be a string? Any object can be converted to a string...







                                    share|improve this answer














                                    share|improve this answer



                                    share|improve this answer








                                    edited Mar 30 at 23:37

























                                    answered Mar 30 at 22:55









                                    AJNeufeldAJNeufeld

                                    6,8641722




                                    6,8641722



























                                        draft saved

                                        draft discarded
















































                                        Thanks for contributing an answer to Code Review Stack Exchange!


                                        • Please be sure to answer the question. Provide details and share your research!

                                        But avoid


                                        • Asking for help, clarification, or responding to other answers.

                                        • Making statements based on opinion; back them up with references or personal experience.

                                        Use MathJax to format equations. MathJax reference.


                                        To learn more, see our tips on writing great answers.




                                        draft saved


                                        draft discarded














                                        StackExchange.ready(
                                        function ()
                                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f216535%2fmethod-for-adding-error-messages-to-a-dictionary-given-a-key%23new-answer', 'question_page');

                                        );

                                        Post as a guest















                                        Required, but never shown





















































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown

































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown







                                        Popular posts from this blog

                                        Triangular numbers and gcdProving sum of a set is $0 pmod n$ if $n$ is odd, or $fracn2 pmod n$ if $n$ is even?Is greatest common divisor of two numbers really their smallest linear combination?GCD, LCM RelationshipProve a set of nonnegative integers with greatest common divisor 1 and closed under addition has all but finite many nonnegative integers.all pairs of a and b in an equation containing gcdTriangular Numbers Modulo $k$ - Hit All Values?Understanding the Existence and Uniqueness of the GCDGCD and LCM with logical symbolsThe greatest common divisor of two positive integers less than 100 is equal to 3. Their least common multiple is twelve times one of the integers.Suppose that for all integers $x$, $x|a$ and $x|b$ if and only if $x|c$. Then $c = gcd(a,b)$Which is the gcd of 2 numbers which are multiplied and the result is 600000?

                                        Ingelân Ynhâld Etymology | Geografy | Skiednis | Polityk en bestjoer | Ekonomy | Demografy | Kultuer | Klimaat | Sjoch ek | Keppelings om utens | Boarnen, noaten en referinsjes Navigaasjemenuwww.gov.ukOffisjele webside fan it regear fan it Feriene KeninkrykOffisjele webside fan it Britske FerkearsburoNederlânsktalige ynformaasje fan it Britske FerkearsburoOffisjele webside fan English Heritage, de organisaasje dy't him ynset foar it behâld fan it Ingelske kultuergoedYnwennertallen fan alle Britske stêden út 'e folkstelling fan 2011Notes en References, op dizze sideEngland

                                        Հադիս Բովանդակություն Անվանում և նշանակություն | Դասակարգում | Աղբյուրներ | Նավարկման ցանկ