Message 115837 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	belopolsky
Recipients	Claudiu.Popa, belopolsky, eric.araujo, flox, pitrou
Date	2010-09-08.01:11:41
SpamBayes Score	4.850412e-07
Marked as misclassified	No
Message-id	<AANLkTi=93bkpLAvW4G1q-DxCJa-NVD=TbmKd=xHVdusM@mail.gmail.com>
In-reply-to	<1283905914.86.0.530234840954.issue9598@psf.upfronthosting.co.za>

Content
On Tue, Sep 7, 2010 at 8:31 PM, Éric Araujo <report@bugs.python.org> wrote: .. > My real question was: Shouldn’t this be a VCS hook instead of untabify’s job? (or in addition to untabify if you insist) > Yes, VCS hook makes sense (and may almost eliminate the need to handle invalid bytestreams in untabify). The hard question is still the same, though: are non-ascii characters allowed in python C code? My answer is "no".

On Tue, Sep 7, 2010 at 8:31 PM, Éric Araujo <report@bugs.python.org> wrote:
..
> My real question was: Shouldn’t this be a VCS hook instead of untabify’s job? (or in addition to untabify if you insist)
>

Yes,  VCS hook makes sense (and may almost eliminate the need to
handle invalid bytestreams in untabify).  The hard question is still
the same, though: are non-ascii characters allowed in python C code?
My answer is "no".

History
Date	User	Action	Args
2010-09-08 01:11:43	belopolsky	set	recipients: + belopolsky, pitrou, eric.araujo, flox, Claudiu.Popa
2010-09-08 01:11:42	belopolsky	link	issue9598 messages
2010-09-08 01:11:41	belopolsky	create