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

Groups > comp.lang.python > #95336 > unrolled thread

Re: Hooking Mechanism when Entering and Leaving a Try Block

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Hooking Mechanism when Entering and Leaving a Try Block Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-08-13 09:34 +0100
    [OT] How to post properly (was: Re: Hooking Mechanism when Entering and Leaving a Try Block) Marko Rauhamaa <marko@pacujo.net> - 2015-08-13 12:09 +0300
      Re: [Meta] How to post properly (was: Re: Hooking Mechanism when Entering and Leaving a Try Block) Steven D'Aprano <steve@pearwood.info> - 2015-08-14 09:15 +1000

#95336 — Re: Hooking Mechanism when Entering and Leaving a Try Block

On 13/08/2015 07:26, Sven R. Kunze wrote:
> On 13.08.2015 02:45, Chris Angelico wrote:
>> On Thu, Aug 13, 2015 at 6:54 AM, Mark Lawrence<breamoreboy@yahoo.co.uk>  wrote:
>>> On 12/08/2015 19:44, Sven R. Kunze wrote:
>>>> On 12.08.2015 18:11, Chris Angelico wrote:
>>>>> (Please don't top-post.)
>>>>
>>>> Is this some guideline? I actually quite dislike pick somebody's mail to
>>>> pieces. It actually pulls things out of context. But if this is a rule
>>>> for this, so be it.
>>>>
>>> The rules here are very simple.  Snip what you don't wish to reply to (yes I
>>> know I forget sometimes), intersperse your answers to what you do want to
>>> respond to.
>> As Mark says, the key is to intersperse your answers with the context.
>> In some email clients, you can highlight a block of text and hit
>> Reply, and it'll quote only that text. (I was so happy when Gmail
>> introduced that feature. It was the one thing I'd been most missing
>> from it.)
>>
>> ChrisA
>
> So, I take this as a "my personal preference guideline" because I cannot
> find an official document for this (maybe, I am looking at the wrong
> places).
>

This is a community list.  The rule has been no top posting here for the 
15 years I've been using Python.  I find trying to follow the really 
long threads on python-dev or python-ideas almost impossible as there is 
no rule, so you're up and down responses like a yo-yo.

> In order to keep you happy, I perform this ancient type communication
> where the most relevant information (i.e. the new one) is either to find
> at the bottom (scrolling is such fun) OR hidden between the lines
> (wasting time is even more fun these days).

What rubbish.  Just because some people have been brainwashed into 
writing English incorrectly by their using M$ Outlook doesn't mean that 
the rest of the world has to follow suit.  If you don't want to work so 
hard to use this list then simply don't bother coming here, I doubt that 
the list will miss you.

> Btw. to me, the *context is the entire post*, not just two lines. I hate
> if people answer me on every single word I've written and try to explain
> what've got wrong instead of trying to understand the message and my
> perspective as a whole. I find it very difficult to respond to such a
> post and I am inclined to completely start from an empty post.

Which is why we prefer interspersed posting such as this.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask
what you can do for our language.

Mark Lawrence

[toc] | [next] | [standalone]

#95338 — [OT] How to post properly (was: Re: Hooking Mechanism when Entering and Leaving a Try Block)

Mark Lawrence <breamoreboy@yahoo.co.uk>:

> The rule has been no top posting here for the 15 years I've been using
> Python.

Top posting is simply annoying.

However, I'd like people to also stick to another rule: only quote a few
lines. I should start seeing your contribution to the discussion without
scrolling because those few lines help me decide if I should skip the
posting altogether. (Well, if I can't see any original content at once,
I'll skip the posting.)

A third rule, which I'm violating here myself, is stick to
Python-related topics on this newsgroup.


Marko

[toc] | [prev] | [next] | [standalone]

#95359 — Re: [Meta] How to post properly (was: Re: Hooking Mechanism when Entering and Leaving a Try Block)

On Thu, 13 Aug 2015 07:09 pm, Marko Rauhamaa wrote:

> A third rule, which I'm violating here myself, is stick to
> Python-related topics on this newsgroup.

On the sorts of places that take these sorts of fine distinctions seriously,
your post would be considered Meta rather than Off-topic. That is:

- posts about the main topic (here, that would be Python) are on-topic;

- posts about posting are meta;

- everything else is off-topic.

We have a reasonable tolerance to off-topic discussions, particularly if
they evolve naturally from an on-topic one.



-- 
Steven

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web