Re: unicode in setup.py file causing RC bug

2007-05-08 Thread Brian Sutherland
On Mon, May 07, 2007 at 09:27:18PM -0400, Scott Kitterman wrote:
 On Monday 07 May 2007 20:43, Kevin Coyner wrote:
 Or 3.  Patch setup.py to expect it.  I believe if you add:
 
 # -*- encoding: utf-8 -*-
 
 to the file before the unicode characters are encountered the first time, 
 that 
 should solve your problem.  I didn't look at your package, but that worked 
 for me before for a similar issue.

I believe it needs to be on either the first or second line:

http://docs.python.org/ref/encodings.html

-- 
Brian Sutherland


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: unicode in setup.py file causing RC bug

2007-05-08 Thread Kevin Coyner


On Tue, May 08, 2007 at 09:42:00AM +0200, Brian Sutherland wrote..

 On Mon, May 07, 2007 at 09:27:18PM -0400, Scott Kitterman wrote:
  On Monday 07 May 2007 20:43, Kevin Coyner wrote:
  Or 3.  Patch setup.py to expect it.  I believe if you add:
 
  # -*- encoding: utf-8 -*-
 
  to the file before the unicode characters are encountered the
  first time, that should solve your problem.  I didn't look at
  your package, but that worked for me before for a similar issue.

 I believe it needs to be on either the first or second line:

 http://docs.python.org/ref/encodings.html

Thanks for the responses, but that line was already present in
my setup.py when Lucas generated the FTBFS bug. The first two lines
were:

#!/usr/bin/env python
# -*- coding: UTF-8 -*-

Is this not an issue with any other python package? Still thinking
of reassigning this bug ...

Thanks,
Kevin

-- 
Kevin Coyner  GnuPG key: 1024D/8CE11941


signature.asc
Description: Digital signature


Re: unicode in setup.py file causing RC bug

2007-05-08 Thread Josselin Mouette
Le mardi 08 mai 2007 à 05:57 -0400, Kevin Coyner a écrit :
 Is this not an issue with any other python package? Still thinking
 of reassigning this bug ...

It looks like an issue in distutils indeed. The file is opened in ASCII
mode, which doesn't allow for writing Unicode text inside.

You should reassign the bug to python.
-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée


unicode in setup.py file causing RC bug

2007-05-07 Thread Kevin Coyner

I maintain the package rpl, which today received an RC bug

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422604

because it FTBFS in an autobuild on Lucas.

The reason it failed is due to the use of unicode for the author's
name in the setup.py file.

distutils (for the setup.py file) is part of python
which is part of the python module distutils.

I see two options for fixing this:

1. Remove the unicode from the author's name and spell it using
ascii.

or

2. Reassign the bug to the main python package.

I'm not much in favor of #1 because we should be able to get
names correct.

I favor #2 as it does seem to be a bug in python. I found the
following regarding the bug:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg03007.html

So just looking for a little guidance in case I missed something
before I proceed.

Thanks
Kevin

-- 
Kevin Coyner  GnuPG key: 1024D/8CE11941


signature.asc
Description: Digital signature


Re: unicode in setup.py file causing RC bug

2007-05-07 Thread Scott Kitterman
On Monday 07 May 2007 20:43, Kevin Coyner wrote:
 I maintain the package rpl, which today received an RC bug

 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422604

 because it FTBFS in an autobuild on Lucas.

 The reason it failed is due to the use of unicode for the author's
 name in the setup.py file.

 distutils (for the setup.py file) is part of python
 which is part of the python module distutils.

 I see two options for fixing this:

 1. Remove the unicode from the author's name and spell it using
 ascii.

 or

 2. Reassign the bug to the main python package.

 I'm not much in favor of #1 because we should be able to get
 names correct.

 I favor #2 as it does seem to be a bug in python. I found the
 following regarding the bug:

 http://www.mail-archive.com/[EMAIL PROTECTED]/msg03007.html

 So just looking for a little guidance in case I missed something
 before I proceed.

Or 3.  Patch setup.py to expect it.  I believe if you add:

# -*- encoding: utf-8 -*-

to the file before the unicode characters are encountered the first time, that 
should solve your problem.  I didn't look at your package, but that worked 
for me before for a similar issue.

Scott K


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: unicode in setup.py file causing RC bug

2007-05-07 Thread Ben Finney
Scott Kitterman [EMAIL PROTECTED] writes:

 # -*- encoding: utf-8 -*-

Specifically, the directive is 'coding: utf-8' inside those
delimiters. (encoding will work also, but only because the parsing
of that line allows it.)

-- 
 \   Those who will not reason, are bigots, those who cannot, are |
  `\ fools, and those who dare not, are slaves.  -- Lord George |
_o__)Gordon Noel Byron |
Ben Finney


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: unicode in setup.py file causing RC bug

2007-05-07 Thread Scott Kitterman
On Monday 07 May 2007 22:11, Ben Finney wrote:
 Scott Kitterman [EMAIL PROTECTED] writes:
  # -*- encoding: utf-8 -*-

 Specifically, the directive is 'coding: utf-8' inside those
 delimiters. (encoding will work also, but only because the parsing
 of that line allows it.)

Thanks.  Good to know.

Scott K


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]