Mailman 3 March 2001 - Python-Dev

Re: [Python-checkins] CVS: python/dist/src/Lib inspect.py,1.10,1.11
by Jeremy Hylton March 23, 2001

March 23, 2001

Are there any more checkins coming? In general -- are there any checkins other than documentation and a fix for the GC/debug/weakref problem? Jeremy

5 6

Re: CVS Python is unstable
by Guido van Rossum March 23, 2001

March 23, 2001

Tim's problem can be reproduced in debug mode as follows (on Windows as well as on Linux): import test.test_weakref import test.test_xmllib Boom! The debugger (on Windows) shows that it does in some GC code. After backing out Fred's last change to _weakref.c, this works as expected and I get no other problems. So I propose to back out that change and be done with it. Here's the CVS comment: ---------------------------- revision 1.8 date: 2001/03/22 18:05:30; author: fdrake; … [View More]

4 9

Re: Python T-shirts
by aahz＠panix.com March 23, 2001

March 23, 2001

[posted to c.l.py with cc to python-dev] In article <mailman.985019605.8781.python-list(a)python.org>, Guido van Rossum <guido(a)digicool.com> wrote: > >At the conference we handed out T-shirts with the slogan on the back >"Python: programming the way Guido indented it". We've been asked if >there are any left. Well, we gave them all away, but we're ordering >more. You can get them for $10 + S+H. Write to Melissa Light ><melissa(a)digicool.com>. Be … [View More]

1 0

CVS Python is unstable
by Tim Peters March 22, 2001

March 22, 2001

At work today, Guido and I both found lots of instabilities in current CVS Python, under different flavors of Windows: senseless errors in the test suite, different behavior across runs, NULL-pointer errors in GC when running under a debug-build Python, some kind of Windows "app error" alert box, and weird complaints about missing attributes during Python shutdown. Back at home, things *seem* much better, but I still get one of the errors I saw at the office: a NULL-pointer dereference in GC,… [View More]

1 0

Re: [Python-Dev] booted from sourceforge
by Michael Hudson March 22, 2001

March 22, 2001

"Fredrik Lundh" <fredrik(a)effbot.org> writes: > attempts to access the python project, the tracker (etc) results in: > > You don't have permission to access <whatever> on this server. > > is it just me? I was getting this a lot yesterday. Give it a minute, and try again - worked for me, albeit somewhat tediously. Cheers, M. -- Just put the user directories on a 486 with deadrat7.1 and turn the Octane into the afforementioned beer fridge and keep it in … [View More]

1 0

booted from sourceforge
by Fredrik Lundh March 22, 2001

March 22, 2001

attempts to access the python project, the tracker (etc) results in: You don't have permission to access <whatever> on this server. is it just me? Cheers /F

3 3

tests failing on irix65
by Flying Cougar Burnette March 22, 2001

March 22, 2001

