Mailman 3 August 2001 - Python-Dev

Re: [Python-Dev] test results
by Michael Hudson Aug. 2, 2001

Aug. 2, 2001

Skip Montanaro <skip(a)pobox.com> writes: > The linuxaudiodev test never seems to work for me (though I do hear > an agonizing wail (is that supposed to be Homer Simpson?) Cardinal Biggles, I think. > from my laptop's speakers when it's run). Sorry I can't be of more use. Cheers, M. -- While preceding your entrance with a grenade is a good tactic in Quake, it can lead to problems if attempted at work. -- C Hacking -- http://home.xnet.com/~raven/Sysadmin/ASR.Quotes.html

1 0

post descr-branch merge results
by barry＠zope.com Aug. 2, 2001

Aug. 2, 2001

Everything looks pretty good from here (Linux, RH6.1-ish). 143 tests passed, and the usual 17 skipped. gcc spit out a bunch of warnings in socketmodule.c, all of which look to be openssl related. It's certainly possible that I have an old openssl package laying around. Other than that, it looks good. Thanks Tim! -Barry gcc -g -O3 -Wall -Wstrict-prototypes -fPIC -DUSE_SSL=1 -I/usr/local/ssl/include -I. -I/home/barry/projects/python/./Include -I/usr/local/include -IInclude/ -c /home/barry/… [View More]projects/python/Modules/socketmodule.c -o build/temp.linux-i686-2.2/socketmodule.o In file included from /home/barry/projects/python/Modules/socketmodule.c:208: /usr/local/ssl/include/openssl/rsa.h:219: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/rsa.h:220: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/rsa.h:221: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/rsa.h:223: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/rsa.h:224: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/rsa.h:227: warning: function declaration isn't a prototype In file included from /usr/local/ssl/include/openssl/objects.h:960, from /usr/local/ssl/include/openssl/evp.h:138, from /usr/local/ssl/include/openssl/x509.h:67, from /home/barry/projects/python/Modules/socketmodule.c:210: /usr/local/ssl/include/openssl/asn1.h:377: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:378: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:379: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:380: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:753: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:755: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:806: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:806: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:809: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:809: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:810: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:817: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:817: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:818: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:854: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:856: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:858: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/asn1.h:859: warning: function declaration isn't a prototype In file included from /usr/local/ssl/include/openssl/x509.h:67, from /home/barry/projects/python/Modules/socketmodule.c:210: /usr/local/ssl/include/openssl/evp.h:267: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/evp.h:268: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/evp.h:269: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/evp.h:271: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/evp.h:272: warning: function declaration isn't a prototype In file included from /home/barry/projects/python/Modules/socketmodule.c:210: /usr/local/ssl/include/openssl/x509.h:122: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/x509.h:123: warning: function declaration isn't a prototype In file included from /usr/local/ssl/include/openssl/x509_vfy.h:69, from /usr/local/ssl/include/openssl/x509.h:520, from /home/barry/projects/python/Modules/socketmodule.c:210: /usr/local/ssl/include/openssl/lhash.h:90: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/lhash.h:91: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/lhash.h:123: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/lhash.h:123: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/lhash.h:128: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/lhash.h:129: warning: function declaration isn't a prototype In file included from /home/barry/projects/python/Modules/socketmodule.c:210: /usr/local/ssl/include/openssl/x509.h:967: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/x509.h:970: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/x509.h:973: warning: function declaration isn't a prototype In file included from /home/barry/projects/python/Modules/socketmodule.c:211: /usr/local/ssl/include/openssl/pem.h:491: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/pem.h:493: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/pem.h:505: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/pem.h:507: warning: function declaration isn't a prototype In file included from /usr/local/ssl/include/openssl/ssl.h:63, from /home/barry/projects/python/Modules/socketmodule.c:212: /usr/local/ssl/include/openssl/comp.h:15: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/comp.h:16: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/comp.h:17: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/comp.h:18: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/comp.h:19: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/comp.h:20: warning: function declaration isn't a prototype In file included from /home/barry/projects/python/Modules/socketmodule.c:212: /usr/local/ssl/include/openssl/ssl.h:224: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:225: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:226: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:442: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:445: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:467: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:574: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:653: warning: function declaration isn't a prototype In file included from /home/barry/projects/python/Modules/socketmodule.c:212: /usr/local/ssl/include/openssl/ssl.h:1032: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:1068: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:1070: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:1143: warning: function declaration isn't a prototype /usr/local/ssl/include/openssl/ssl.h:1144: warning: function declaration isn't a prototype [View Less]

2 1

Re: [Python-Dev] Parrot -- should life imitate satire?
by Samuele Pedroni Aug. 2, 2001

Aug. 2, 2001

