Mailman 3 November 2000 - Python-Dev

Regression testing
by A.M. Kuchling Nov. 23, 2000

Nov. 23, 2000

This morning I was looking at test_minidom.py, which contains its own simplistic framework for running a series of regression tests. Maybe another 2.1 task could be selecting a standard unit testing framework; this should mostly be a matter of selecting one, since there are already some candidates. I'm aware of PyUnit (pyunit.sourceforge.net) and the unittest.py from Quixote, and have a vague feeling I'm forgetting one other module. No prizes for guessing which one I'd vote for. :) --amk

2 1

Too much silence
by Andrew Kuchling Nov. 23, 2000

Nov. 23, 2000

All the PEPs for 2.1 are supposed to be complete for Dec. 16, and some of those PEPs are pretty complicated. I'm a bit worried that it's been so quiet on python-dev lately, especially after the previous two weeks of lively discussion. (And no comments on my Python/Distutils PEP at all -- not even an assigned number... <sniffle>) --amk

8 10

more Sourceforge CVS screwiness
by Charles G Waldman Nov. 22, 2000

Nov. 22, 2000

Haven't seen this for a while - I was unable to build the most current version of Python from CVS and was about to squawk, when I realized that the problem was a bogus "config.h" in my dist/src/Include directory: shell$ pwd /usr/local/src/Python-CVS/python/dist/src/Include shell$ cvs status config.h =================================================================== File: config.h Status: Up-to-date Working revision: 2.1 Repository revision: 2.1 /cvsroot/python/python/dist/src/Include/Attic/config.h,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) A fresh checkout of the whole tree does not contain this file. I know how to fix this (edit CVS/Entries) but it troubles me that old files from the Attic keep re-appearing when I do updates (without any sticky tags or anything, I always do "cvs update -dP") Am I the only person who sees this? Does Sourceforge just not like me for some reason?

1 0

Re: [Python-checkins] CVS: python/dist/src/Lib/xml/dom minidom.py,1.13,1.14
by Andrew Kuchling Nov. 22, 2000

Nov. 22, 2000

On Tue, Nov 21, 2000 at 02:02:24PM -0800, Fred L. Drake wrote: >Update of /cvsroot/python/python/dist/src/Lib/xml/dom >In directory slayer.i.sourceforge.net:/tmp/cvs-serv16177/Lib/xml/dom > >Modified Files: > minidom.py ... Yay! This checkin may fix Bug #116677: "minidom:Node.appendChild() has wrong semantics". Does the patch check for illegal children (bug #116678). --amk

6 21

PEP Process Inefficient?
by Moshe Zadka Nov. 22, 2000

Nov. 22, 2000

The PEP process, while *miles* better then anything I've seen in any other development process I've ever seen, has some deficiencies. I'll try to point them out, and to suggest some partial solution: 1. Users are not sure who to post PEP questions/remarks to: Python dev? the original author? The Python devver they know best? 2. It is the responsiblity of the PEP author to add open questions/pertinent remarks to the PEP. 3. Mail about the PEP which contains important discussion is lost. Proposal: (still some shaky areas though): Why not use Squishdot for PEPs? The PEP would be the "article", and remarks could be comments. I think (but I'm not sure) Squishdot has the ability to edit/moderate comments, and retroactively change the article. If not, then my second best hope is some kind of Wiki system, with self imposed article/comments-like structure. Immediate problem I'm trying to solve: PEP 228, the numeric model PEP, has inspired a lot of discussion, and very interesting comments. However for someone who doesn't remember all the e-mails by heart, wading through the archives is much too time consuming. In addition, personal mail sent to me is not available for public discussion. Problems with proposed solution: no e-mail notification. I think Zwiki does have an option for e-mail notification, though. Don't know about Squishdot. -- Moshe Zadka <sig(a)zadka.site.co.il> This is a signature anti-virus. Please stop the spread of signature viruses!

8 14

[development doc updates]
by Fred L. Drake Nov. 22, 2000

Nov. 22, 2000

The development version of the documentation has been updated: http://python.sourceforge.net/devel-docs/

1 0

Re: [Python-Dev] Assertions
by uche.ogbuji＠fourthought.com Nov. 22, 2000

Nov. 22, 2000

> Tim Peters wrote: > > > > ... > > > > -1. User input is never trustworthy. Your and your users' software lives > > will be a lot happier if you stick to the rule that an assertion failure > > always (always!) announces a bug in the implementation -- assertion failure > > is never a user's fault. > > So you prefer > > if __debug__ and node.nodeType!=ELEMENT_TYPE: > raise TypeError > > Unfortunately there's no way to turn that off at "compile time" so you > always incur the __debug__ lookup cost. That would send us back to two > versions of the methods. > > Maybe testing would indicate that the performance implications are > minor. If so, I wouldn't mind having the type checks in there. Of course, continuations would be perfect here, as one could set the continuation to resume after the check if he wished to bypass it. Something tells me I should duck now... not-very-seriously-mind-you'ly yrs -- Uche Ogbuji Principal Consultant uche.ogbuji(a)fourthought.com +1 303 583 9900 x 101 Fourthought, Inc. http://Fourthought.com 4735 East Walnut St, Ste. C, Boulder, CO 80301-2537, USA Software-engineering, knowledge-management, XML, CORBA, Linux, Python

1 0

Re: [Python-checkins] CVS: python/dist/src/Lib/xml/dom minidom.py,1.13,1.14
by Greg Stein Nov. 22, 2000

Nov. 22, 2000

On Tue, Nov 21, 2000 at 02:02:24PM -0800, Fred L. Drake wrote: > Update of /cvsroot/python/python/dist/src/Lib/xml/dom > In directory slayer.i.sourceforge.net:/tmp/cvs-serv16177/Lib/xml/dom > > Modified Files: > minidom.py > Log Message: >... > *** minidom.py 2000/10/23 18:09:50 1.13 > --- minidom.py 2000/11/21 22:02:22 1.14 > *************** > *** 15,22 **** > """ > > - import pulldom > import string This "import string" plus numerous uses within minidom seem a bit extraneous since this is part of the Python 2.0 library... Cheers, -g -- Greg Stein, http://www.lyra.org/

2 1

Greg Stein in Bug Assignments?
by Moshe Zadka Nov. 21, 2000

Nov. 21, 2000

I've looked at the people bugs can be assigned to, and Greg Stein is missing. Is this purposeful or just an oversight? Specifically, bug 123045 seems to be a two-second fix, but I'd rather Greg would look at it -- it's his code originally, so maybe he does not think it's a bug. -- Moshe Zadka <moshez(a)math.huji.ac.il> -- 95855124 http://advogato.org/person/moshez

3 3

Re: [Python-Dev] Too much silence
by Moshe Zadka Nov. 21, 2000

Nov. 21, 2000

> No doubt. I'm still waiting for some feedback on my coercion > patch. I'd write a PEP but I don't think it would help. Marc's > web page already explains things in detail. Also, I don't want > to spend too much time going down a path that Guido and the other > developers are not going to accept. Neil, you can take the coercion patch from me. I thought I'd have more time to deal with it then I do. Please let me know. -- Moshe Zadka <sig(a)zadka.site.co.il> This is a signature anti-virus. Please stop the spread of signature viruses!

1 0