From metatracker at psf.upfronthosting.co.za  Fri Jan 16 11:50:54 2009
From: metatracker at psf.upfronthosting.co.za (valentin)
Date: Fri, 16 Jan 2009 10:50:54 +0000
Subject: [Tracker-discuss] [issue232] output problem
In-Reply-To: <1232103054.65.0.124508170062.issue232@psf.upfronthosting.co.za>
Message-ID: <1232103054.65.0.124508170062.issue232@psf.upfronthosting.co.za>


New submission from valentin <jean-paul.valentin at ingenico.com>:

Feature? the output of attached Hello program looks as follows
F:\prompt>he0.py
Hello
F:\prompt>

'Hello' was sent with sys.stdout.write, so "without newline".
But why cannot be output (more logically):
F:\prompt>he0.py
HelloF:\prompt>

Is it normal? Is there any means or workaround to obtain this output if I wish??
Sorry to disturb you with such a trivial issue!

----------
files: he0.py
messages: 1131
nosy: jval
priority: feature
status: unread
title: output problem

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue232>
_______________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: he0.py
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20090116/a02a699a/attachment.txt>

From metatracker at psf.upfronthosting.co.za  Fri Jan 16 12:11:02 2009
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 16 Jan 2009 11:11:02 +0000
Subject: [Tracker-discuss] [issue232] output problem
In-Reply-To: <1232103054.65.0.124508170062.issue232@psf.upfronthosting.co.za>
Message-ID: <1232104262.7.0.796608197215.issue232@psf.upfronthosting.co.za>


Georg Brandl <g.brandl at gmx.net> added the comment:

You should ask this question on one of these three mailing lists:

    python-list at python.org
    help at python.org
    tutor at python.org

This tracker is about issues in Python's bug tracker.

----------
nosy: +gbrandl
status: unread -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue232>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Jan 17 12:25:08 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 17 Jan 2009 11:25:08 +0000
Subject: [Tracker-discuss] [issue228] Inefficient display of ticket content,
	request for improvement proposals
In-Reply-To: <1228636961.97.0.248408525634.issue228@psf.upfronthosting.co.za>
Message-ID: <1232191508.93.0.925098702842.issue228@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

Closed because of lack of response.

----------
nosy: +loewis
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue228>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Jan 17 13:15:48 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 17 Jan 2009 12:15:48 +0000
Subject: [Tracker-discuss] [issue215] Add synthetic token "hasrev" to
	SpamBayes detector
In-Reply-To: <1219600918.16.0.201826532823.issue215@psf.upfronthosting.co.za>
Message-ID: <1232194548.07.0.0781899624895.issue215@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

Thanks for the patch. Committed (with modifications) as r68654, r68655, r68656,
r68657, r68658, r68659.

----------
nosy: +loewis
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue215>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Jan 17 15:45:41 2009
From: metatracker at psf.upfronthosting.co.za (Skip Montanaro)
Date: Sat, 17 Jan 2009 14:45:41 +0000
Subject: [Tracker-discuss] [issue215] Add synthetic token "hasrev" to
	SpamBayes detector
In-Reply-To: <1232194548.07.0.0781899624895.issue215@psf.upfronthosting.co.za>
Message-ID: <18801.61202.70904.427788@montanaro.dyndns.org>


Skip Montanaro <skip at pobox.com> added the comment:

Martin> Martin v. L??wis <martin at v.loewis.de> added the comment:

    Martin> Thanks for the patch. Committed (with modifications) as r68654,
    Martin> r68655, r68656, r68657, r68658, r68659.

Thank you.  Also in that thread I asked about extensions/spambayes.py.  How
is that different than detectors/spambayes.py?

Skip

----------
status: resolved -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue215>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Jan 17 15:49:52 2009
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Sat, 17 Jan 2009 14:49:52 +0000
Subject: [Tracker-discuss] [issue215] Add synthetic token "hasrev" to
	SpamBayes detector
In-Reply-To: <1219600918.16.0.201826532823.issue215@psf.upfronthosting.co.za>
Message-ID: <1232203792.67.0.309177300314.issue215@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

This is for the spambayes_classify action, which is invoked through the "mark as
spam" and "mark as ham" buttons.

----------
status: chatting -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue215>
_______________________________________________________

From skip at pobox.com  Thu Jan 29 21:31:42 2009
From: skip at pobox.com (skip at pobox.com)
Date: Thu, 29 Jan 2009 14:31:42 -0600 (CST)
Subject: [Tracker-discuss] Using "Re:" in issue responses
Message-ID: <20090129203142.BDF31D912AB@montanaro.dyndns.org>

I subscribe to the python-bugs-list mailing list via digest so maybe I
notice this more than people getting messages one-by-one, but I would find
it helpful if all responses to an initial issue submission had "Re:" in the
subject to make it easier to distinguish them from original reports.  Just
my two cents...

Skip

From metatracker at psf.upfronthosting.co.za  Thu Jan 29 23:07:01 2009
From: metatracker at psf.upfronthosting.co.za (Skip Montanaro)
Date: Thu, 29 Jan 2009 22:07:01 +0000
Subject: [Tracker-discuss] [issue233] Using "Re:" in issue responses
In-Reply-To: <20090129203142.BDF31D912AB@montanaro.dyndns.org>
Message-ID: <20090129203142.BDF31D912AB@montanaro.dyndns.org>


New submission from Skip Montanaro <skip at pobox.com>:

I subscribe to the python-bugs-list mailing list via digest so maybe I
notice this more than people getting messages one-by-one, but I would find
it helpful if all responses to an initial issue submission had "Re:" in the
subject to make it easier to distinguish them from original reports.  Just
my two cents...

Skip

----------
messages: 1137
nosy: montanaro
status: unread
title: Using "Re:" in issue responses

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue233>
_______________________________________________________