Re: im.py: a python communications tool

References	(11 earlier) <CAPTjJmqSBmvVZCTyBLyrzw7RfU-QWK48fBLcncR5Qju62GG2OA@mail.gmail.com> <mailman.324.1365493163.3114.python-list@python.org> <5163d1d0$0$29977$c3e8da3$5496439d@news.astraweb.com> <mailman.332.1365497906.3114.python-list@python.org> <kk19ap$2vs$1@reader1.panix.com>
Date	2013-04-09 09:36 -0700
Subject	Re: im.py: a python communications tool
From	Mark Janssen <dreamingforward@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.374.1365529242.3114.python-list@python.org> (permalink)

Show all headers | View raw

> Are there that many people in the country who have no clue how the
> legal system works?

Gads.  I'm trying to show you how the legal system *doesn't* work.
All your points may be valid under court history, but that history is
tainted.  It doesn't mean the system is working, only that cases have
been decided.  And the court should not be ruling on issues of such
accidents because guilt cannot established ("accidents" where there
was no intention of harm, nor tacit agreement made between any
parties)  like a person giving a rose to their neighbor in an act of
good will.  Such events should use mediators, not judges because their
is no *law* to be decided.  The judges, or course, can act as
mediators, but the court system seems bogged down enough already.

I mean really, a good-will act?  The Good Samaritan rules already
establish that you can't sue people for good faith acts.  Do you
really want a world where *good intentions* are penalized?  Come on --
that's why the system is broken and shame on every citizen that
continues this error in system of the People.  It doesn't matter if
people get harmed, as long as good faith is in place before and after
the event.  The "system" shouldn't get dragged in because you want to
act like a child and get your daddy to help you.

Mark

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