Mailman 3 February 2004 - Python-Dev

RE: [Python-Dev] Decimal.py in sandbox
by Batista, Facundo Feb. 10, 2004

Feb. 10, 2004

Aahz wrote: #- On Tue, Feb 10, 2004, Batista, Facundo wrote: #- > To whom I shall send the diffs to get committed? Should I #- commit them to #- > the sandbox myself? #- #- Given that it's sandbox, go ahead and commit yourself. We can always #- revert. ;-) With what user? I'm facundobatista in SF. Have I, as facundobatista, commit privileges in the python sandbox? What should I do to have them? Thank you! . Facundo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADVERTENCIA La información contenida en este mensaje y cualquier archivo anexo al mismo, son para uso exclusivo del destinatario y pueden contener información confidencial o propietaria, cuya divulgación es sancionada por la ley. Si Ud. No es uno de los destinatarios consignados o la persona responsable de hacer llegar este mensaje a los destinatarios consignados, no está autorizado a divulgar, copiar, distribuir o retener información (o parte de ella) contenida en este mensaje. Por favor notifíquenos respondiendo al remitente, borre el mensaje original y borre las copias (impresas o grabadas en cualquier medio magnético) que pueda haber realizado del mismo. Todas las opiniones contenidas en este mail son propias del autor del mensaje y no necesariamente coinciden con las de Telefónica Comunicaciones Personales S.A. o alguna empresa asociada. Los mensajes electrónicos pueden ser alterados, motivo por el cual Telefónica Comunicaciones Personales S.A. no aceptará ninguna obligación cualquiera sea el resultante de este mensaje. Muchas Gracias.

3 2

Re: [Python-Dev] Syntax for "except"
by Phillip J. Eby Feb. 10, 2004

Feb. 10, 2004

At 08:51 AM 2/10/04 -0800, Guido van Rossum wrote: > > Why was Python syntax designed so > > except (TypeError, ValueError): > > is OK but > > except [TypeError, ValueError]: > > is forbidden. Should this be changed? Is immutability needed here? Where > > in Python is immutability really needed or really improves efficiency? > >I never *intended* this to be seen as a container, but rather as a use >of parentheses for grouping. But the current implementation *does* have a nice side effect of allowing error psuedoclasses to be created, e.g.: FooOrBarError = FooError, BarError try: ... except FooOrBarError: ... This can be useful for dealing with stuff like DBAPI errors, where you're writing code that may need to work with multiple DBAPI modules' errors simultaneously. Since FooOrBarError can be rebound to reflect the possible errors in play, it allows some dyanmism without having to write a bunch of Python code to introspect sys.exc_info(), while also making the code's intention clearer than if it had to do such introspection.

2 1

Another big ANSI-fication change - another good chance for testing
by Skip Montanaro Feb. 10, 2004

Feb. 10, 2004

I just checked in changes to a fair number of files to no longer test for the presence of header files required by ANSI C (C89). I ran the test suite successfully on Mac OS X (gcc 3.3) and Solaris 8 (gcc 2.95.3). On Mandrake 8.1 (gcc 3.0.1) I had some trouble with tests related to the bsddb package, but I was having those same problems before applying my changes. Once I can do a cvs up again I'll try cygwin as well. Obvious stuff I couldn't check: Windows, OS/2, RISCOS. (The handcrafted pyconfig.h files for all changed.) Please give it a whirl. Skip

1 0

RE: [Python-Dev] Decimal.py in sandbox
by Batista, Facundo Feb. 10, 2004

Feb. 10, 2004

Kevin Jacobs wrote: #- I'd be happier with at least one round of review before #- committing to CVS. #- The code is fairly complex and an extra set of eyes will help keep #- things focused. I've also volunteered to be that extra set #- of eyes, and #- plan a quick turn-around on any patches sent to me. #- #- However, I don't have CVS write permission either, even to #- the sandbox. So, I sent to Kevin the first diffs about Decimal.py, and he was OK to them. They're mostly about cosmetics, but I wanted a few not fundamental changes to get the circuit working and then start with heavier changes. To whom I shall send the diffs to get committed? Should I commit them to the sandbox myself? Thanks for all! . Facundo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADVERTENCIA La información contenida en este mensaje y cualquier archivo anexo al mismo, son para uso exclusivo del destinatario y pueden contener información confidencial o propietaria, cuya divulgación es sancionada por la ley. Si Ud. No es uno de los destinatarios consignados o la persona responsable de hacer llegar este mensaje a los destinatarios consignados, no está autorizado a divulgar, copiar, distribuir o retener información (o parte de ella) contenida en este mensaje. Por favor notifíquenos respondiendo al remitente, borre el mensaje original y borre las copias (impresas o grabadas en cualquier medio magnético) que pueda haber realizado del mismo. Todas las opiniones contenidas en este mail son propias del autor del mensaje y no necesariamente coinciden con las de Telefónica Comunicaciones Personales S.A. o alguna empresa asociada. Los mensajes electrónicos pueden ser alterados, motivo por el cual Telefónica Comunicaciones Personales S.A. no aceptará ninguna obligación cualquiera sea el resultante de este mensaje. Muchas Gracias.

