Re: im.py: a python communications tool

References	(9 earlier) <CAPTjJmqxns1dDbHVvu7_T7Zxf_UROcWnhxWWctaaAsRndVTy9g@mail.gmail.com> <mailman.321.1365492029.3114.python-list@python.org> <5163c578$0$29977$c3e8da3$5496439d@news.astraweb.com> <mailman.327.1365494541.3114.python-list@python.org> <5163da98$0$29977$c3e8da3$5496439d@news.astraweb.com>
Date	2013-04-09 02:29 -0700
Subject	Re: im.py: a python communications tool
From	Mark Janssen <dreamingforward@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.335.1365499791.3114.python-list@python.org> (permalink)

Show all headers | View raw

> And by putting it online for free download, IN THE ABSENCE OF AN EXPLICIT
> DISCLAIMER, you are implying that it is fit for its purpose, and that you
> have a duty of care to make sure that it does do what you say it does.

No, there is no requirement for a disclaimer.  In the US, what is not
explicitly restricted by the law is withheld by the citizen.  I don't
have to give a disclaimer if my intentions are in good faith.

And further, I'm not saying that it's fit for a purpose in some
trade-like agreement.  So I'm not in possible breach of any agreement
whatsoever.

> If you go into a restaurant, and they have bowls of breadsticks free for
> people to eat, and you eat one, and it had a needle in it and you stabbed
> yourself and got infected, don't you think that the restaurant ought to
> take responsibility for their carelessness?

If I go to a freebiebox placed outside a restaurant with such, no, I'm
taking responsibility.  "Caveat emptor" as they say and here's there's
no buyer.
If I go to a table and there are free breadstix on the table and start
eating them without intentions to pay, then I'm the shithole.
If I get infected from some food at a restaurant which I paid for,
then each side will have to argue their case.  The court may find
negligence on the side of the restaurant, or it may not.

> Don't you think that it is
> pretty shitty, weaselly behaviour for them to say "But you didn't pay for
> the breadstick! We never promised that it wouldn't contain an AIDS-
> infected needle!"

Hey, you know it's expected that if someone gets hurt from something
you provided, but you didnt' intend it on them and didn't make any
money off of them, that you still say you're sorry.  Each person in a
government of the people is expected to do their fair part in using
commonsense.  The courts can't deal with every little squabble.

> The principle is the same. There is an implied warranty that a breadstick
> will not contain infected needles, and that software will do what you say
> it does.

No to the latter.  As for the former, if I'm at a restaurant I'm
entering a business relationship.  The cost of the  breadsticks are
already bundled in the other food you are *expected* to order.

>   WARNING: Breadsticks in this restaurant may contain infected needles.
>   Eat at your own risk!

Here again your letting the Novus Ordo "market mentality" dominate
your thinking when it should be on about person-to-person simple
interactions.  Unless of course, you've allowed corporations to be
people, and your in a corporate restaurant, please no.

>> Okay, if the TV show disconnected the brake lines, there could be
>> argument of criminal negligence on her production, but otherwise the car
>> company could be sued.   You don't sue Oprah because she's not the one
>> who designed it.
>
> That will surely depend on the jurisdiction. Some places may reason that
> your relationship was with Oprah (to be precise, her production company
> that actually gave you the car), that she had a duty of care, and so it
> is her that you should sue. It is then Oprah's responsibility to sue the
> manufacturer.

Well, out here in the good ol' USA, there no "duty of care", because
you're not a child being taken care of and Oprah is not someone acting
"in loco parentis".   The 14th(?) amendment give equal treatment under
the law, there's no duty of care unless you can argue that it's
expected of your adult ass getting on TV.

MarkJ

Thread

im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-05 17:16 -0700
  Re: im.py: a python communications tool Demian Brecht <demianbrecht@gmail.com> - 2013-04-05 17:52 -0700
    Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-06 08:35 -0700
  Re: im.py: a python communications tool Roy Smith <roy@panix.com> - 2013-04-05 21:07 -0400
    Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-05 18:13 -0700
    Re: im.py: a python communications tool Andrew Berg <bahamutzero8825@gmail.com> - 2013-04-05 20:26 -0500
      Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-06 07:54 -0700
      Re: im.py: a python communications tool garabik-news-2005-05@kassiopeia.juls.savba.sk - 2013-04-07 08:59 +0000
        Re: im.py: a python communications tool jhunter.dunefsky@gmail.com - 2013-04-07 14:47 -0700
          Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-07 22:36 +0000
            Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-08 13:00 +1000
            Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-08 03:48 -0700
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-08 16:16 -0700
            Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-08 22:05 -0400
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-08 20:37 -0700
            Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-09 02:04 -0400
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-08 23:20 -0700
              Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 06:47 +0000
            Re: im.py: a python communications tool Demian Brecht <demianbrecht@gmail.com> - 2013-04-08 23:42 -0700
            Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-09 02:42 -0400
            Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 17:14 +1000
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 00:20 -0700
              Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 07:38 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 01:02 -0700
                Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 09:08 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:29 -0700
                Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 13:05 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-12 12:57 -0700
                Re: im.py: a python communications tool Neil Cerutti <neilc@norwich.edu> - 2013-04-12 20:05 +0000
                RE: im.py: a python communications tool "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2013-04-12 21:48 +0000
                RE: im.py: a python communications tool "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2013-04-12 19:46 +0000
            Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 17:21 +1000
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 00:39 -0700
              Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 08:31 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 01:58 -0700
                Re: im.py: a python communications tool Grant Edwards <invalid@invalid.invalid> - 2013-04-09 14:41 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 09:36 -0700
                Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 19:40 +1000
                Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 13:03 +0000
                Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 23:23 +1000
                Re: im.py: a python communications tool Chris Angelico <rosuav@gmail.com> - 2013-04-09 19:48 +1000
                Re: im.py: a python communications tool Jake D <jhunter.dunefsky@gmail.com> - 2013-04-09 04:09 -0700
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:46 -0700
              Re: im.py: a python communications tool Grant Edwards <invalid@invalid.invalid> - 2013-04-09 14:30 +0000
            Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 01:15 -0700
              Re: im.py: a python communications tool Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-04-09 08:45 +0000
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:00 -0700
                Re: im.py: a python communications tool Dave Angel <davea@davea.name> - 2013-04-09 05:18 -0400
                Re: im.py: a python communications tool Mark Janssen <dreamingforward@gmail.com> - 2013-04-09 02:32 -0700
            Re: im.py: a python communications tool Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-04-09 17:10 +0100

csiph-web