Mailman 3 March 2002 - Python-Dev

Re: [Python-Dev] PEP 263 considered faulty (for some Japanese)
by SUZUKI Hisao March 26, 2002

March 26, 2002

> And TextEdit cannot save as UTF-8? It can. But doing so suffers from "mojibake". > The primary reason why this is not supported is different, though: it > would complicate the implementation significantly, atleast the phase 1 > implementation. If people contribute a phase 2 implementation that > supports the UTF-16 BOM as a side effect, I would personally > reconsider. OK, I will write a sample implementation of the "stage2" as soon as possible, and put it in the public domain. Anyway, until the stage2 comes true, you can write Japanese python files only in either EUC-JP or UTF-8 unless you hack up the interpreter, thus Python remains unsatisfactory to many present Japanese till the day of UTF-8. We should either hurry up or wait still. As for UTF-16 with BOM, any text outside Unicode literals should be translated into UTF-8 (not UTF-16). It is the sole logical consequence in that UTF-8 is strictly ASCII-compatible and able to map all the characters in Unicode naturally. You will write source codes in UTF-16 as follows: s = '<characters>' ... u = unicode(s, 'utf-8') # not utf-16! This suggests me that the implementation will be somewhat like as Stephen J. Turnbull sketches... N.B. one should write a binary (not character, but, say, image or audio) data literal as follows: b = '\x89\xAB\xCD\xEF' The stage2 implementation will translate it into UTF-8 exactly as follows :-) b = '\x89\xAB\xCD\xEF' Hence there is no problem in translating UTF-16 file into UTF-8. (At least, any UTF-16 python file is impossible totally for now, allowing it does not hurt anyone here and there.) -- SUZUKI Hisao >>> def fib(n): return reduce(lambda x, y: suzuki(a)acm.org ... (x,x[0][-1]+x[1]), [()]*n, ((0L,),1L))

4 6

RE: [Python-checkins] CVS: python/dist/src/Lib pickle.py,1.57,1.58
by Tim Peters March 26, 2002

March 26, 2002

[Guido] > Modified Files: > pickle.py > Log Message: > Fix for SF 502085. > Don't die when issubclass(t, TypeType) fails. > > Bugfix candidate (but I think it's too late for 2.2.1). Because ...? The 2.2.1c2 Windows installer won't get built today, and the tarball won't get cut at least until Michael has another cut at the NEWS file. So it's not too late to put it into 2.2.1 if you feel confident about this change.

3 2

CVS server hosed?
by Skip Montanaro March 26, 2002

March 26, 2002

When I try cvs up I get ssh_exchange_identification: Connection closed by remote host cvs [update aborted]: end of file from server (consult above messages if any) This just started in the last few minutes. Is the CVS server down or sick? Skip

6 11

Developer's guide Web pages
by Andrew Kuchling March 25, 2002

March 25, 2002

The python-dev HOWTO has now been cut up and rearranged into a set of Web pages at http://www.python.org/dev/ . Please suggest additional things that should be explained in these pages, or that should be linked to. Comments on the accuracy of the "Python Culture" page are also welcome; it might be missing some important points, or it might describe my idealization of how we try to behave. :) And if anyone has suggestions on how make the pages more likely to attract new developers to Python, I'm all ears! --amk (www.amk.ca) It's more serious than death, Mr Stevenson. He's changing form. -- The Doctor, in "The Seeds of Doom"

5 4

self._backupfilename in fileinput
by Skip Montanaro March 25, 2002

March 25, 2002

Working my way through the unqualified except: clauses, I found one in fileinput.py that looks very straightforward: try: os.unlink(backupfilename) except: pass To make sure that OSError was all that could be raised I started looking at what values backupfilename could assume. Then I started looking at self._backupfilename. This weird beast takes on values of three distinct types: None, 0, and various strings. While it's not technically broken, is this something worth fixing? My inclination is to just add OSError to the except clause and let someone else worry about fixing something that's ugly but not really broken. Skip

2 1

Re: [Python-Dev] 2.2.1c1 platform reports.
by Michael Hudson March 25, 2002

March 25, 2002

Andrew MacIntyre <andymac(a)bullseye.apana.org.au> writes: > On 22 Mar 2002, Michael Hudson wrote: > > > I crunched through the various platform experiences I'd heard for > > 2.2.1c1, and came up with the following. Can anyone fill in some > > gaps, add comments or dig into some of the mentioned problems? Things > > are looking fairly good, but reports from AIX-land in particular are > > making my head spin like a top. > > Sorry, I've not had time to look at this for the OS/2-EMX build; maybe > tonight. I thought OS/2-EMX was only going to be supported in 2.3? I'm certainly not going to port all those checkins you made to the -maint branch. Cheers, M. -- For their next act, they'll no doubt be buying a firewall running under NT, which makes about as much sense as building a prison out of meringue. -- -:Tanuki:- -- http://home.xnet.com/~raven/Sysadmin/ASR.Quotes.html

3 2

[development doc updates]
by Fred L. Drake March 25, 2002

March 25, 2002

The development version of the documentation has been updated: http://python.sourceforge.net/maint-docs/ Documentation for Python 2.2.1 release candidate 2.

1 0

Re: [Python-Dev] release22-maint Doc/ tree is closed
by Michael Hudson March 25, 2002

March 25, 2002

"Fred L. Drake, Jr." <fdrake(a)acm.org> writes: > Please don't check anything into the Doc/ tree on the > release22-maint branch. Thanks. Actually, please don't check anything into anywhere on the release22-maint branch, unless you're me, Tim, Fred or Jack, or have been told to by one of us. Cheers, M. -- Important data should not be entrusted to Pinstripe, as it may eat it and make loud belching noises. -- from the announcement of the beta of "Pinstripe" aka. Redhat 7.0

1 0

release22-maint Doc/ tree is closed
by Fred L. Drake, Jr. March 25, 2002

March 25, 2002

Please don't check anything into the Doc/ tree on the release22-maint branch. Thanks. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation

1 0

Tomorrow's 2.2.1xx release
by Tim Peters March 25, 2002

March 25, 2002

Do we intend to release 2.2.1c2 tomorrow, or 2.2.1 final? I ask because I want to get a head start on adding the right identification strings to the Windows installer. I expect Fred also needs to know for the docs.

2 1