2 1

Fwd: Re: [Python-Dev] *grumble* wchar.h
by Barry Scott Feb. 9, 2004

Feb. 9, 2004

Opss forgot to mail the list. > Barry> This site http://www.comeaucomputing.com/iso/ has a link to where > Barry> you can but ISO C99 for $20. Also you should be able to buy from > Barry> www.iso.org or your countries standards body. > >Barry, > >Thanks for the link. I wasn't aware any C standards were available in >electronic form. That makes it a lot more palatable than the cost of the >printed docs. > >Skip

1 0

Allowing non-ASCII identifiers
by "Martin v. Löwis" Feb. 9, 2004

Feb. 9, 2004

I'd like to work on adding support for non-ASCII characters in identifiers, using the following principles: 1. At run-time, identifiers are represented as Unicode objects unless they are pure ASCII. IOW, they are converted from the source encoding to Unicode objects in the process of parsing. 2. As a consequence of 1), all places there identifiers appear need to support Unicode objects (e.g. __dict__, __getattr__, etc) 3. Legal non-ASCII identifiers are what legal non-ASCII identifiers are in Java, except that Python may use a different version of the Unicode character database. Python would share the property that future versions allow more characters in identifiers than older versions. If you are too lazy too look up the Java definition, here is a rough overview: An identifier is "JavaLetter JavaLetterOrDigit*" JavaLetter is a character of the classes Lu, Ll, Lt, Lm, or Lo, or a currency symbol (for Python: excluding $), or a connecting punctuation character (which is unfortunately underspecified - will research the implementation). JavaLetterOrDigit is a JavaLetter, or a digit, a numeric letter, a combining mark, a non-spacing mark, or an ignorable control character. Does this need a PEP? Regards, Martin

5 10

Tests failling on release23-maint branch
by Jim Fulton Feb. 9, 2004

Feb. 9, 2004

On RedHat 9: [jim@enterprised src]$ uname -a Linux enterprised.zope.com 2.4.20-28.9 #1 Thu Dec 18 13:45:22 EST 2003 i686 i686 i386 GNU/Linux [jim@enterprised src]$ gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) [jim@enterprised src]$ ./configure --with-pydebug --prefix=/usr/local/python/release23-maintdb ... [jim@enterprised src]$ make ... [jim@enterprised src]$ nice ./python -E -tt ./Lib/test/regrtest.py -l -uall ... 6 tests failed: test_curses test_linuxaudiodev test_socket_ssl test_tarfile test_timeout test_urllibnet 19 tests skipped: test_aepack test_al test_bsddb185 test_bz2 test_cd test_cl test_email_codecs test_gl test_imgfile test_macfs test_macostools test_nis test_normalization test_pep277 test_plistlib test_scriptpackages test_sunaudiodev test_winreg test_winsound 1 skip unexpected on linux2: test_bz2 -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

3 2

OSCON Reminder: proposal deadline *** TODAY ***
by Guido van Rossum Feb. 9, 2004

Feb. 9, 2004

This is the FINAL reminder: you still have all day today to submit a proposal for the Python 12 Conference at OSCON: The O'Reilly Open Source Convention (OSCON) will be held July 26-30, 2004 at the Portland Marriott Downtown in Portland, OR. http://conferences.oreillynet.com/os2004/ Proposals Submission Information--Deadline: February 9, 2004 http://conferences.oreillynet.com/cs/os2004/create/e_sess --Guido van Rossum (home page: http://www.python.org/~guido/)

1 0

building python with profiling support
by Jeremy Hylton Feb. 9, 2004

Feb. 9, 2004

I've used gprof to profile the interpreter in the past, but I'm stuck trying to it again on my current machine. I configured Python by saying CC="gcc -pg" ../configure That's the way I've built Python for profiling in the past and that's what the README says to do. The python binary that gets generated doesn't generate a gmon.out file. It appears that the problem is with the command used to generate the actual Python executable: c++ -pthread -Xlinker -export-dynamic -o python \ Modules/python.o \ libpython2.4.a -lpthread -ldl -lutil -lm The -pg flag has been lost. Can anyone suggest a recipe that will work? Or suggest how to modify the Makefile so that the -pg flag gets passed along. Jeremy

4 3

*grumble* wchar.h
by Skip Montanaro Feb. 8, 2004

Feb. 8, 2004

I decided to tackle the ANSI C assumption next. If we assume an ANSI C compiler, then a number of checks for header files required by the standard can be deleted. Working from the list here: http://en.wikipedia.org/wiki/ANSI_C_standard_library I started zapping tests. Once finished, I tried building. Everything seemed to work fine except the _locale module wouldn't build because my Mac doesn't have wchar.h. So, is wchar.h part of the ANSI C standard or is Apple's GCC setup (Mac OS X 10.2.8, gcc 3.3) in error? Skip

2 5