[Python-Dev] List of candidate 2.4.4 bugs?

Is anyone maintaining a list of candidate bugs to be fixed in 2.4.4? If not, should we start a wiki page for the purpose? --amk ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mai

[Python-Dev] Arlington sprints to occur monthly

Jeffrey Elkner has arranged things so that the 1-day Python sprints in Arlington VA will now be happening every month. Future sprints will be on September 23rd, October 21st, November 18th, and December 16th. See http://wiki.python.org/moin/ArlingtonSprint for directions and to sign up. --amk _

Re: [Python-Dev] Removing anachronisms from logging module

On Fri, Aug 25, 2006 at 10:44:53AM -0700, Guido van Rossum wrote: > any more; neither does Vinay. I propose as a project for someone to > clean it up ... There's a list of simple tasks in the wiki at . --amk ___ P

Re: [Python-Dev] What should the focus for 2.6 be?

On Mon, Aug 21, 2006 at 12:24:54PM -0700, Brett Cannon wrote: > As for the docs, they just need a thorough updating. Michael Hudson was working on a new guide to extending/embedding Python. Incorporating that should be a goal for 2.6 (the document may still need to be finished -- I'm not sure w

Re: [Python-Dev] 2.4 & 2.5 beta 3 crash

On Fri, Aug 18, 2006 at 12:26:33AM +0200, Armin Rigo wrote: > Without more inspection, I'd say that this looks like it won't do the > right thing about nested finally's, as in: I guess it'll have to loop back up through the block stack: for (j=i- 1; j>=0; j--) { switch (c->u->u_fblock[j].fb_ty

Re: [Python-Dev] no remaining issues blocking 2.5 release

On Tue, Aug 15, 2006 at 10:44:40PM -0400, Kurt B. Kaiser wrote: > It would be nice if the key IDLE changes could make it to the "What's New > in Python X.X". If Andrew is interested, I could draft something for him. Sure! I can try to look through the IDLE NEWS file, but you'd certainly have a b

Re: [Python-Dev] Arlington VA sprint on Sept. 23

On Tue, Aug 15, 2006 at 12:21:34AM +0200, Georg Brandl wrote: > * close RFEs and patches which have no chance of going in (there are many > patches on SF having one or two "-1" comments, is anyone ever going to > check them in without a python-dev discussion?) In the past, someone (I think Ray

[Python-Dev] Arlington VA sprint on Sept. 23

The CanDo group continues to have sprints in Arlington, so we may as well continue to piggyback on their space. The next one will be Saturday Sept. 23; sign up at . If the PEP 356 plan holds, Python 2.5 will have been released a week and a half before.

Re: [Python-Dev] uuid test suite failing

On Thu, Jul 27, 2006 at 05:40:57PM +0200, Georg Brandl wrote: > The UUID test suite, which wasn't run by regrtest.py until now, is > now failing on some buildbots (and my machine). This should be fixed > before releasing something. Looking at the failures, there seem to be two problems on Unix var

[Python-Dev] Release manager: pdb bugfix incompatibility

Bug #1526834: if you do 'b f(' in pdb, the debugger crashes. This bug stems from pdb just sticking the string in a regex and compiling it. cre = re.compile(r'def\s+%s\s*[(]' % funcname) A side effect of this is that 'b f()' works to match the function 'f', because the empty parens are legal reg

[Python-Dev] 2.5: uses of sys.exc_type, exc_value

http://www.python.org/sf/1525469 reports that SimpleXMLRPCServer.py still uses sys.exc_type and sys.exc_value when handling exceptions. These variables aren't thread-safe and sys.exc_info() is the better way. I have a patch attached to the bug that fixes the problem. Question 1: is this worth fix

[Python-Dev] Python sprint in Arlington July 29/30

The CanDo developers are sprinting for three days starting on this coming Friday, so there's space available for a Python sprint. I'll try to attend at least on Saturday (Sunday may not be possible for me). Does anyone want to come and work on Python stuff? If yes, please add your name to

Re: [Python-Dev] Community buildbots (was Re: User's complaints)

On Fri, Jul 14, 2006 at 01:37:28PM +0200, Fredrik Lundh wrote: > (add PEP announcements and python-dev summary items to the mix, and you > have a high-quality development blog generated entirely from existing content) > (hmm. maybe this could be put together by a robot? time to start hacking on >

Re: [Python-Dev] Community buildbots (was Re: User's complaints)

On Fri, Jul 14, 2006 at 12:00:07PM +0200, Giovanni Bajo wrote: > unstable or whatnot. There is no official statement of the kind "all > the real development is done in branches, the trunk is always very > stable, feel free to grab it". Thus, we (external developers) assume > that it's better to wai

Re: [Python-Dev] Community buildbots (was Re: User's complaints)

On Thu, Jul 13, 2006 at 02:03:22PM -0400, [EMAIL PROTECTED] wrote: > I would like to propose, although I certainly don't have time to implement, > a program by which Python-using projects could contribute buildslaves which > would run their projects' tests with the latest Python trunk. An excellen

Re: [Python-Dev] User's complaints

On Mon, Jul 10, 2006 at 05:13:53PM +0200, Armin Rigo wrote: > didn't draw much applause. It certainly gave me the impression that > many changes in Python are advocated and welcomed by only a small > fraction of users. The benefits of changes are usually clear, but I don't think the costs of chan

[Python-Dev] Another 2.5 bug candidate?

http://www.python.org/sf/1488934 argues that Python's use of fwrite() has incorrect error checking; this most affects file.write(), but there are other uses of fwrite() in the core. It seems fwrite() can return N bytes written even if an error occurred, and the code needs to also check ferror(f->f

Re: [Python-Dev] For sandboxing: alternative to crippling file()

On Thu, Jun 29, 2006 at 11:48:36AM -0700, Brett Cannon wrote: > My worry, as has been from the start, is containing 'file'. The ``del > __builtins__`` bug for 'rexec' started me as skittish towards hiding stuff > from the built-in namespace. And knowing how easy it tends to be to get at > objects

Re: [Python-Dev] xturtle.py a replacement for turtle.py(!?)

On Wed, Jun 28, 2006 at 12:57:23PM +0200, Gregor Lingl wrote: > I would very much appreciate if xturtle.py could go into > Python 2.5 That decision is up to Anthony Baxter, the release manager. Unfortunately 2.5beta1 is already out, and the developers try to avoid large changes during the beta se

[Python-Dev] Do we need a bug triage day?

Do we need a sort of mini bug-day to look at the outstanding bugs and note ones that absolutely need to be fixed before 2.5final? Or has someone already done this? --amk ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/l

Re: [Python-Dev] ImportWarning flood

On Mon, Jun 26, 2006 at 08:29:49AM +0200, "Martin v. Löwis" wrote: > (read some email archives > to find out what the original problem was). People at Google don't read manuals? --amk ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.

Re: [Python-Dev] ImportWarning flood

On Wed, Jun 21, 2006 at 10:34:53PM -0700, Ralf W. Grosse-Kunstleve wrote: > But this doesn't: > python -W'ignore:Not importing directory:ImportWarning' This is a bug. I've filed bug #1510580 and assigned it to Brett. I think the problem was exposed by the new-style exception change, but the actu

Re: [Python-Dev] External Package Maintenance (was Re: Please stopchanging wsgiref on the trunk)

On Mon, Jun 12, 2006 at 03:12:20PM -0400, Phillip J. Eby wrote: > encountered this myself. I *have* seen some developers make spurious > "cleanups" to working code that breaks compatibility with older Python > versions, though, just not in wsgiref. Note that the standard library policy has alwa

Re: [Python-Dev] Dropping externally maintained packages (Was:Please stop changing wsgiref on the trunk)

On Mon, Jun 12, 2006 at 11:25:21AM -0700, Guido van Rossum wrote: > Have any instances of that actually happened? That would be a problem > with *any* code in the Python library, not just external > contributions, so I'm not sure why external contribions should be > treated any differently here. T

Re: [Python-Dev] External Package Maintenance

On Mon, Jun 12, 2006 at 10:42:44AM -0700, Guido van Rossum wrote: > standard library code is just more of a maintenance burden. Maybe we > should get serious about slimming down the core distribution and > having a separate group of people maintain sumo bundles containing > Python and lots of other

Re: [Python-Dev] 2.5 issues need resolving in a few days

On Fri, Jun 09, 2006 at 07:28:47AM -0700, Aahz wrote: > Okay, I guess I mis-remembered what had been agreed to. Should this go > into What's New? Already there: . (Fred, is it possible to set the anchors used for

Re: [Python-Dev] Symbol page for Language Reference Manual Index

On Thu, Jun 08, 2006 at 12:18:23AM -0400, Terry Reedy wrote: > I am willing to do perhaps half the work needed to produce such in time for > the 2.5 release. In particular, I am willing to write a plain text file > listing symbols (in ascii sort order) and section numbers, in an agreed-on > for

Re: [Python-Dev] wsgiref doc draft; reviews/patches wanted

On Tue, Jun 06, 2006 at 06:49:45PM -0400, Phillip J. Eby wrote: > Source: http://svn.eby-sarna.com/svnroot/wsgiref/docs Minor correction: svn://svn.eby-sarna.com/svnroot/wsgiref/docs (at least, http didn't work for me). The docs look good, and I think they'd be ready to go in. --amk

Re: [Python-Dev] Stdlib Logging questions (PEP 337 SoC)

On Tue, Jun 06, 2006 at 10:36:06AM -0400, Jim Jewett wrote: > Are you suggesting that the logging module should ship with a standard > configuration that does something specific for py.* loggers? Or even > one that has different handlers for different stdlib modules? No, I meant some modules don'

[Python-Dev] DC Python sprint on July 29th

The Arlington sprint this past Saturday went well, though the number of Python developers was small and people mostly worked on other projects. The CanDo group, the largest at the sprint with about 10 people, will be having a three-day sprint July 28-30 (Fri-Sun) at the same location. We should

Re: [Python-Dev] Stdlib Logging questions (PEP 337 SoC)

On Mon, Jun 05, 2006 at 08:49:47PM -0400, Jim Jewett wrote: > If no explicit changes are made locally, > >py.asyncore.dispatcher.hits >py.asyncore.dispatcher.messages These handler names seem really specific, though. Why have 'dispatcher' in there? Part of Jackilyn's task should be to r

Re: [Python-Dev] wsgiref documentation

On Mon, Jun 05, 2006 at 06:33:29PM -0400, Phillip J. Eby wrote: > At 08:08 AM 6/5/2006 -0400, A.M. Kuchling wrote: > >I had the start of an outline in sandbox/wsgiref-docs, but am not > >working on them at the moment because no one is willing to say if the > >list of documente

Re: [Python-Dev] wsgiref documentation

On Fri, Jun 02, 2006 at 03:33:41PM -0400, Doug Fort wrote: > I'm going over the possible tasks for the Arlington Sprint. > Documentation for wsgiref looks like somethng I could handle. > > Is anyone already working on this? I had the start of an outline in sandbox/wsgiref-docs, but am not working

Re: [Python-Dev] Python Benchmarks

On Fri, Jun 02, 2006 at 07:44:07PM -0400, Tim Peters wrote: > Fortran code could scream. Test times were reproducible to the > nanosecond with no effort. Running on a modern box for a few > microseconds at a time is a way to approximate that, provided you > measure the minimum time with a high-re

Re: [Python-Dev] [Python-3000] stdlib reorganization

On Tue, May 30, 2006 at 11:46:06PM -0700, Talin wrote: > I like it. Its a much cleaner organization than the 2.4 libs. I would > like to see it used as a starting point for a reorg of the standard lib > namespace. I'm not convinced that the chapter organization of a book is necessarily the best

Re: [Python-Dev] [Python-3000] stdlib reorganization

On Tue, May 30, 2006 at 03:36:02PM -0600, Steven Bethard wrote: > That sounds about reasonable. One possible grouping: Note that 2.5's library reference has a different chapter organization from 2.4's. See . --amk

[Python-Dev] partition() variants

I didn't find an answer in the str.partition() thread in the archives (it's enormous, so easy to miss the right message), so I have two questions: 1) Is str.rpartition() still wanted? 2) What about adding partition() to the re module? --amk ___ Python

[Python-Dev] Confirmed: DC-area sprint on Sat. June 3rd

The DC-area sprint is now confirmed. It'll be on Saturday June 3, from 10 AM to 5 PM at the Arlington Career Center in Arlington VA. I've created a wiki page at ; please add your name if you'll be coming. The wiki page can also be used to brainstorm a

Re: [Python-Dev] Date for DC-area Python sprint?

I found out that May 27th is on Memorial Day weekend, and some people will doubtless have travel plans. Let's aim for the next Saturday, June 3rd. (No intersection with the Need for Speed sprint; oh well.) I'll post a detailed announcement and set up a wiki page when things are nailed down, but

[Python-Dev] Date for DC-area Python sprint?

I'm working on setting up a sprint in the Washington DC area; currently I have a lead that would be in Arlington. I'd like to discuss the date on python-dev in order to coordinate with other events. The sprint has no particular goal, so people might just hack on their core-related projects. It c

Re: [Python-Dev] introducing the experimental pyref wiki

On Sat, Apr 29, 2006 at 08:54:00PM +0200, Fredrik Lundh wrote: > http://pyref.infogami.com/ I find this work very exciting. Time hasn't been kind to the reference guide -- as language features were added to 2.x, not everything has been applied to the RefGuide, and users will probably have bee

Re: [Python-Dev] [Python-checkins] r45770 - in python/trunk:

On Fri, Apr 28, 2006 at 01:13:21AM +0200, thomas.wouters wrote: > - Warn-raise ImportWarning when importing would have picked up a directory >as package, if only it'd had an __init__.py. This swaps two tests (for >case-ness and __init__-ness), but case-test is not really more expensive, >

Re: [Python-Dev] 2.5 open issues

On Fri, Apr 28, 2006 at 11:02:07AM -0400, Phillip J. Eby wrote: > I doubt I'll have time to write documentation for it before alpha 3. If > it's okay for the docs to wait for one of the beta releases -- or better > yet, if someone could volunteer to create rough draft documentation that I > cou

Re: [Python-Dev] 2.5 open issues

On Thu, Apr 27, 2006 at 10:58:49PM -0700, Neal Norwitz wrote: > If you are addressed on this message, it means you have open issues > that need to be resolved for 2.5. Some of these issues are > documentation, others are code issues. This information comes from > PEP 356. There are also these it

Re: [Python-Dev] 2.5 open issues

On Fri, Apr 28, 2006 at 10:27:45AM +0200, Thomas Heller wrote: > I could imagine three parts of the ctypes docs: ... > 3. Some articles/howtos which cover advanced issues. Note that there's now a Doc/howto directory, so you could put articles there. The howtos aren't built as part of the docume

Re: [Python-Dev] Reviewed patches

On Tue, Apr 25, 2006 at 06:04:12PM -0400, Jim Jewett wrote: > So how are the committers supposed to even know that it is waiting for > assessment? The solutions that I've seen work are Could we mark the bug/patch as status 'pending'? This status exists in the SF bug tracker but no bugs or patche

Re: [Python-Dev] Reviewed patches [was: SoC proposal: "fix some old, old bugs in sourceforge"]

On Tue, Apr 25, 2006 at 04:10:02PM -0400, Jim Jewett wrote: > I don't see a good way to say "It looks good to me". I don't see any > way to say "There were issues, but I think they're resolved now". So > either way, I and the author are both sort of waiting for a committer > to randomly happen ba

Re: [Python-Dev] Updated context management documentation

On Wed, Apr 26, 2006 at 12:08:47AM +1000, Nick Coghlan wrote: > However, I made the > changes below in order to address the conflicts between the alpha 1 > documentation and implementation. IMHO this set of changes makes the terminology reasonably clear, so I'm happy with it. I've edited the Wh

Re: [Python-Dev] SoC proposal: "fix some old, old bugs in sourceforge"

On Mon, Apr 24, 2006 at 09:45:41PM -0700, Neal Norwitz wrote: > hard bugs to fix. I guess there are also a lot that we can't > reproduce and the submitter is MIA. Those might be easier. Ping them > if not reproducible, if no response in a month, we close. The last time there was a thread sugges

Re: [Python-Dev] SoC proposal: "fix some old, old bugs in sourceforge"

On Mon, Apr 24, 2006 at 12:30:12PM -0400, Alan McIntyre wrote: > My unglamorous proposal is to review bugs & patches (starting with the > oldest) and resolve at least 200 of them. Is that too much? Too few? > I'll fix as many as possible during the SoC time frame, but I wanted to > set a realist

[Python-Dev] Adding wsgiref

What with all the discussion that resulted from setuptools, we should probably also discuss the suggestion to add wsgiref to the standard library. PEP 356 doesn't have many details about what's under consideration. (wsgiref is an implementation of the WSGI interface defined in PEP 333. I believe

Re: [Python-Dev] Why are contexts also managers? (was r45544 - peps/trunk/pep-0343.txt)

On Fri, Apr 21, 2006 at 06:54:11PM +0100, Guido van Rossum wrote: > Phillip, I do recomment you look at decimal.py. If we're not reversing > the PEP changes, that module needs to be changed; it has a class > Context (that was always there) with a __context__ method which > returns an instance of a

Re: [Python-Dev] Why are contexts also managers? (was r45544 - peps/trunk/pep-0343.txt)

On Fri, Apr 21, 2006 at 07:31:35PM +1000, Nick Coghlan wrote: > fit the new definition. So we settled on calling them "context managers" > instead. ... > method. Instead, the new term "manageable context" (or simply "context") > was introduced to mean "anything with a __context__ method". This

[Python-Dev] Distutils for Python 2.1 (was "Raising objections")

On Thu, Apr 20, 2006 at 11:33:30AM +0100, Guido van Rossum wrote: > Unfortunately, this is mixed in with some stuff that isn't part of > distutils' "core competency", like text utilities, process spawning, > and option parsing. These should (eventually, when the 2.1 > compatibility requirement is l

Re: [Python-Dev] Raising objections

On Thu, Apr 20, 2006 at 07:53:55AM +0200, "Martin v. Löwis" quoted: > > It is flatly not possible to "fix" distutils and preserve backwards > > compatibility. Would it be possible to figure what parts are problematic, and introduce PendingDeprecationWarnings or DeprecationWarnings so that we can

Re: [Python-Dev] Raising objections

On Wed, Apr 19, 2006 at 03:02:15PM -0400, Phillip J. Eby wrote: > I can tell you the reasons, no need to guess: 5. The Distutils has lots of customization hooks, but if the exact hook you need isn't there, you're in deep trouble. I learned this when trying to implement a package database. > I a

Re: [Python-Dev] Why are contexts also managers? (was r45544 - peps/trunk/pep-0343.txt)

On Wed, Apr 19, 2006 at 11:10:55PM +1000, Nick Coghlan wrote: > When Phillip went through to make the terminology consistent he actually > swapped the meanings of "context" (which meant 'has a __context__ method' > in the original PEP) and "context manager" (which meant 'has __enter__ and > __ex

Re: [Python-Dev] Why are contexts also managers? (was r45544 - peps/trunk/pep-0343.txt)

On Wed, Apr 19, 2006 at 10:00:21PM +1000, Nick Coghlan wrote: > And the parenthetical comment was completely backwards and should have read: > > (This means that all context managers are contexts, but not all contexts > are >context managers). > > The reason for recommending that context

Re: [Python-Dev] Raising objections

On Wed, Apr 19, 2006 at 10:54:09AM +0200, Gerhard Häring wrote: > We should probably check my docs in soon even in a preliminary state, so > they can be reviewed/improved. There's a group of volunteers who will help fix the LaTeX markup, so you certainly don't need to have everything working (or

Re: [Python-Dev] Raising objections (was: setuptools in the stdlib)

On Tue, Apr 18, 2006 at 09:10:20PM -0700, Neal Norwitz wrote: > There is an outstanding issues section in the 2.5 release PEP 356. In > this case, perhaps it would have been good to add a bullet item there. > I've been trying to ensure the issues aren't lost. There's only one > item in the list t

Re: [Python-Dev] Why are contexts also managers? (was r45544 - peps/trunk/pep-0343.txt)

On Tue, Apr 18, 2006 at 03:37:37PM -0400, Phillip J. Eby wrote: > I was going to say, "so they can be context managers", but I suppose you > have a point. There is no need for a context to have a __context__ method, > unless it is also a context manager. Ugh. It would be easy to just remove th

[Python-Dev] Why are contexts also managers? (was r45544 - peps/trunk/pep-0343.txt)

On Tue, Apr 18, 2006 at 08:55:18PM +0200, phillip.eby wrote: > Modified: >peps/trunk/pep-0343.txt > > +"context manager" then encompasses all objects with a __context__() > +method that returns a context object. (This means that all contexts > +are context managers, but not all con

[Python-Dev] PEP 343: confusing context terminology

PEP 343 says: This PEP proposes that the protocol used by the with statement be known as the "context management protocol", and that objects that implement that protocol be known as "context managers". The term "context" then encompasses all objects with a __context__() method

Re: [Python-Dev] TODO Wiki (was: Preserving the blamelist)

On Wed, Apr 12, 2006 at 11:23:51PM -0400, Tim Peters wrote: > Not the same thing, but I just added: > http://wiki.python.org/moin/SimpleTodo I added a list of the Demo directories so that people know which ones need updating. --amk ___ Python-Dev ma

Re: [Python-Dev] Preserving the blamelist

On Wed, Apr 12, 2006 at 01:43:43PM -0400, Tim Peters wrote: > BTW, someone looking for an easy task might enjoy rewriting other > tp_traverse slots to use Py_VISIT. We even have cases now (like > super_traverse) where modules define their own workalike > traverse-visit macros, which has become con

Re: [Python-Dev] outstanding items for 2.5

On Sun, Apr 02, 2006 at 11:34:18PM -0800, Neal Norwitz wrote: > Review the PEP and let me know what needs to be changed. If your pet > project isn't already in the PEP, assume it has been deferred until > 2.6. I'd like to see Gregory K. Johnson's updated mailbox module (in sandbox/mailbox/) inclu

[Python-Dev] Py3K thought: use external library for client-side HTTP

Thought: We should drop all of httplib, urllib, urllib2, and ftplib, and instead adopt some third-party library for HTTP/FTP/whatever, write a Python wrapper, and use it instead. (The only such library I know of is libcurl, but doubtless there are other candidates; see http://curl.haxx.se/libcurl/

[Python-Dev] Topic suggestions from the PyCon feedback

Those of you on python-checkins will have noticed the recent fiddling around with the feedback from PyCon. I'd like to draw the attention of the python-dev readership to the answers for the question "What 3 topics should have been covered at PyCon?" I split out core Python and web-related topic

Re: [Python-Dev] C AST to Python discussion

On Wed, Feb 15, 2006 at 10:29:38AM -0500, Jeremy Hylton wrote: > Unfortunately, the compiler talk isn't until the last day and I can't > stay for sprints. It would be better to have the talk, then the open > space, then the sprint. If you mean "Implementation of the Python Bytecode Compiler", tha

Re: [Python-Dev] http://www.python.org/dev/doc/devel still available

On Mon, Feb 13, 2006 at 03:52:44PM -0500, Fred L. Drake, Jr. wrote: > What I would also like to see is to have an automatically-updated > version for each of the maintainer versions of Python, as well as > the development trunk. That would mean two versions at this point > (2.4.x, 2.5.x); only one

Re: [Python-Dev] PEP 247 and hashlib

On Mon, Jan 16, 2006 at 01:37:18PM +0900, Seo Sanghyeon wrote: > But hashlib.new() takes the algorithm name... Does PEP need an update? The new() function in hashlib's interface doesn't conform to PEP 247; that's all. I don't think the PEP needs to be updated. --amk _

[Python-Dev] PyCon TX 2006: Early-bird registration ends Jan. 15!

book your hotel room, too. PyCon TX 2006 is being held at a Dallas/Addison hotel, and we have negotiated a special low rate of $79 plus applicable taxes: http://us.pycon.org/Addison/Hotels We hope to see you in Texas! Regards, A.M. Kuchling [EMAIL PROTECTED] Chair, PyCon 2006 http://us

Re: [Python-Dev] LaTeX and Python doc contributions

On Thu, Dec 22, 2005 at 12:23:03PM -0600, [EMAIL PROTECTED] wrote: > Who is asking this of potential contributors? I know you, Aahz and I have > repeatedly told people on c.l.py that LaTeX knowledge is not necessary. One comment on a bug to this effect was found. I don't think there's a point in

Re: [Python-Dev] documentation comments

On Thu, Dec 22, 2005 at 09:27:06AM +, Steve Holden wrote: > Could the PSF help here by offering annual prizes for the best > contributions to the documentation, or wouldn't that be an adequate > motivator? I think the most effective thing would be to award a grant to someone to build a real

Re: [Python-Dev] status of development documentation

On Wed, Dec 21, 2005 at 07:55:42PM +0100, Walter Dörwald wrote: > >reST is a possibility, though I don't think anyone has worked on > >building the required toolchain. Fred has a LaTeX-to-XML-format > >converter kicking around somewhere, > > Is this available somewhere? Docs/tools/sgmlconv/, I t

Re: [Python-Dev] status of development documentation

On Wed, Dec 21, 2005 at 05:10:24PM +0100, Fredrik Lundh wrote: > (as I hinted, I'd prefer HTML with microformat annotations as the > main format; with roundtripping to markdown or rest (etc) for people > who prefer to author in that, and tidy->xhtml->python tools for the > HTML generation) I don't

Re: [Python-Dev] "xml" package in standard library

On Tue, Dec 13, 2005 at 03:54:00PM -0500, Fred L. Drake, Jr. wrote: > I'd like to propose that a new package be created in the standard library: > xmlcore. This package should contain what's currently in the "xml" package. +1; it's what should have been done in the first place. --amk __

[Python-Dev] c.l.p post on docs

I just posted a lengthy message to comp.lang.python/python-list about Python's docs; the title is "Documentation suggestions". A short summary of the post is: "The RefGuide is hard to read and hard to keep updated. Do we need a friendly language description? If we do that, should the existing Re

Re: [Python-Dev] [Python-checkins] commit of r41586 - in python/trunk: Lib/SimpleXMLRPCServer.py Misc/NEWS

On Tue, Dec 06, 2005 at 07:47:06AM -0800, Guido van Rossum wrote: > Happened to see this commit. What's the magic about 10MB? Is there any > understanding of what causes it to fail? What is the failure mode? > Could it just be fragmentation causing the malloc or realloc to fail? > Should we perhaps

[Python-Dev] Python bug day this Sunday

Let's have a Python bug day this Sunday. One goal might be to assess bugs and patches, and make a list of ones we can work on at the Python core sprint at PyCon . Meeting on IRC: #python-dev on irc.freenode.net Date: Sunday, December 4t

Re: [Python-Dev] Memory management in the AST parser & compiler

On Wed, Nov 30, 2005 at 07:42:20PM +1000, Nick Coghlan wrote: > The second step is to then modify ast.c to use the new structures. A branch > probably wouldn't help much with initial development (this is a "break the > world, check in when stuff compiles again" kind of change, which is hard to >

[Python-Dev] Bug day this Sunday?

Is anyone interested in joining a Python bug day this Sunday? A useful task might be to prepare for the python-core sprint at PyCon by going through the bug and patch managers, and listing bugs/patches that would be good candidates for working on at PyCon. We'd meet in the usual location: #python

Re: [Python-Dev] s/hotshot/lsprof

On Sun, Nov 20, 2005 at 11:33:42PM +0100, Fredrik Lundh wrote: > do we really need CADT-based development in the standard library? I didn't recognize the acronym, but Google told me CADT = "Cascade of Attention-Deficit Teenagers"; see http://www.jwz.org/doc/cadt.html for a rant. --amk __

[Python-Dev] python-dev sprint at PyCon

Every PyCon has featured a python-dev sprint. For the past few years, hacking on the AST branch has been a tradition, but we'll have to come up with something new for this year's conference (in Dallas Texas; sprints will be Monday Feb. 27 through Thursday March 2). According to Anthony's release

[Python-Dev] Reminder: PyCon 2006 submissions due in a week

The submission deadline for PyCon 2006 is now a week away. PyCon 2006 will be in Dallas, Texas, February 24-26 2006. For 2006, I'd like to see more tutorial-style talks on the program. This means that your talk doesn't have to be about something entirely new; you can show how to use a particular

Re: [Python-Dev] AST branch is in?

On Tue, Oct 25, 2005 at 01:36:26PM +1000, Simon Burton wrote: > Is there a python interface ? Not yet, as far as I know. FYI, all: please see the following weblog entry for a description of the AST branch: http://www.amk.ca/diary/2005/10/the_ast_branch_lands_1 If I got anything wrong,

Re: [Python-Dev] Tools directory (Was RE: Replacement for print in Python 3.0)

On Thu, Sep 08, 2005 at 06:52:59PM -0700, Brett Cannon wrote: > Otherwise it is mostly a lack of advertisement and them not being > installed by ``make install``. If you just download the soure and Agreed. I've often wished that reindent.py was installed somewhere. > Probably the only way > i

Re: [Python-Dev] Replacement for print in Python 3.0

On Fri, Sep 02, 2005 at 10:07:29AM +0200, Fredrik Lundh wrote: > > OK, now that I've offended everyone, I'll go back into retirement. But I > > *am* laughing at you. > > Amen. Seconded. --amk ___ Python-Dev mailing list Python-Dev@python.org http://mai

Re: [Python-Dev] python/dist/src/Lib/test test_re.py, 1.45.6.3, 1.45.6.4

On Wed, Aug 31, 2005 at 07:56:04PM -0400, Jim Jewett wrote: > What is the reasoning behind this? > > It seems to me that if a (passing) test is being added, maintenance releases > are the *most* important places to run them. In this case, it's because adding the test requires importing a new mod

[Python-Dev] Switching re and sre

FYI: In a discussion on the Python security response list, Guido suggested that the sre.py and re.py modules should be switched. Currently re.py just imports the contents of sre.py -- once it supported both sre and the PCRE-based pre.py -- and sre.py contains the actual code. Now that pre.py is g

[Python-Dev] New mailbox module

Gregory K. Johnson, who's been working on the mailbox module in nondist/sandbox/mailbox for Google's Summer of Code, thinks his project is essentially complete. He's added the ability to modifying mailboxes by adding and removing messages, adding test cases for the new features, and written the co

[Python-Dev] PEP 8: exception style

PEP 8 doesn't express any preference between the two forms of raise statements: raise ValueError, 'blah' raise ValueError("blah") I like the second form better, because if the exception arguments are long or include string formatting, you don't need to use line continuation characters because of

[Python-Dev] Request to add developer

I wish to request that 'gregorykjohnson' be added to the Python SF project. Gregory is the participant I'm mentoring in Google's Summer of Code program. His project is enhancing mailbox.py to give it the ability to modify mailboxes as well as read them; see http://gkj.freeshell.org/summer_of_code

[Python-Dev] Request to rewrite PEP 206

Just a note, sparked by Raymond's recent work cleaning up old PEPs: I'd like to take over PEP 206, the "Batteries Included" PEP, and rewrite it to describe a "Python Advanced Library", a set of third-party packages to complement the standard library. I've written to Moshe, the original author, to

Re: [Python-Dev] b32encode and NUL bytes

On Fri, Jun 10, 2005 at 01:13:35PM -0500, Jeff Epler wrote: > > Is this a feature? I do see b32encode padding the string with NULs first. This is bug #1170331, which was fixed when I applied patch #1171487 earlier this week. > This also seems suspect: > >>> base64.b32encode("\0a") > 'ABQQ' >

Re: [Python-Dev] Bug day on the 25th?

On Fri, Jun 10, 2005 at 11:35:47AM -0300, Gustavo Niemeyer wrote: > Not sure if that's a reason to prevent the event, since > fixing bugs is a good thing no matter when, but that's two > days before EuroPython, and many people might be moving to > the conference at that time. Thanks for pointing t

[Python-Dev] Bug day on the 25th?

It seems like a good idea to have another Python bug day. Saturday June 25th seems the most practical date (this coming weekend is too soon, and the weekend after is a minor holiday -- Father's Day). We'd convene in the usual place: the #pydotorg IRC channel, on irc.freenode.net. Assuming no on

Re: [Python-Dev] [Python-checkins] python/dist/src/Lib sre_compile.py, 1.57, 1.58

On Thu, Jun 02, 2005 at 03:34:17PM -0400, Raymond Hettinger wrote: > The times two operation also occurs twice in nearby code. Are those > also incorrect? I believe they're correct. EXPN: The regex engine refers to both 'groups', where group #N means the corresponding group in the pattern, and

[Python-Dev] Vestigial code in threadmodule?

Looking at bug #1209880, the following function from threadmodule.c is referenced. I think the args==NULL case, which can return None instead of a Boolean value, can never be reached because PyArg_ParseTuple() will fail if args==NULL. Before ripping the args==NULL code out, I wanted to be sure my

Re: [Python-Dev] Re: anonymous blocks

On Wed, Apr 20, 2005 at 08:18:11AM -0700, Aahz wrote: > antithesis, it would be either C++ or Perl. Ruby is antithetical to some > of Python's core ideology because it borrows from Perl, but Ruby is much > more similar to Python than Perl is. I'm not that familiar with the Ruby community; might i

<    1   2   3   4   >