<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I approve of the sentiment, but it seems to me that the unlicense is
    most definitely a LICENSE. Putting legal terms and conditions, or
    waiver of same, into a differently named file, seems a step too far.<br>
    <br>
    Nevertheless, sounds cool to me, I'll read up and consider using it.
    Thanks!<br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 06/10/13 22:45, Harry Percival
      wrote:<br>
    </div>
    <blockquote
cite="mid:CACFvh99KO0F7X_tXZiS4FvHGHsNT7HQTgePWdeF9GQnP+T6thw@mail.gmail.com"
      type="cite">
      <div dir="ltr">apologies for resurrecting a dead thread, but i
        came across this license and was impressed:<br>
        <br>
        <a moz-do-not-send="true" href="http://unlicense.org/">http://unlicense.org/</a><br>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">
          On 12 September 2013 20:08, John Lee <span dir="ltr"><<a
              moz-do-not-send="true" href="mailto:jjl@pobox.com"
              target="_blank">jjl@pobox.com</a>></span> wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            On Wed, 11 Sep 2013, Jonathan Hartley wrote:<br>
            [...]
            <div class="im"><br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  I've seen it done in a special "coding style test
                  suite" (that gets run along with all the other tests).
                   Slightly nicer than a push hook IMO because you see
                  it earlier and because it works the same way as all
                  your other automated tests of your code.  There was a
                  bit of special code so that you got one failure per
                  coding style violation I think (including one per
                  missing copyright statement), but those are bonus
                  points.<br>
                  <br>
                  Maybe somebody has written a test runner plugin that
                  does that? My quick searches didn't turn one up,
                  though there is this, which could easily be adapted
                  (not a plugin, and looks like it wants to be)<br>
                  <br>
                  <a moz-do-not-send="true"
href="http://stackoverflow.com/questions/12227443/is-there-a-plugin-for-pylint-and-pyflakes-for-nose-tests"
                    target="_blank">http://stackoverflow.com/questions/12227443/is-there-a-plugin-for-pylint-and-pyflakes-for-nose-tests</a>
                  <br>
                  <br>
                  John<br>
                  _______________________________________________<br>
                  python-uk mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:python-uk@python.org" target="_blank">python-uk@python.org</a><br>
                  <a moz-do-not-send="true"
                    href="https://mail.python.org/mailman/listinfo/python-uk"
                    target="_blank">https://mail.python.org/mailman/listinfo/python-uk</a><br>
                </blockquote>
                <br>
                <br>
                I don't think it should be a test runner plugin, so much
                as just a test. Maybe a big common utility function (in
                a pypi package) which a tiny custom test function can
                then call to parametrize it for your project.<br>
              </blockquote>
              <br>
            </div>
            That works.  The reason I suggested a plugin was so that
            plugin hooks can give the coding style check function the
            modules (and scripts) on which to operate.
            <div class="HOEnZb">
              <div class="h5"><br>
                <br>
                <br>
                John<br>
                _______________________________________________<br>
                python-uk mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:python-uk@python.org" target="_blank">python-uk@python.org</a><br>
                <a moz-do-not-send="true"
                  href="https://mail.python.org/mailman/listinfo/python-uk"
                  target="_blank">https://mail.python.org/mailman/listinfo/python-uk</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <br>
        -- <br>
        ------------------------------<br>
        Harry J.W. Percival<br>
        ------------------------------<br>
        Twitter: @hjwp<br>
        Mobile:  +44 (0) 78877 02511<br>
        Skype:         harry.percival
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
python-uk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:python-uk@python.org">python-uk@python.org</a>
<a class="moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/python-uk">https://mail.python.org/mailman/listinfo/python-uk</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Jonathan Hartley    <a class="moz-txt-link-abbreviated" href="mailto:tartley@tartley.com">tartley@tartley.com</a>    <a class="moz-txt-link-freetext" href="http://tartley.com">http://tartley.com</a>
Made of meat.       +44 7737 062 225       twitter/skype: tartley

</pre>
  </body>
</html>