Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.021 X-Spam-Evidence: '*H*': 0.96; '*S*': 0.00; 'context': 0.05; 'distributing': 0.07; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'referenced': 0.09; 'respond.': 0.09; 'sep': 0.09; 'propagated': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'summarize': 0.16; 'usenet': 0.16; 'thu,': 0.17; 'context.': 0.22; 'logical': 0.22; 'posts': 0.23; 'seems': 0.23; 'host': 0.24; 'header:X-Complaints-To:1': 0.28; 'post': 0.28; 'point': 0.31; 'server.': 0.32; 'could': 0.32; 'everyone.': 0.33; 'url:home': 0.33; 'to:addr:python-list': 0.33; 'text': 0.34; 'posting': 0.35; 'subject:?': 0.35; 'received:org': 0.36; 'but': 0.36; 'url:org': 0.36; 'should': 0.36; 'charset:us- ascii': 0.36; 'enough': 0.36; 'possible': 0.37; 'does': 0.37; 'subject:: ': 0.38; 'sure': 0.38; 'to:addr:python.org': 0.39; 'list,': 0.39; 'header:Received:5': 0.40; 'your': 0.60; 'most': 0.61; 'time,': 0.62; 'helps': 0.63; 'readers': 0.65; 'reply': 0.66; 'e-mail,': 0.66; 'response.': 0.67; 'asked.': 0.84; 'original.': 0.84; 'taken.': 0.84; "they'd": 0.84; 'dennis': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Dennis Lee Bieber Subject: Re: pythonOCC examples doesn't work? Date: Thu, 13 Sep 2012 22:55:51 -0400 Organization: > Bestiaria Support Staff < References: <5B80DD153D7D744689F57F4FB69AF47416678FC5@SCACMX008.exchad.jpmchase.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: adsl-76-253-102-123.dsl.klmzmi.sbcglobal.net X-Newsreader: Forte Agent 3.3/32.846 X-No-Archive: YES X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 40 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1347591352 news.xs4all.nl 6884 [2001:888:2000:d::a6]:45124 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:29104 On Thu, 13 Sep 2012 21:11:58 -0400, Dwight Hutto declaimed the following in gmane.comp.python.general: > > Your point is taken. Most of the time, if it's in an in line response > I would write the email line by line, with the referenced text shown > above my response. > > However, when it seems like a conversation, I just trim the above, and > respond. That's how I view an e-mail, like an ongoing conversation. > If it were a private email -- you to the OP -- that would be reasonable; they should know what they'd asked. However... This is a cross-linked Usenet <> mailing list, and Usenet does not guarantee that all posts will arrive in logical order... It is possible that once could see your response BEFORE the OP's post has propagated to the same Usenet server. http://www.ietf.org/rfc/rfc1855.txt Section three applies. rfc> - If you are sending a reply to a message or a posting be sure you rfc> summarize the original at the top of the message, or include just rfc> enough text of the original to give a context. This will make rfc> sure readers understand when they start to read your response. rfc> Since NetNews, especially, is proliferated by distributing the rfc> postings from one host to another, it is possible to see a rfc> response to a message before seeing the original. Giving context rfc> helps everyone. But do not include the entire original! -- Wulfraed Dennis Lee Bieber AF6VN wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/