Hi. > > The point is to put the commonly called things in the vtable in a way that > you can avoid as much conditional code as possible, while less common > things get dealt with in ways you'd generally expect. (Dynamic lookups with > caching and suchlike things) If I'm right, you're designing a object-based VM. I don't how typical is OO programming in Perl, but in Python that plays a central role, if your long run goal is to compile to native code you should have a "hard-… [View More]

3 2

testing
by Guido van Rossum Aug. 2, 2001

Aug. 2, 2001

I have noticed PSU activity on this channel. This is a test message to check wh

1 0

PyOS_snprintf() / PyOS_vsnprintf()
by M.-A. Lemburg Aug. 2, 2001

Aug. 2, 2001

Just to let you know and to initiate some cross-platform testing: While working on the warning patch for modsupport.c, I've added two new APIs which hopefully make it easier for Python to switch to buffer overflow safe [v]snprintf() APIs for error reporting et al. The two new APIs are PyOS_snprintf() and PyOS_vsnprintf() and work just like the standard ones in many C libs. On platforms which have snprintf(), the native APIs are used, on all other an emulation with snprintf() tries to do its … [View More]

3 4

descr-branch is dead; long live the trunk
by Tim Peters Aug. 1, 2001

Aug. 1, 2001

I completed merging descr-branch back into the trunk. Checkins should no longer occur on descr-branch. The trunk was tagged before and after the merge: before tag: date2001-08-01 after tag: after-descr-branch-merge After a few quiet months have passed, I intend to get rid of the assorted dateYYYY-MM-DD tags added for repeated merging of the trunk back into the branch. One problem: test_weakref.py fails now. It didn't fail in the trunk before the merge, or in descr-branch. All the … [View More]weakref files (_weakref.c, weakref.py, test_weakref.py) are the same in both trunk and branch, so there's no obvious accounting for this. Most of test_weakref works fine: C:\Code\python\dist\src\PCbuild>python ../lib/test/test_weakref.py test_basic_callback (__main__.ReferencesTestCase) ... FAIL test_basic_proxy (__main__.ReferencesTestCase) ... ok test_basic_ref (__main__.ReferencesTestCase) ... ok test_callable_proxy (__main__.ReferencesTestCase) ... ok test_getweakrefcount (__main__.ReferencesTestCase) ... ok test_getweakrefs (__main__.ReferencesTestCase) ... ok test_multiple_callbacks (__main__.ReferencesTestCase) ... ok Make sure all references are invalidated before callbacks ... ok test_proxy_ref (__main__.ReferencesTestCase) ... ok test_proxy_reuse (__main__.ReferencesTestCase) ... ok test_ref_reuse (__main__.ReferencesTestCase) ... ok ====================================================================== FAIL: test_basic_callback (__main__.ReferencesTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "../lib/test/test_weakref.py", line 52, in test_basic_callback self.check_basic_callback(create_unbound_method) File "../lib/test/test_weakref.py", line 114, in check_basic_callback "callback did not properly set 'cbcalled'") File "C:\CODE\PYTHON\DIST\SRC\lib\unittest.py", line 249, in failUnless if not expr: raise self.failureException, msg AssertionError: callback did not properly set 'cbcalled' ---------------------------------------------------------------------- Ran 11 tests in 0.000s FAILED (failures=1) Traceback (most recent call last): File "../lib/test/test_weakref.py", line 410, in ? run_unittest(ReferencesTestCase) File "../lib/test\test_support.py", line 146, in run_unittest raise TestFailed(str(err[1])) test_support.TestFailed: callback did not properly set 'cbcalled' C:\Code\python\dist\src\PCbuild> Fred, would you take a look at that and see whether anything punches you in the eye? CVS made the merge back into the trunk much harder than it should have been, and I don't to want hold things up for what's *probably* a shallow problem I'm just too fried now to pick up on. gamblingly y'rs - tim [View Less]

1 1

Revised decimal type PEP
by Michael McLay Aug. 1, 2001

Aug. 1, 2001

