Method for adding error messages to a dictionary given a key The Next CEO of Stack Overflow“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

Where do students learn to solve polynomial equations these days?

Would this house-rule that treats advantage as a +1 to the roll instead (and disadvantage as -1) and allows them to stack be balanced?

What is the value of α and β in a triangle?

What happened in Rome, when the western empire "fell"?

What steps are necessary to read a Modern SSD in Medieval Europe?

How do I align (1) and (2)?

Why is quantifier elimination desirable for a given theory?

How to avoid supervisors with prejudiced views?

Is it possible to replace duplicates of a character with one character using tr

What was the first Unix version to run on a microcomputer?

Is it okay to majorly distort historical facts while writing a fiction story?

Why is the US ranked as #45 in Press Freedom ratings, despite its extremely permissive free speech laws?

Why is information "lost" when it got into a black hole?

The exact meaning of 'Mom made me a sandwich'

Example of a Mathematician/Physicist whose Other Publications during their PhD eclipsed their PhD Thesis

Chain wire methods together in Lightning Web Components

Do I need to write [sic] when a number is less than 10 but isn't written out?

How to install OpenCV on Raspbian Stretch?

Won the lottery - how do I keep the money?

How to get from Geneva Airport to Metabief?

What does "Its cash flow is deeply negative" mean?

Domestic-to-international connection at Orlando (MCO)

A Man With a Stainless Steel Endoskeleton (like The Terminator) Fighting Cloaked Aliens Only He Can See

Is a distribution that is normal, but highly skewed considered Gaussian?



Method for adding error messages to a dictionary given a key



The Next CEO of Stack Overflow“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










4












$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







New contributor




darkhorse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







$endgroup$
















    4












    $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







    New contributor




    darkhorse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.







    $endgroup$














      4












      4








      4





      $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







      New contributor




      darkhorse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.







      $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







      New contributor




      darkhorse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      darkhorse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      darkhorse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 4 hours ago









      darkhorsedarkhorse

      1584




      1584




      New contributor




      darkhorse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      darkhorse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      darkhorse is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















          2 Answers
          2






          active

          oldest

          votes


















          3












          $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$




















            2












            $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$













              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
              );



              );






              darkhorse is a new contributor. Be nice, and check out our Code of Conduct.









              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

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              3












              $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$

















                3












                $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$















                  3












                  3








                  3





                  $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 2 hours ago









                  ReinderienReinderien

                  4,975925




                  4,975925























                      2












                      $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$

















                        2












                        $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$















                          2












                          2








                          2





                          $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 44 mins ago









                          Austin HastingsAustin Hastings

                          7,5671233




                          7,5671233




















                              darkhorse is a new contributor. Be nice, and check out our Code of Conduct.









                              draft saved

                              draft discarded


















                              darkhorse is a new contributor. Be nice, and check out our Code of Conduct.












                              darkhorse is a new contributor. Be nice, and check out our Code of Conduct.











                              darkhorse is a new contributor. Be nice, and check out our Code of Conduct.














                              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

                              Are there any AGPL-style licences that require source code modifications to be public? Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Force derivative works to be publicAre there any GPL like licenses for Apple App Store?Do you violate the GPL if you provide source code that cannot be compiled?GPL - is it distribution to use libraries in an appliance loaned to customers?Distributing App for free which uses GPL'ed codeModifications of server software under GPL, with web/CLI interfaceDoes using an AGPLv3-licensed library prevent me from dual-licensing my own source code?Can I publish only select code under GPLv3 from a private project?Is there published precedent regarding the scope of covered work that uses AGPL software?If MIT licensed code links to GPL licensed code what should be the license of the resulting binary program?If I use a public API endpoint that has its source code licensed under AGPL in my app, do I need to disclose my source?

                              2013 GY136 Descoberta | Órbita | Referências Menu de navegação«List Of Centaurs and Scattered-Disk Objects»«List of Known Trans-Neptunian Objects»

                              Mortes em março de 2019 Referências Menu de navegação«Zhores Alferov, Nobel de Física bielorrusso, morre aos 88 anos - Ciência»«Fallece Rafael Torija, o bispo emérito de Ciudad Real»«Peter Hurford dies at 88»«Keith Flint, vocalista do The Prodigy, morre aos 49 anos»«Luke Perry, ator de 'Barrados no baile' e 'Riverdale', morre aos 52 anos»«Former Rangers and Scotland captain Eric Caldow dies, aged 84»«Morreu, aos 61 anos, a antiga lenda do wrestling King Kong Bundy»«Fallece el actor y director teatral Abraham Stavans»«In Memoriam Guillaume Faye»«Sidney Sheinberg, a Force Behind Universal and Spielberg, Is Dead at 84»«Carmine Persico, Colombo Crime Family Boss, Is Dead at 85»«Dirigent Michael Gielen gestorben»«Ciclista tricampeã mundial e prata na Rio 2016 é encontrada morta em casa aos 23 anos»«Pagan Community Notes: Raven Grimassi dies, Indianapolis pop-up event cancelled, Circle Sanctuary announces new podcast, and more!»«Hal Blaine, Wrecking Crew Drummer, Dies at 90»«Morre Coutinho, que editou dupla lendária com Pelé no Santos»«Cantor Demétrius, ídolo da Jovem Guarda, morre em SP»«Ex-presidente do Vasco, Eurico Miranda morre no Rio de Janeiro»«Bronze no Mundial de basquete de 1971, Laís Elena morre aos 76 anos»«Diretor de Corridas da F1, Charlie Whiting morre aos 66 anos às vésperas do GP da Austrália»«Morreu o cardeal Danneels, da Bélgica»«Morreu o cartoonista Augusto Cid»«Morreu a atriz Maria Isabel de Lizandra, de "Vale Tudo" e novelas da Tupi»«WS Merwin, prize-winning poet of nature, dies at 91»«Atriz Márcia Real morre em São Paulo aos 88 anos»«Mauritanie: décès de l'ancien président Mohamed Mahmoud ould Louly»«Morreu Dick Dale, o rei da surf guitar e de "Pulp Fiction"»«Falleció Víctor Genes»«João Carlos Marinho, autor de 'O Gênio do Crime', morre em SP»«Legendary Horror Director and SFX Artist John Carl Buechler Dies at 66»«Morre em Salvador a religiosa Makota Valdina»«مرگ بازیکن‌ سابق نساجی بر اثر سقوط سنگ در مازندران»«Domingos Oliveira morre no Rio»«Morre Airton Ravagniani, ex-São Paulo, Fla, Vasco, Grêmio e Sport - Notícias»«Morre o escritor Flavio Moreira da Costa»«Larry Cohen, Writer-Director of 'It's Alive' and 'Hell Up in Harlem,' Dies at 77»«Scott Walker, experimental singer-songwriter, dead at 76»«Joseph Pilato, Day of the Dead Star and Horror Favorite, Dies at 70»«Sheffield United set to pay tribute to legendary goalkeeper Ted Burgin who has died at 91»«Morre Rafael Henzel, sobrevivente de acidente aéreo da Chapecoense»«Morre Valery Bykovsky, um dos primeiros cosmonautas da União Soviética»«Agnès Varda, cineasta da Nouvelle Vague, morre aos 90 anos»«Agnès Varda, cineasta francesa, morre aos 90 anos»«Tania Mallet, James Bond Actress and Helen Mirren's Cousin, Dies at 77»e