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

Groups > comp.lang.python > #109484

Re: Don't put your software in the public domain

From Terry Reedy <tjreedy@udel.edu>
Newsgroups comp.lang.python
Subject Re: Don't put your software in the public domain
Date 2016-06-04 15:12 -0400
Message-ID <mailman.0.1465067564.2306.python-list@python.org> (permalink)
References (3 earlier) <c32d2b5f-77f6-49fa-b285-572696397939@googlegroups.com> <pan.2016.06.03.21.00.59.976000@nowhere.invalid> <87eg8d4dss.fsf@rudin.co.uk> <87a8j19xb0.fsf@elektro.pacujo.net> <niv96d$44k$1@ger.gmane.org>

Show all headers | View raw

On 6/4/2016 4:24 AM, Marko Rauhamaa wrote:
> Paul Rudin <paul.nospam@rudin.co.uk>:
>
>> Don't confuse consideration with agreement - they're seperate legal
>> concepts.
>>
>> Agreement is certainly necessary in pretty much all jurisdictions.
>> Consideration is required in most common law jurisdiction (England,
>> the US, most of the commonwealth) but not in many continental legal
>> systems.
>
> Thankfully, I live in a jurisdiction where things are simpler. I've
> actually successfully represented a relative in a court of law without
> any legal training.
>
> In Finland, it is common for families to have a printed copy of the law
> on the bookshelf.

How wonderful that 'the law' can fit in a book.  English-speaking common 
law commentaries once had Blackstone's 4 volume Commentaries 
(https://en.wikipedia.org/wiki/William_Blackstone#Commentaries_on_the_Laws_of_England), 
but bookshelve of statute laws seem to have overwhelmed that, at least 
in the US.

 > Families traditionally sort out things like
> inheritances without the involvement of lawyers. Nowadays, the law is
> available online, of course.

For free, I presume.  I just discovered that the Delaware Code is now 
online http://delcode.delaware.gov/index.shtml.


-- 
Terry Jan Reedy

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-02 00:59 +1000
  Re: Don't put your software in the public domain Marko Rauhamaa <marko@pacujo.net> - 2016-06-01 18:44 +0300
  Re: Don't put your software in the public domain Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-01 13:45 -0700
    Re: Don't put your software in the public domain John Wong <gokoproject@gmail.com> - 2016-06-01 17:00 -0400
      Re: Don't put your software in the public domain Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2016-06-02 13:38 +1000
    Re: Don't put your software in the public domain Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2016-06-02 13:43 +1000
  Re: Don't put your software in the public domain Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-06-02 18:41 +1200
    Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-02 21:56 +1000
      Re: Don't put your software in the public domain Chris Angelico <rosuav@gmail.com> - 2016-06-02 22:04 +1000
        Re: Don't put your software in the public domain Marko Rauhamaa <marko@pacujo.net> - 2016-06-02 15:26 +0300
          Re: Don't put your software in the public domain Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-02 18:11 -0700
    Re: Don't put your software in the public domain Robin Becker <robin@reportlab.com> - 2016-06-02 13:52 +0100
    Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-03 19:53 +1000
      Re: Don't put your software in the public domain Michael Torrie <torriem@gmail.com> - 2016-06-03 07:14 -0600
        Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-04 12:02 +1000
          Re: Don't put your software in the public domain Random832 <random832@fastmail.com> - 2016-06-04 23:46 -0400
      Re: Don't put your software in the public domain Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-03 09:15 -0700
        Re: Don't put your software in the public domain Nobody <nobody@nowhere.invalid> - 2016-06-03 21:58 +0100
          Re: Don't put your software in the public domain Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-03 18:10 -0700
            Re: Don't put your software in the public domain Paul Rudin <paul.nospam@rudin.co.uk> - 2016-06-04 09:04 +0100
          Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-04 12:28 +1000
            Re: Don't put your software in the public domain Nobody <nobody@nowhere.invalid> - 2016-06-06 06:54 +0100
              Re: Don't put your software in the public domain Paul Rudin <paul.nospam@rudin.co.uk> - 2016-06-06 13:36 +0100
              Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-07 01:59 +1000
          Re: Don't put your software in the public domain Paul Rudin <paul.nospam@rudin.co.uk> - 2016-06-04 08:24 +0100
            Re: Don't put your software in the public domain Marko Rauhamaa <marko@pacujo.net> - 2016-06-04 11:24 +0300
              Re: Don't put your software in the public domain Terry Reedy <tjreedy@udel.edu> - 2016-06-04 15:12 -0400
                Re: Don't put your software in the public domain Marko Rauhamaa <marko@pacujo.net> - 2016-06-05 00:26 +0300
        Re: Don't put your software in the public domain Steven D'Aprano <steve@pearwood.info> - 2016-06-04 12:12 +1000
        Re: Don't put your software in the public domain Paul Rudin <paul.nospam@rudin.co.uk> - 2016-06-04 08:20 +0100

csiph-web