PEP: 2XX Title: Adding a Decimal type to Python Version: $Revision:$ Author: mclay(a)nist.gov <mclay(a)nist.gov> Status: Draft Type: ?? Created: 25-Jul-2001 Python-Version: 2.2 Introduction This PEP describes the addition of a decimal number type to Python. Rationale The original Python numerical model included int, float, and long. By popular request the imaginary type was added to improve support for engineering and scientific applications. The addition of a … [View More]decimal number type to Python will improve support for business applications as well as improve the utility of Python a teaching language. The number types currently used in Python are encoded as base two binary numbers. The base 2 arithmetic used by binary numbers closely approximates the decimal number system and for many applications the differences in the calculations are unimportant. The decimal number type encodes numbers as decimal digits and use base 10 arithmetic. This is the number system taught to the general public and it is the system used by businesses when making financial calculations. For financial and accounting applications the difference between binary and decimal types is significant. Consequently the computer languages used for business application development, such as COBOL, use decimal types. The decimal number type meets the expectations of non-computer scientists when making calculations. For these users the rounding errors that occur when using binary numbers is a source of confusion and irritation. Implementation The tokenizer will be modified to recognized number literals with a 'd' suffix and a decimal() function will be added to __builtins__. A decimal number can be used to represent integers and floating point numbers and decimal numbers can also be displayed using scientific notation. Examples of decimal numbers include: 1234d -1234d 1234.56d -1234.56d 1234.56e2d -1234.56e-2d The type returned by either a decimal floating point or a decimal integer is the same: >>> type(12.2d) <type 'decimal'> >>> type(12d) <type 'decimal'> >>> type(-12d+12d) <type 'decimal'> >>> type(12d+12.0d) <type 'decimal'> This proposal will also add an optional 'b' suffix to the representation of binary float type literals and binary int type literals. >>> float(12b) 12.0 >>> type(12.2b) <type 'float'> >>> type(float(12b)) <type 'float'> >>> type(12b) <type 'int'> The decimal() conversion function added to __builtins__ will support conversions of strings, and binary types to decimal. >>> type(decimal("12d")) <type 'decimal'> >>> type(decimal("12")) <type 'decimal'> >>> type(decimal(12b)) <type 'decimal'> >>> type(decimal(12.0b)) <type 'decimal'> >>> type(decimal(123456789123L)) <type 'decimal'> The conversion functions int() and float() in the __builtin__ module will support conversion of decimal numbers to the binary number types. >>> type(int(12d)) <type 'int'> >>> type(float(12.0d)) <type 'float'> Expressions that mix integers with decimals will automatically convert the integer to decimal and the result will be a decimal number. >>> type(12d + 4b) <type 'decimal'> >>> type(12b + 4d) <type 'decimal'> >>> type(12d + len('abc')) <type 'decimal'> >>> 3d/4b 0.75 Expressions that mix binary floats with decimals introduce the possibility of unexpected results because the two number types use different internal representations for the same numerical value. The severity of this problem is dependent on the application domain. For applications that normally use binary numbers the error may not be important and the conversion should be done silently. For newbie programmers a warning should be issued so the newbie will be able to locate the source of a discrepancy between the expected results and the results that were achieved. For financial applications the mixing of floating point with binary numbers should raise an exception. To accommodate the three possible usage models the python interpreter command line options will be used to set the level for warning and error messages. The three levels are: promiscuous mode, -f or --promiscuous safe mode -s or --save pedantic mode -p or --pedantic The default setting will be set to the safe setting. In safe mode mixing decimal and binary floats in a calculation will trigger a warning message. >>> type(12.3d + 12.2b) Warning: the calculation mixes decimal numbers with binary floats <type 'decimal'> In promiscuous mode warnings will be turned off. >>> type(12.3d + 12.2b) <type 'decimal'> In pedantic mode warning from safe mode will be turned into exceptions. >>> type(12.3d + 12.2b) Traceback (innermost last): File "<stdin>", line 1, in ? TypeError: the calculation mixes decimal numbers with binary floats Semantics of Decimal Numbers ?? [View Less]

7 28

[development doc updates]
by Fred L. Drake Aug. 1, 2001

Aug. 1, 2001

The development version of the documentation has been updated: http://python.sourceforge.net/devel-docs/ Incremental updates, including some useful improvements in the docs for the re module.

1 0

numerical models and numpy
by Paul F. Dubois July 31, 2001

July 31, 2001

I'm a little worried that you all may be assuming that I'm keeping up with this flood of stuff on python-dev about the numerical model. I have tried but I just can't manage that much volume. My silence doesn't mean approval. Whatever "native" types you decide on there will be considerable pressure on us to include corresponding types in Numerical Python, but I don't think that can happen. At the moment there seem to be few people with any time to spare to help me. I won't be able to do such … [View More]

2 1

Re: [Python-Dev] Parrot -- should life imitate satire?
by Dan Sugalski July 31, 2001

July 31, 2001

At 06:12 PM 7/31/2001 -0700, Ka-Ping Yee wrote: >On Tue, 31 Jul 2001, Eric S. Raymond wrote: > > Things Python would bring to this party: our serious-cool GC, our > > C extension/embedding system (*much* nicer than XS). Things Perl would > > bring: blazingly fast regexps, taint, flexitypes, references. > >I don't really understand the motivation. Do we want any of those things? > >Taint might be worth something, and i would see the regexp engine as >… [View More]

1 0