On Tue, 2011-12-13 at 16:11 +0100, Hartmut Goebel wrote:
> Am 11.12.2011 15:26, schrieb Giovanni Bajo:
> > One issue I had from the start is that PyInstaller only allows for ascii
> > vs unicode. I think that what it should really allows for is a
> > user-configurable list of codecs. For instance, many people will want
> > just utf-8 support, but right now they need to use unicode for that.
> >
> > I know this is a different topic, but since we're refactoring the codec
> > support I think it makes sense to know where we're heading. My
> > suggestion is to add a Codecs() call in spec files to be used like this:
> >
> > a = Analysys(....)
> > a += Codecs(["utf-8"])
> 
> *Adding* Codeces is quite useless, at least in python 2.6 and 2.7: In 
> these versions even a simple program includes the encodings, se 
> buildtest/basic/test_helloworld.py.
> 
> *Removing* codecs would make more sence:
> 
> a = Analysys(...., excludes=Codecs("*", exclude="utf-8"))

OK.

> > One available codec will be "all" which means "all codecs available in
> I would use "*". This symbol is already used in `import` and can never 
> conflict with any codec name.

OK.
-- 
Giovanni Bajo   ::  [email protected]
Develer S.r.l.  ::  http://www.develer.com

My Blog: http://giovanni.bajo.it

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to