Hey Gang, Given the latest state of the CVS tree I am getting the following failures on my irix65 O2 (and have been for quite some time- I'm just now getting around to reporting them): ------------%< snip %<----------------------%< snip %<------------ test_pty The actual stdout doesn't match the expected stdout. This much did match (between asterisk lines): ********************************************************************** test_pty ********************************************… [View More]************************** Then ... We expected (repr): 'I' But instead we got: '\n' test test_pty failed -- Writing: '\n', expected: 'I' importing test_pty into an interactive interpreter gives this: Python 2.1b2 (#27, Mar 20 2001, 23:21:17) [C] on irix6 Type "copyright", "credits" or "license" for more information. >>> import test.test_pty Calling master_open() Got master_fd '4', slave_name '/dev/ttyq6' Calling slave_open('/dev/ttyq6') Got slave_fd '5' Writing to slave_fd I wish to buy a fish license.For my pet fish, Eric. calling pty.fork() Waiting for child (16654) to finish. Child (16654) exited with status 1024. >>> ------------%< snip %<----------------------%< snip %<------------ test_symtable test test_symtable crashed -- exceptions.TypeError: unsubscriptable object running the code test_symtable code by hand in the interpreter gives me: Python 2.1b2 (#27, Mar 20 2001, 23:21:17) [C] on irix6 Type "copyright", "credits" or "license" for more information. >>> import _symtable >>> symbols = _symtable.symtable("def f(x): return x", "?", "exec") >>> symbols <symtable entry global(0), line 0> >>> symbols[0] Traceback (most recent call last): File "<stdin>", line 1, in ? TypeError: unsubscriptable object ------------%< snip %<----------------------%< snip %<------------ test_zlib make: *** [test] Segmentation fault (core dumped) when I run python in a debugger and import test_zlib by hand I get this: Python 2.1b2 (#27, Mar 20 2001, 23:21:17) [C] on irix6 Type "copyright", "credits" or "license" for more information. >>> import test.test_zlib 0xe5c1a120 0x43b6aa94 0xbd602f7 0xbd602f7 expecting Bad compression level expecting Invalid initialization option expecting Invalid initialization option normal compression/decompression succeeded compress/decompression obj succeeded decompress with init options succeeded decompressobj with init options succeeded the faliure is on line 86 of test_zlib.py (calling obj.flush()). here are the relevant portions of the call stack (sorry they're stripped): t_delete(<stripped>) ["malloc.c":801] realfree(<stripped>) ["malloc.c":531] cleanfree(<stripped>) ["malloc.c":944] _realloc(<stripped>) ["malloc.c":329] _PyString_Resize(<stripped>) ["stringobject.c":2433] PyZlib_flush(<stripped>) ["zlibmodule.c":595] call_object(<stripped>) ["ceval.c":2706] ... [View Less]

3 5

PEP 1, PEP Purpose and Guidelines
by barry＠digicool.com March 22, 2001

March 22, 2001

With everyone feeling so PEPpy lately (yay!) I thought it was time to do an updating pass through PEP 1. Attached below is the latest copy, also available (as soon as uploading is complete) via http://python.sourceforge.net/peps/pep-0001.html Note the addition of the Replaces: and Replaced-By: headers for formalizing the PEP replacement policy (thanks to Andrew Kuchling for the idea and patch). Enjoy, -Barry -------------------- snip snip -------------------- PEP: 1 Title: PEP Purpose … [View More]and Guidelines Version: $Revision: 1.16 $ Author: barry(a)digicool.com (Barry A. Warsaw), jeremy(a)digicool.com (Jeremy Hylton) Status: Draft Type: Informational Created: 13-Jun-2000 Post-History: 21-Mar-2001 What is a PEP? PEP stands for Python Enhancement Proposal. A PEP is a design document providing information to the Python community, or describing a new feature for Python. The PEP should provide a concise technical specification of the feature and a rationale for the feature. We intend PEPs to be the primary mechanisms for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Python. The PEP author is responsible for building consensus within the community and documenting dissenting opinions. Because the PEPs are maintained as plain text files under CVS control, their revision history is the historical record of the feature proposal[1]. Kinds of PEPs There are two kinds of PEPs. A standards track PEP describes a new feature or implementation for Python. An informational PEP describes a Python design issue, or provides general guidelines or information to the Python community, but does not propose a new feature. PEP Work Flow The PEP editor, Barry Warsaw <barry(a)digicool.com>, assigns numbers for each PEP and changes its status. The PEP process begins with a new idea for Python. Each PEP must have a champion -- someone who writes the PEP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The PEP champion (a.k.a. Author) should first attempt to ascertain whether the idea is PEP-able. Small enhancements or patches often don't need a PEP and can be injected into the Python development work flow with a patch submission to the SourceForge patch manager[2] or feature request tracker[3]. The PEP champion then emails the PEP editor with a proposed title and a rough, but fleshed out, draft of the PEP. This draft must be written in PEP style as described below. If the PEP editor approves, he will assign the PEP a number, label it as standards track or informational, give it status 'draft', and create and check-in the initial draft of the PEP. The PEP editor will not unreasonably deny a PEP. Reasons for denying PEP status include duplication of effort, being technically unsound, or not in keeping with the Python philosophy. The BDFL (Benevolent Dictator for Life, Guido van Rossum <guido(a)python.org>) can be consulted during the approval phase, and is the final arbitrator of the draft's PEP-ability. The author of the PEP is then responsible for posting the PEP to the community forums, and marshaling community support for it. As updates are necessary, the PEP author can check in new versions if they have CVS commit permissions, or can email new PEP versions to the PEP editor for committing. Standards track PEPs consists of two parts, a design document and a reference implementation. The PEP should be reviewed and accepted before a reference implementation is begun, unless a reference implementation will aid people in studying the PEP. Standards Track PEPs must include an implementation - in the form of code, patch, or URL to same - before it can be considered Final. PEP authors are responsible for collecting community feedback on a PEP before submitting it for review. A PEP that has not been discussed on python-list(a)python.org and/or python-dev(a)python.org will not be accepted. However, wherever possible, long open-ended discussions on public mailing lists should be avoided. A better strategy is to encourage public feedback directly to the PEP author, who collects and integrates the comments back into the PEP. Once the authors have completed a PEP, they must inform the PEP editor that it is ready for review. PEPs are reviewed by the BDFL and his chosen consultants, who may accept or reject a PEP or send it back to the author(s) for revision. Once a PEP has been accepted, the reference implementation must be completed. When the reference implementation is complete and accepted by the BDFL, the status will be changed to `Final.' A PEP can also be assigned status `Deferred.' The PEP author or editor can assign the PEP this status when no progress is being made on the PEP. Once a PEP is deferred, the PEP editor can re-assign it to draft status. A PEP can also be `Rejected'. Perhaps after all is said and done it was not a good idea. It is still important to have a record of this fact. PEPs can also be replaced by a different PEP, rendering the original obsolete. This is intended for Informational PEPs, where version 2 of an API can replace version 1. PEP work flow is as follows: Draft -> Accepted -> Final -> Replaced ^ +----> Rejected v Deferred Some informational PEPs may also have a status of `Active' if they are never meant to be completed. E.g. PEP 1. What belongs in a successful PEP? Each PEP should have the following parts: 1. Preamble -- RFC822 style headers containing meta-data about the PEP, including the PEP number, a short descriptive title, the names contact info for each author, etc. 2. Abstract -- a short (~200 word) description of the technical issue being addressed. 3. Copyright/public domain -- Each PEP must either be explicitly labelled in the public domain or the Open Publication License[4]. 4. Specification -- The technical specification should describe the syntax and semantics of any new language feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Python platforms (CPython, JPython, Python .NET). 5. Rationale -- The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion. 6. Reference Implementation -- The reference implementation must be completed before any PEP is given status 'Final,' but it need not be completed before the PEP is accepted. It is better to finish the specification and rationale first and reach consensus on it before writing code. The final implementation must include test code and documentation appropriate for either the Python language reference or the standard library reference. PEP Style PEPs are written in plain ASCII text, and should adhere to a rigid style. There is a Python script that parses this style and converts the plain text PEP to HTML for viewing on the web[5]. Each PEP must begin with an RFC822 style header preamble. The headers must appear in the following order. Headers marked with `*' are optional and are described below. All other headers are required. PEP: <pep number> Title: <pep title> Version: <cvs version string> Author: <list of authors' email and real name> * Discussions-To: <email address> Status: <Draft | Active | Accepted | Deferred | Final | Replaced> Type: <Informational | Standards Track> Created: <date created on, in dd-mmm-yyyy format> * Python-Version: <version number> Post-History: <dates of postings to python-list and python-dev> * Replaces: <pep number> * Replaced-By: <pep number> Standards track PEPs must have a Python-Version: header which indicates the version of Python that the feature will be released with. Informational PEPs do not need a Python-Version: header. While a PEP is in private discussions (usually during the initial Draft phase), a Discussions-To: header will indicate the mailing list or URL where the PEP is being discussed. No Discussions-To: header is necessary if the PEP is being discussed privately with the author, or on the python-list or python-dev email mailing lists. PEPs may also have a Replaced-By: header indicating that a PEP has been rendered obsolete by a later document; the value is the number of the PEP that replaces the current document. The newer PEP must have a Replaces: header containing the number of the PEP that it rendered obsolete. PEP headings must begin in column zero and the initial letter of each word must be capitalized as in book titles. Acronyms should be in all capitals. The body of each section must be indented 4 spaces. Code samples inside body sections should be indented a further 4 spaces, and other indentation can be used as required to make the text readable. You must use two blank lines between the last line of a section's body and the next section heading. Tab characters must never appear in the document at all. A PEP should include the Emacs stanza included by example in this PEP. A PEP must contain a Copyright section, and it is strongly recommended to put the PEP in the public domain. You should footnote any URLs in the body of the PEP, and a PEP should include a References section with those URLs expanded. References and Footnotes [1] This historical record is available by the normal CVS commands for retrieving older revisions. For those without direct access to the CVS tree, you can browse the current and past PEP revisions via the SourceForge web site at http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/python/nondist/peps/?cvsroot=… [2] http://sourceforge.net/tracker/?group_id=5470&atid=305470 [3] http://sourceforge.net/tracker/?atid=355470&group_id=5470&func=browse [4] http://www.opencontent.org/openpub/ [5] The script referred to here is pep2html.py, which lives in the same directory in the CVS tree as the PEPs themselves. Try "pep2html.py --help" for details. The URL for viewing PEPs on the web is http://python.sourceforge.net/peps/ Copyright This document has been placed in the public domain. Local Variables: mode: indented-text indent-tabs-mode: nil End: [View Less]

2 1

test_coercion failing
by Jack Jansen March 21, 2001

March 21, 2001

Test_coercion fails on the Mac (current CVS sources) with We expected (repr): '(1+0j)' But instead we got: '(1-0j)' test test_coercion failed -- Writing: '(1-0j)', expected: '(1+0j)' The computation it was doing was "2 / (2+0j) =". To my mathematical eye it shouldn't be complaining in the first place, but I assume this may be either a missing round() somewhere or a symptom of a genuine bug. Can anyone point me in the right direction? -- Jack Jansen | ++++ stop the execution of … [View More]

7 9

Re: [Python-Dev] test_doctest failing, but perhaps by accident
by Michael Hudson March 21, 2001

March 21, 2001

Guido van Rossum <guido(a)digicool.com> writes: > > Cute! Hard to explain, unless someone is using PyDict_Next on this dict: > > since the dict has 11 items, it's exactly at the boundary where PyDict_Next > > will now resize it. > > It *could* be the garbage collector. I think it would have to be; there just aren't that many calls to PyDict_Next around. I confused myself by thinking that calling keys() called PyDict_Next, but it doesn't. glad-that-one's-… [View More]

1 0